mcp.zencap.ai
https://mcp.zencap.ai/mcp
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 9009011522f13c82… |
| http_response_observation | 1d ago | faf51796818ecade… |
| availability_observation | 1d ago | f5ded428217d2f64… |
| hosting_provider_observation | 1d ago | 32f443b02a0f05d7… |
| tls_certificate_observation | 1d ago | 9b5063d4d70433b3… |
| oauth_metadata_observation | 1d ago | 75df08b8b2e87e77… |
| mcp_protocol_observation | 1d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.zencap.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.