atx/registry

doc2mcp.site/api/mcp/407d9b68-d7db-4a44-b06d-9ca6fb5f3e1f

https://doc2mcp.site/api/mcp/407d9b68-d7db-4a44-b06d-9ca6fb5f3e1f/mcp

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 8h 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
dns_resolution_observation8h ago40050cf352b84d1c…
http_response_observation8h ago9031d4d6c84d9b47…
availability_observation8h agoe9b9ba306d7f5f46…
hosting_provider_observation8h ago07b610f7cd67ffa2…
tls_certificate_observation8h agoba853fb9efc964b2…
oauth_metadata_observation8h agoe163eeb9be3eaa33…
mcp_protocol_observation8h agoba8447a2f05fe896…
mcp_capability_observation8h ago3070f1625417370b…

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

Operate this service?

Prove control of doc2mcp.site/api/mcp/407d9b68-d7db-4a44-b06d-9ca6fb5f3e1f to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →