api.remoet.dev/mcp/oauth
https://api.remoet.dev/mcp/oauth
63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
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 | d185bb71f1a28bd3… |
| http_response_observation | 2d ago | af9e44b8a1eda73a… |
| availability_observation | 2d ago | 29c3cdc8fd0f0993… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 2f5490e83abd8d3d… |
| oauth_metadata_observation | 2d ago | 8b1444033a432e99… |
| 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 api.remoet.dev/mcp/oauth to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.