emem.dev
https://emem.dev/mcp
87
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
| mcp.tool_schema_changed | -3 |
Findings (2)
| low | Input schema changed without a name change: emem_recall mcp.tool_schema_changed @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | 93902e7451c453aa… |
| http_response_observation | 4h ago | 6677323af2d9a204… |
| availability_observation | 4h ago | 2bff87577969351b… |
| tls_certificate_observation | 4h ago | c53a385664c167cc… |
| oauth_metadata_observation | 4h ago | 5c8451b9530f0a18… |
| mcp_protocol_observation | 4h ago | 8fd2a547ead8ad82… |
| mcp_capability_observation | 4h ago | 91bfafe275c6fb16… |
| mcp_capability_drift | 4h ago | 06d832433a2f1fc4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of emem.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.