xmemo.dev
https://xmemo.dev/mcp
81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 1d1fba9d79fe4e5d… |
| http_response_observation | 2d ago | f37b969baaac27d0… |
| availability_observation | 2d ago | 84b22dfb2fea8b84… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 86974a8f61f7ab39… |
| oauth_metadata_observation | 2d ago | b6f800a6e6714c95… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of xmemo.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.