exascale.build MCP server

exascale.build is an MCP server with 64 tools an agent can call, among them describe_ai_infrastructure_construction_v1, describe_ai_infrastructure_equipment_trade_v1, describe_ai_infrastructure_production_v1. It answers at https://api.exascale.build/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.

Source-cited US machine-economy data: power, AI infra, chips, robot trade + adoption, satellites.

Description as the publisher wrote it.

The 64 tools exascale.build offers

Add exascale.build to your AI client

Every block below points at https://api.exascale.build/mcp. Pick your client and copy.

claude mcp add --transport http exascale-build https://api.exascale.build/mcp

{
  "mcpServers": {
    "exascale-build": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.exascale.build/mcp"]
    }
  }
}

{
  "mcpServers": {
    "exascale-build": {
      "url": "https://api.exascale.build/mcp"
    }
  }
}

{
  "servers": {
    "exascale-build": {
      "type": "http",
      "url": "https://api.exascale.build/mcp"
    }
  }
}

{
  "context_servers": {
    "exascale-build": {
      "url": "https://api.exascale.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "exascale-build": {
      "serverUrl": "https://api.exascale.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "exascale-build": {
      "url": "https://api.exascale.build/mcp"
    }
  }
}

name: exascale.build
version: 0.0.1
schema: v1
mcpServers:
  - name: exascale.build
    type: streamable-http
    url: https://api.exascale.build/mcp

{
  "mcpServers": {
    "exascale-build": {
      "httpUrl": "https://api.exascale.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "exascale-build": {
      "type": "http",
      "url": "https://api.exascale.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "exascale-build": {
      "url": "https://api.exascale.build/mcp"
    }
  }
}

goose://extension?url=https%3A%2F%2Fapi.exascale.build%2Fmcp&type=streamable_http&id=exascale-build&name=exascale.build

Is exascale.build up right now?

It answered our last check on 17 October 2026 in 349 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to exascale.build

Questions about exascale.build

Is there an official exascale.build MCP server?

Yes. It is published by exascale.build and served from api.exascale.build, the vendor's own domain: https://api.exascale.build/mcp.

How many tools does exascale.build have?

64, as returned by the server's own tools/list on 9 September 2026: describe_ai_infrastructure_construction_v1, describe_ai_infrastructure_equipment_trade_v1, describe_ai_infrastructure_production_v1, describe_ai_infrastructure_trade_v1, describe_capability_v1, describe_capacity_factor_v1, describe_natural_gas_prices_v1, describe_power_asset_ownership_v1, and 56 more.

Is exascale.build down?

It answered our last check on 17 October 2026 in 349 ms. Over 10 checks since 4 September 2026 it answered 10.

How do I add exascale.build to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.exascale.build/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does exascale.build need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: build.exascale. Endpoint host: api.exascale.build. ARD identifier: urn:air:build.exascale:mcp:osint. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.