api.ref.tools
https://api.ref.tools/mcp
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 | c0a9fa424f338802… |
| http_response_observation | 2d ago | daac9c36cf2a3595… |
| availability_observation | 2d ago | 5cc93d2d117df4d2… |
| hosting_provider_observation | 2d ago | 958411567b2d9bdc… |
| tls_certificate_observation | 2d ago | 045563ecb2e56696… |
| oauth_metadata_observation | 2d ago | 2a44fc1c5fa84e50… |
| 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.ref.tools to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.