atx/registry

spec-api-mcp.vercel.app

https://spec-api-mcp.vercel.app/mcp

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 agoe8952aa2dd5098dd…
dns_resolution_observation1d ago6e07379233a34740…
http_response_observation1d ago3596cf0c3f3ae99f…
hosting_provider_observation1d ago07b610f7cd67ffa2…
tls_certificate_observation1d agoc56037c91c742c74…
oauth_metadata_observation1d ago9be51e6f2cf25bf6…
mcp_protocol_observation1d agoe3befc1e32edc3d5…
mcp_capability_observation1d agocc9ce27cd5a0ac78…

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

Operate this service?

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

Claim this profile →