blame.today
https://blame.today/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1h ago | 17b89ccc0e7d543f… |
| http_response_observation | 1h ago | 0290549f1ef9eee3… |
| availability_observation | 1h ago | 78e7fb28bf5381b1… |
| hosting_provider_observation | 1h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1h ago | 8c8ffb535e2dbb79… |
| oauth_metadata_observation | 1h ago | 79d3db533efd1bbb… |
| mcp_protocol_observation | 1h ago | 327aba5c263657a9… |
| mcp_capability_observation | 1h ago | d6205fd77fa7a8cd… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of blame.today to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.