api.ejentum.com/self-inspect-mcp
https://api.ejentum.com/self-inspect-mcp
76
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 5h 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 | 5h ago | 36eb9584e5128c6a… |
| http_response_observation | 5h ago | 3b6c8a57416d99a5… |
| availability_observation | 5h ago | 63253c0a638a44bf… |
| tls_certificate_observation | 5h ago | ae7838fb5ef1acfc… |
| oauth_metadata_observation | 5h ago | 839a40c4fb15b5da… |
| mcp_protocol_observation | 5h ago | 917d8a8a7aec90a8… |
| mcp_capability_observation | 5h ago | 22bf6969f17ece49… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.ejentum.com/self-inspect-mcp to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.