atx/registry

doc2mcp.site/api/mcp/e56f8219-0046-4351-9ba3-37e837db71ed

https://doc2mcp.site/api/mcp/e56f8219-0046-4351-9ba3-37e837db71ed/mcp

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d 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_observation2d ago40050cf352b84d1c…
http_response_observation2d ago8552714feff19763…
availability_observation2d agoe7abb2e6a7563368…
hosting_provider_observation2d ago07b610f7cd67ffa2…
tls_certificate_observation2d ago5a85346bfb3a144b…
oauth_metadata_observation2d agoe163eeb9be3eaa33…
mcp_protocol_observation2d agofca071e363257f8f…
mcp_capability_observation2d ago3070f1625417370b…

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

Operate this service?

Prove control of doc2mcp.site/api/mcp/e56f8219-0046-4351-9ba3-37e837db71ed to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →