mcp.releases.sh
https://mcp.releases.sh/mcp
71
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 | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (2)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 4788e9e4dab19815… |
| http_response_observation | 2d ago | 3c002a1d359206be… |
| availability_observation | 2d ago | 844beb78442bc275… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | a2583ae038f1207d… |
| oauth_metadata_observation | 2d ago | 625f2b8c26879fba… |
| mcp_protocol_observation | 2d ago | 902b8f606fe33bda… |
| mcp_capability_observation | 2d ago | ef5fa96c53155642… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.releases.sh to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.