GPUQuant AI Infrastructure

com.gpuquant由 gpuquant.com 发布官方发布者v1.0.1更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行数据与分析商业与电商

概览

AI 生成的概览

一个托管的只读 MCP 服务器,用于检索 GPUQuant 有来源的 AI 基础设施记录,并查看设施与公司的证据。

可以做什么
按设施或公司名称、slug、运营商、地区或国家代码检索已发布的基础设施记录,仅支持字面文本搜索和有限分页。按 slug 读取单个设施,包括规范链接、有来源的事实和实际核验日期。读取一家公司及一页已发布的供应商、客户、所有权、投资或设施关系。结果会链接回 GPUQuant 记录及其支撑来源,并保留核验日期和未知值。
适用场景
当助手需要关于 AI 基础设施站点或其背后公司的有来源研究背景时适用,例如运营商、状态、产能声明或供应链关系,并且需要区分已核验事实与仅被报道或未知的信息。
运行要求
通过 Streamable HTTP 连接的远程 MCP 端点,无需 API 密钥或凭据。仓库中的可选冒烟测试脚本需要 Node.js 20 或更高版本。需要能访问该托管服务的网络。
安装前请注意
只读:不进行交易,也不提供投资建议,且不提供授权数据源、交易账户、订单、图像或原始来源摘录。日期描述的是底层记录,检索时间戳并不等于重新核验;缺失值保持未知,来源的日期或范围可能不同。已宣布、在建和运营产能是不同的声明。数据及链接来源各自适用其条款。

安装

在 SourceWeft 中

  1. 打开 控制台中的 GPUQuant AI Infrastructure,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.gpuquant%2Finfrastructure/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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

来源:README.md,提交 17a7e08

工具

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.

输入参数kindlimitquery必填offset

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.

输入参数slug必填

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.

输入参数slug必填limitoffsetrelationship

版本历史

1
  1. v1.0.1最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分