atx/registry

outagedeck.com/api

https://outagedeck.com/api/mcp

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 7d ago

Why this score

oauth_metadata_present+14
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (2)

mediumCapabilities are listable without authentication, including 3 whose names suggest state change (add_custom_provider, remove_custom_provider, update_custom_provider) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation7d ago27f53e7b553943c8…
http_response_observation7d agod657699ccad53cf1…
availability_observation7d ago001c66fc006c47eb…
hosting_provider_observation7d ago07b610f7cd67ffa2…
tls_certificate_observation7d agofa584ce3ffcaa70a…
oauth_metadata_observation7d agod189a63d232d7b27…
mcp_protocol_observation7d agob49a9e75ba7840ca…
mcp_capability_observation7d ago64cd2d80337b855a…

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

Operate this service?

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

Claim this profile →