FastGPU MCP server
Which servers in the official MCP registry are FastGPU's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-13
- Registry nameco.fastgpu/fastgpuverified in the MCP registry
The registry name sits under fastgpu.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-13
- Tools2
- Server calls itselfFastGPU
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 126 ms.
list_gpu_pricesOne entry per GPU model with its cheapest live on-demand cloud rental price in USD per GPU-hour, the provider offering it, and how many providers rent it, from FastGPU's live price feed across marketplaces, neoclouds and hyperscalers…
match_workloadDescribe a job (an open-weight model to serve or fine-tune, a model size, or a GPU need) and get up to eight ranked GPU configurations that can run it at the lowest live price, each with the GPU count, the effective USD per hour for the…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"fastgpu": {
"type": "http",
"url": "https://fastgpu.co/api/mcp"
}
}
}OpenAPI spec
11 paths, read 2026-10-13. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.