mcp.remem.me
https://mcp.remem.me/mcp
69
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 3f12a49448cebce4… |
| http_response_observation | 2d ago | 2d67275a9df32d94… |
| availability_observation | 2d ago | 06f3ed3741c7324c… |
| tls_certificate_observation | 2d ago | 0475f3f343902b0b… |
| oauth_metadata_observation | 2d ago | 03d603818cd43b33… |
| mcp_protocol_observation | 2d ago | d76b2a45df4e3847… |
| mcp_capability_observation | 2d ago | 817d92d6aa4079f5… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.remem.me to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.