GPUQuant MCP
Give your AI agent access to GPUQuant’s sourced infrastructure records through the Model Context Protocol. Find facilities, inspect published facts and follow company relationships back to their sources.
Add this URL in your client’s remote MCP server settings. No credentials are required.
https://gpuquant.com/api/mcp
Use an MCP client that supports remote HTTP transport. In VS Code, add the following server to .vscode/mcp.json, start it from the file’s server controls, and enable its tools in agent chat.
{
"servers": {
"gpuquant": {
"type": "http",
"url": "https://gpuquant.com/api/mcp"
}
}
}This is the VS Code configuration format. Other clients may use different keys for the same URL.
The server uses the official MCP SDK v2 and supports MCP 2026-07-28 over HTTP, plus legacy clients using the 2025 initialization handshake and Streamable HTTP. Your MCP client handles protocol headers and initialization. The API URL is a protocol endpoint; this page is its human-readable guide.
kind to facilities, companies or all. Queries are 2–160 characters; results include canonical record URLs and slugs.slug: its operator, location, published capacity, status, verification context and supporting source links. Missing facts remain unknown.slug and page through its relationships or sites. Filter relationship by suppliers, customers, holds, heldBy, sites or all.Search and company results default to 10 entries, with a maximum of 25 per request. Pass the returned nextOffset as offset to continue. Your client can call tools/list for the current input schemas.
search_infrastructure
{
"query": "Frankfurt",
"kind": "facilities",
"limit": 5
}Open a returned facility slug with get_facility to read its facts and sources. Facility search also covers other infrastructure site types.
get_facility
{
"slug": "<facility-slug-from-search>"
}Replace the placeholder with a slug from search. Compare published capacity and operating status with the linked evidence.
get_company
{
"slug": "nvidia",
"relationship": "suppliers",
"limit": 10
}Keep confirmed and reported relationships distinct. Use the returned nextOffset to request another page when present.
Coverage follows GPUQuant’s published infrastructure records. Search results are discovery aids; open the detail tools and supporting sources before comparing facilities. The atlas is not a complete inventory of every site or relationship.
Verification dates describe checks of the underlying record, and source dates describe those sources. Fetching a result today does not make an older fact current. Unpublished capacity stays unknown; announced and operating capacity should be kept separate.
This release provides no GPU price or market-feed tool. Licensed Ornn and Silicon Data series, raw source excerpts, images and building geometry are excluded. It cannot access trading accounts, execute orders or provide investment recommendations.