atx/registry

mcp.inboxguard.io

https://mcp.inboxguard.io/mcp

75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago

Why this score

oauth_metadata_present+14
tls_present_and_valid+12
mcp.unauthenticated_consequential_tools-8
reachable+6
mcp_capabilities_discoverable+4
headers.missing_hsts-3

Findings (2)

mediumCapabilities are listable without authentication, including 3 whose names suggest state change (create_notification_channel, create_share_link, remove_domain) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d agof2ceaf580db16398…
http_response_observation2d ago488fce67ec71f8d7…
availability_observation2d ago6347ef07ece5228d…
tls_certificate_observation2d agoc4af687d96431e25…
oauth_metadata_observation2d ago57aa9123cc0c721e…
mcp_protocol_observation2d ago0cfe9966c7217376…
mcp_capability_observation2d ago95d6bd5a5f641a61…

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

Operate this service?

Prove control of mcp.inboxguard.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →