GPU Finder MCP server
Which servers in the official MCP registry are GPU Finder'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-19
- Registry namedev.gpufinder/gpufinderverified in the MCP registry
The registry name sits under gpufinder.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools8
- Server calls itselfgpufinder
- Server versiona6
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 165 ms.
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer501 ms
- Space in an agent's context≈ 1,887 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.
list_gpusList the GPU models GPU Finder tracks: canonical name and slug, VRAM, memory type, bandwidth, interconnect, provider and instance counts, and min/max hourly USD price. Use it to find valid gpu names for the other tools or to compare GPU…
list_providersList GPU cloud providers: name and slug, GPU and instance counts, min/max hourly USD price, egress cost per GB and free egress allowance, website and GPU Finder links, and last update time. Use it to find valid provider slugs or compare…
get_pricesList every provider offer for one GPU model and node size: provider, instance type, region, GPU count, on-demand and spot USD price per whole node hour, links and last update. Use it for the full price table; use get_market_snapshot for…
get_availabilityShow day-by-day stock for one GPU model over the last seven days, per provider and node size: instances observed available versus total each day. Optionally limit to one provider. Use it to judge how reliably a GPU can be found in stock…
get_price_historyShow how one GPU model's price changed month by month per provider: on-demand and spot USD per whole node hour for up to 12 UTC months. Use it for trends; use get_prices for current prices. Pages default to 20 rows, maximum 100; each page…
get_data_statusReport how fresh GPU Finder's data is: when price and availability collection last completed, and each provider's last success, last run, consecutive failures and last error. Use it to decide whether a price or availability answer may be…
get_market_snapshotAnswer "what is the cheapest way to rent this GPU now": the cheapest listed offer and the cheapest offer observed in stock for one GPU model and node size, each with provider, region, whole node and per GPU hourly USD price, availability…
get_usageShow this API key's usage across REST and MCP: plan allowance, units used and remaining, and UTC reset times. Use it before large paginated reads or after a quota_exceeded error. Spends no monthly units and works after the monthly…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"gpufinder": {
"type": "http",
"url": "https://gpufinder.dev/mcp"
}
}
}OpenAPI spec
8 paths, read 2026-10-19. 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.