api.exascale.build
https://api.exascale.build/mcp
68
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (1)
| medium | Capabilities are listable without authentication, including 6 whose names suggest state change (describe_ai_infrastructure_equipment_trade_v1, describe_ai_infrastructure_trade_v1, describe_robotics_trade_v1, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | a535ef4b49e512c8… |
| http_response_observation | 2d ago | cd053f09b073dd7e… |
| availability_observation | 2d ago | 636afc4b4219983a… |
| tls_certificate_observation | 2d ago | b9b7697723940c02… |
| oauth_metadata_observation | 2d ago | 28bf3086817b55b2… |
| mcp_protocol_observation | 2d ago | 470880cdbf5af080… |
| mcp_capability_observation | 2d ago | cbedf036e308b1c9… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.exascale.build to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.