mcp.deeprecall.io
https://mcp.deeprecall.io/mcp
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 5f6b5b798567040a… |
| http_response_observation | 2d ago | 778600b3e69a6a3f… |
| availability_observation | 2d ago | 948a6feeaa9bbcaf… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 3e6ae1a3f6ecf80c… |
| oauth_metadata_observation | 2d ago | aa53e8baf8abfdc4… |
| mcp_protocol_observation | 2d ago | 8fad1fb6e54d3158… |
| mcp_capability_observation | 2d ago | e46f7ab76a021c60… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.deeprecall.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.