atx/registry

patchistry-mcp-server.vercel.app/rpc

https://patchistry-mcp-server.vercel.app/rpc

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago

Why this score

tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
availability_observation1d ago1a4518ef5a1f3ebf…
hosting_provider_observation1d ago07b610f7cd67ffa2…
tls_certificate_observation1d agoc56037c91c742c74…
dns_resolution_observation1d ago9a65cec8e5d57f7d…
http_response_observation1d agoc49af4067222aa9d…
oauth_metadata_observation1d ago1b2e18b267a4494a…
mcp_capability_observation1d agof2aee1b66b849df8…
mcp_protocol_observation1d agod44ad26a8a76039d…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of patchistry-mcp-server.vercel.app/rpc to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →