api.rtcstats.com/v1.0
https://api.rtcstats.com/v1.0/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 3h ago | 5b901247e91617fa… |
| http_response_observation | 3h ago | f87959d58ff7d636… |
| availability_observation | 3h ago | 44beca55971e1e34… |
| hosting_provider_observation | 3h ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 3h ago | 522147670315a4f3… |
| oauth_metadata_observation | 3h ago | e13cbc8e4011c8e2… |
| mcp_protocol_observation | 3h ago | fb2ac0ee833733f9… |
| mcp_capability_observation | 3h ago | d9405ed023effd4e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.rtcstats.com/v1.0 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.