mcp.reply.io
https://mcp.reply.io/
96
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 |
| mcp_requires_authentication | +10 |
| reachable | +6 |
| hsts_enabled | +4 |
Findings (0)
No findings from the current evidence set.
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | efca8b41cd4ccdb0… |
| http_response_observation | 2d ago | 2b52a5aa8cb2718d… |
| availability_observation | 2d ago | 3c11a2eac16d8d21… |
| tls_certificate_observation | 2d ago | b354e90b88fe82a2… |
| oauth_metadata_observation | 2d ago | 1636cad97278e23a… |
| 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 mcp.reply.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.