digche.vercel.app/api
https://digche.vercel.app/api/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 | 979d67fcd3b875e7… |
| http_response_observation | 2d ago | 0f9302aaa67a566e… |
| availability_observation | 2d ago | a4edd94d379d753e… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | b10d6dd58bd768b2… |
| oauth_metadata_observation | 2d ago | 7285772b5239ca49… |
| mcp_protocol_observation | 2d ago | fa60f2f5f95a50cc… |
| mcp_capability_observation | 2d ago | e3eb688be19b9f01… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of digche.vercel.app/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.