GPUQuant AI Infrastructure

com.gpuquantPublished by gpuquant.comOfficial publisherv1.0.1Updated Oct 24, 2026

Search AI infrastructure, inspect facility evidence and explore sourced company relationships.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A hosted, read-only MCP server for searching GPUQuant's sourced AI infrastructure records and inspecting facility and company evidence.

What you can do
Search published infrastructure records by facility or company name, slug, operator, locality or country code, with bounded pagination and literal text search only. Read a single facility by slug, including its canonical URL, sourced facts and actual verification date. Read a company plus a page of published supplier, customer, ownership, investment or facility relationships. Results link back to GPUQuant records and their supporting sources, keeping verification dates and unknown values visible.
When to use it
Useful when an assistant needs sourced research context on AI infrastructure sites or the companies behind them, such as operators, status, capacity claims or supply-chain relationships, and when it should distinguish verified facts from reported or unknown ones.
Requirements
A remote MCP endpoint over Streamable HTTP; no API key or credentials are required. The optional smoke-test script in the repository needs Node.js 20 or newer. Network access to the hosted service is required.
Before you install
Read-only: it does not place trades or give investment recommendations, and it does not expose licensed data feeds, trading accounts, orders, imagery or raw source excerpts. Dates describe the underlying records, so a retrieval timestamp is not fresh verification; missing values stay unknown and sources may differ in date or scope. Announced, under-construction and operating capacity are distinct claims. Data and linked sources keep their own terms.

Installation

In SourceWeft

  1. Open GPUQuant AI Infrastructure in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.gpuquant%2Finfrastructure/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "gpuquant-ai-infrastructure": {
      "type": "http",
      "url": "https://gpuquant.com/api/mcp"
    }
  }
}

README

GPUQuant MCP

Connect an AI agent to sourced AI infrastructure records from GPUQuant.

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 and your client's current MCP documentation. The endpoint supports the current MCP protocol and legacy clients using the 2025 initialization handshake.

Tools

ToolPurpose
search_infrastructureFind infrastructure records by name or location with bounded pagination
get_facilityRead a facility's public facts, sources and verification context
get_companyRead 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

The MIT license applies to this repository's original documentation and example code. Data and linked sources retain their own terms. Methodology · Map · Community

Source: README.md at commit 17a7e08

Tools

3

search_infrastructure

Search infrastructure

Search published facility and company names, slugs, operators, localities, and country codes. Literal text search with bounded pagination; no arbitrary SQL or URL fetching.

Parameterskindlimitqueryrequiredoffset

get_facility

Get facility evidence

Read one published facility by slug, including canonical URL, sourced facts, and actual verification date. At most 20 source links; no quotes, imagery, geometry, or market series.

Parametersslugrequired

get_company

Get company relationships

Read a company and a page of published supplier, customer, ownership, investment, or facility relationships. Company verification dates are unknown. Each upstream relationship category is capped at 500.

Parametersslugrequiredlimitoffsetrelationship

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts