emailens.dev/api
https://emailens.dev/api/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 8h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | Capability set changed: +4 / -0 mcp.capability_set_changed @ 1.0.0 |
Evidence (9)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 8h ago | 801c0b15b83c4cb1… |
| http_response_observation | 8h ago | f62ba577ab263f0d… |
| availability_observation | 8h ago | 7d59fe4a9983df9a… |
| hosting_provider_observation | 8h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 8h ago | ff55f29dd3a554c6… |
| oauth_metadata_observation | 8h ago | 6b593d2c57d46f1f… |
| mcp_protocol_observation | 8h ago | a7c7189cae14c40e… |
| mcp_capability_observation | 8h ago | 8f97cb61a8508166… |
| mcp_capability_drift | 8h ago | 9e1fca1d8ca43c21… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of emailens.dev/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.