mcp

# GPUQuant MCP

Connect an AI agent to sourced AI infrastructure records from [GPUQuant](https://gpuquant.com).

GPUQuant's hosted MCP provides read-only tools for finding infrastructure, inspecting facility facts and checking company relationships. Results link to GPUQuant records and their supporting sources, retaining verification dates and unknown values.

**Connection URL:** `https://gpuquant.com/api/mcp`

**Transport:** Streamable HTTP. No API key is required for this public infrastructure service.

This repository contains connection instructions, the registry manifest and a reproducible HTTP smoke test. The hosted service runs on GPUQuant; cloning this repository does not copy or self-host GPUQuant's database.

## Connect

In an MCP-compatible application's remote-server settings, add the connection URL above. Use the application's own remote MCP support; configuration format varies by client.

For clients using the VS Code `mcp.json` format:

```json
{
  "servers": {
    "gpuquant": {
      "type": "http",
      "url": "https://gpuquant.com/api/mcp"
    }
  }
}
```

See the [GPUQuant connection guide](https://gpuquant.com/mcp) and your client's current MCP documentation. The endpoint supports the current MCP protocol and legacy clients using the 2025 initialization handshake.

## Tools

| Tool | Purpose |
| --- | --- |
| `search_infrastructure` | Find infrastructure records by name or location with bounded pagination |
| `get_facility` | Read a facility's public facts, sources and verification context |
| `get_company` | Read company facts and sourced relationships |

Use `tools/list` to obtain the exact current input schemas. Results include canonical GPUQuant URLs so readers can open the underlying record and report a correction.

## Example questions

- “Find infrastructure records mentioning Copenhagen and show their sources.”
- “What does GPUQuant know about this facility's operator and status, and when was it verified?”
- “Which supply-chain relationships are documented for this company, and which are only reported?”
- “Identify unknown or stale facts before summarizing this company's infrastructure.”

## Coverage and interpretation

The first release focuses on infrastructure records and company relationships. It does not expose licensed Ornn or Silicon Data feeds, trading accounts, orders, imagery, building geometry or raw source excerpts. Dates describe the underlying records or sources; a retrieval timestamp is not a fresh verification of a fact.

Announced capacity, construction and operating capacity are different claims. Missing values remain unknown. Supporting sources may describe different dates or scopes; inspect them before relying on a comparison. The MCP supplies research context and does not place trades or provide investment recommendations.

## Check the connection

Requires Node.js 20 or newer. No packages or credentials are needed:

```sh
node scripts/smoke.mjs
```

The script checks initialization, tool discovery, all three tools against real records, and current-protocol discovery. To test a development endpoint:

```sh
node scripts/smoke.mjs http://localhost:3000/api/mcp
```

## Corrections and connection issues

- [Report an incorrect infrastructure record](https://github.com/gpuquant/atlas/issues/new?template=correction.yml).
- [Report an MCP connection issue](https://github.com/gpuquant/mcp/issues/new?template=bug.yml).
- [Contact GPUQuant](https://gpuquant.com/contact) for data access and partnerships.

The MIT license applies to this repository's original documentation and example code. Data and linked sources retain their own terms. [Methodology](https://gpuquant.com/docs) · [Map](https://gpuquant.com/map) · [Community](https://gpuquant.com/community)