mcp.example4.ai
https://mcp.example4.ai/mcp
76
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | dc945a5c8b1ae60b… |
| http_response_observation | 2d ago | cee7f460623e3b5e… |
| availability_observation | 2d ago | d071e332a8999c4d… |
| tls_certificate_observation | 2d ago | 33a62062d2b0f82b… |
| oauth_metadata_observation | 2d ago | f2d34145c3db08fb… |
| mcp_protocol_observation | 2d ago | d2777d97552fcab5… |
| mcp_capability_observation | 2d ago | 13177e3c83c6833f… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.example4.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.