rmcp.dev
https://rmcp.dev/mcp
90
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 5d07d417ca66e41f… |
| http_response_observation | 2d ago | 7cf82c08356f593d… |
| availability_observation | 2d ago | 9adeb3142b5263a8… |
| tls_certificate_observation | 2d ago | 9d09068b8be8533b… |
| oauth_metadata_observation | 2d ago | 7c23b9b72cd910c7… |
| mcp_protocol_observation | 2d ago | 492393bf49345283… |
| mcp_capability_observation | 2d ago | b10c5666fd589c90… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of rmcp.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.