build.avax.network/api
https://build.avax.network/api/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 7d ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (cli_lookup_command) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7d ago | 2e7a9c262643a99c… |
| http_response_observation | 7d ago | 39383165001c6ad8… |
| availability_observation | 7d ago | 24cd933f5ccbf483… |
| hosting_provider_observation | 7d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 7d ago | a8e0f55ea7c64124… |
| oauth_metadata_observation | 7d ago | d8a3ed890303f1bb… |
| mcp_protocol_observation | 7d ago | b0159c5481c28fb3… |
| mcp_capability_observation | 7d ago | 26c2b3a618168f92… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of build.avax.network/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.