api.1inch.com/mcp/protocol
https://api.1inch.com/mcp/protocol
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 6h ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | Capability set changed: +1 / -0 mcp.capability_set_changed @ 1.0.0 |
Evidence (9)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 6h ago | b77f5b4d84d5ee58… |
| http_response_observation | 6h ago | 9d939b07119f744c… |
| availability_observation | 6h ago | 8300e676a34d4ed0… |
| hosting_provider_observation | 6h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 6h ago | 2c77e442b8341f85… |
| oauth_metadata_observation | 6h ago | 0cfe83d45077edf8… |
| mcp_protocol_observation | 6h ago | a9945554723eb316… |
| mcp_capability_observation | 6h ago | 2e28636dfee17f0a… |
| mcp_capability_drift | 6h ago | 9996b855e0af12a7… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.1inch.com/mcp/protocol to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.