mcp.filingapi.dev
https://mcp.filingapi.dev/mcp
69
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4d ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| availability_observation | 4d ago | a0b1073db9c20a38… |
| dns_resolution_observation | 4d ago | 1b137b7ae9f1181f… |
| http_response_observation | 4d ago | b12da6b3b0cbd6f7… |
| tls_certificate_observation | 4d ago | 001a4fa59ecf9e93… |
| oauth_metadata_observation | 4d ago | 8a82ea37430ecd7f… |
| mcp_protocol_observation | 4d ago | b17c0cf9a7d6d1bd… |
| mcp_capability_observation | 4d ago | 53bb44bf8fb1f5dc… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.filingapi.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.