openchainbench.com/api
https://openchainbench.com/api/mcp/mcp
61
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 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 82e3efd911a4ce51… |
| http_response_observation | 2d ago | a6b6f5ac9f7ca4ca… |
| availability_observation | 2d ago | d67254612a01a63a… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | 1a1381c86c9d1d2b… |
| oauth_metadata_observation | 2d ago | 4a00d823252cd10e… |
| mcp_protocol_observation | 2d ago | 432a5b87ea38f83f… |
| mcp_capability_observation | 2d ago | 6ac020df04fba152… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of openchainbench.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.