api.anchor-x402.com
https://api.anchor-x402.com/mcp
66
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| mcp.tool_schema_changed | -3 |
Findings (2)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
| low | Input schema changed without a name change: ledger_report, tldr_text mcp.tool_schema_changed @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | 714bbf89c1fd9def… |
| http_response_observation | 4h ago | 2502d0a9537744e9… |
| availability_observation | 4h ago | fe13a94d35dda9d6… |
| tls_certificate_observation | 4h ago | 01d9b412850e47d4… |
| oauth_metadata_observation | 4h ago | 0fa834d0b6fa8167… |
| mcp_protocol_observation | 4h ago | 3a5e92f9ab01b7d4… |
| mcp_capability_observation | 4h ago | 0b9fcea01fed72bd… |
| mcp_capability_drift | 4h ago | e348d370d7991b30… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.anchor-x402.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.