mcp.reqistry.dev
https://mcp.reqistry.dev/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (submit_api) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 71291426712c6155… |
| http_response_observation | 2d ago | 9570f8f615499beb… |
| availability_observation | 2d ago | 073a10454e6df330… |
| tls_certificate_observation | 2d ago | 35d1c0e72b05cb85… |
| oauth_metadata_observation | 2d ago | 81612c9ff74a66c3… |
| mcp_protocol_observation | 2d ago | 7861a4abd14239e5… |
| mcp_capability_observation | 2d ago | 60250a7096e358f0… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.reqistry.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.