mcp.memxus.com
https://mcp.memxus.com/mcp
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| oauth_metadata_present | +14 |
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (update) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 40fea26778c12da5… |
| http_response_observation | 1d ago | db88bd0b418a627d… |
| availability_observation | 1d ago | a26c0cbc09666d8a… |
| hosting_provider_observation | 1d ago | f6ca63562d443d49… |
| tls_certificate_observation | 1d ago | b7194508c289b39c… |
| oauth_metadata_observation | 1d ago | d540a99a0b587adb… |
| mcp_protocol_observation | 1d ago | bd914abaa3f21c88… |
| mcp_capability_observation | 1d ago | 7b660dee17126765… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.memxus.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.