enmente.clinic/api
https://enmente.clinic/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 | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 8h ago | a2a1d6bbb3b88d32… |
| http_response_observation | 8h ago | b5cb4fb942d5d294… |
| availability_observation | 8h ago | d4346de9c6141cda… |
| hosting_provider_observation | 8h ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 8h ago | 99ba2737f828a24d… |
| oauth_metadata_observation | 8h ago | 1868e8c42e295917… |
| mcp_protocol_observation | 8h ago | 868ec3431b2ae2fc… |
| mcp_capability_observation | 8h ago | a2a61de294b1172f… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of enmente.clinic/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.