MCP QUEEN
build.exascale/osint A
Source-cited US machine-economy data: power, AI infra, chips, robot trade + adoption, satellites.
Cloud & Infrav1.1.6streamable-httpapi.exascale.build
Grade evidence — probed 2026-07-12 21:01 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1000ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo exascale.build@1.27.2 |
| tooling | 35 / 35 | tools/list OK: 50 tools e.g. "list_capabilities_v1"; 50/50 described, 50/50 fully-typed schemas, median description 619 chars |
| latency | 7 / 10 | initialize round-trip 1000ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.1.6; namespace build.exascale matches endpoint/repo |
Score 94/100 · latency 1000ms · 50 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http osint https://api.exascale.build/mcp
Generic MCP client config:
{ "mcpServers": { "osint": { "type": "http", "url": "https://api.exascale.build/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/build.exascale/osint · referral link https://mcpqueen.com/go/build.exascale/osint (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/build.exascale/osint)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 21:01 | A | 94 | 1000ms |