atx/registry

apistatuscheck.com/api

https://apistatuscheck.com/api/mcp

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2h 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_observation2h ago8b66db674e29d397…
http_response_observation2h agode82f0818ba11dbf…
availability_observation2h ago0c851f593b809b50…
hosting_provider_observation2h ago07b610f7cd67ffa2…
tls_certificate_observation2h agoe6568a58b68cf1b9…
oauth_metadata_observation2h ago0c6b100d7a64521e…
mcp_protocol_observation2h ago37874468199e082a…
mcp_capability_observation2h ago15febf3fcc9e3483…

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

Operate this service?

Prove control of apistatuscheck.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →