GPU Finder
REMOTE · GPUFINDER.DEV · 2 COMPONENTS
GPU prices, observed stock and seven-day availability history. Read-only; free API key.
Available components
Last scanned (9 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1029 tokens (~114/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +3
- The server now declares the “resources” capability functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- Schema quality: excellent → good functional
- New prompt “find_gpu_rental” functional
- New resource “pricing-and-stock” functional
- 1 Nov 26 0
- Tool “get_market_snapshot” rewrote its description, which is the text the model reads security
- Schema quality: 112 → 125 ▼ functional
- “get_market_snapshot” added an optional parameter “provider” cosmetic
- “get_market_snapshot” added an optional parameter “region” cosmetic
- 30 Oct 26 +3
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Tool “get_prices” rewrote its description, which is the text the model reads security
- Tool “get_usage” rewrote its description, which is the text the model reads security
- Tool “list_gpus” rewrote its description, which is the text the model reads security
- Tool “list_providers” rewrote its description, which is the text the model reads security
- Tool “get_availability” rewrote its description, which is the text the model reads security
- Tool “get_data_status” rewrote its description, which is the text the model reads security
- Tool “get_market_snapshot” rewrote its description, which is the text the model reads security
- Tool “get_price_history” rewrote its description, which is the text the model reads security
- Schema quality: 126 → 112 ▲ functional
- Tool “get_prices” changed its title: Compare GPU prices cosmetic
- Tool “list_gpus” changed its title: List GPU models cosmetic
- Tool “list_providers” changed its title: List GPU providers cosmetic
- Tool “get_usage” changed its title: Check account usage cosmetic
- Tool “get_availability” changed its title: Check GPU availability cosmetic
- Tool “get_data_status” changed its title: Check data freshness cosmetic
- Tool “get_market_snapshot” changed its title: Find the cheapest available GPU cosmetic
- Tool “get_price_history” changed its title: View GPU price history cosmetic
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://gpufinder.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gpufinder.dev | CN=YR2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 625398cb06c658d6a65d5c0285457132270 |
| SANs: gpufinder.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gpufinder.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| gpufinder.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://gpufinder.dev/.well-known/oauth-protected-resource/mcp", scope="gpu:read", error="invalid_token", error_description="Connect your GPU Finder account or provide a valid API key"
Bearer resource_metadata="https://gpufinder.dev/.well-known/oauth-protected-resource/mcp", scope="gpu:read", error="invalid_token", error_description="Connect your GPU Finder account or provide a valid API key"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://www.googletagmanager.com; font-src 'self'; connect-src 'self' https://www.google-analytics.com https://analytics.google.com https://region1.google-analytics.com https://www.googletagmanager.com https://raw.githubusercontent.com https://vitals.vercel-insights.com https://va.vercel-scripts.com; frame-src 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://gpufinder.dev/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://gpufinder.dev/mcp |
| Authorisation server | https://gpufinder.dev/api/developer/auth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gpufinder.dev/mcp | Verified | 200 | |
| http (plaintext) | http://gpufinder.dev/mcp | HTTPS enforced | 308 | https://gpufinder.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_availability Check GPU availability ~164
Show day-by-day stock for one GPU model over the last seven days, per provider and node size: available configuration-hours versus known configuration-hours each day, summed across tracked instances. Optionally limit to one provider. Reports observed availability history, not provider uptime or launch guarantees. Days without observations are unknown, not zero. Pages default to 20 rows, maximum 100; each page costs one data unit.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | yes | GPU model name, case-insensitive, e.g. "H100", "RTX 4090". See list_gpus. |
| page | object | – | Pagination. Omit for the first page. |
| provider | string | – | Provider name or slug, e.g. "runpod", "lambda". See list_providers. |
No output schema declared.
No examples provided.
get_data_status Check data freshness ~64
Report 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. Includes timestamps for assessing data staleness. Costs one data unit; it is not an anonymous health check.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market_snapshot Find the cheapest available GPU ~240
Check a GPU configuration once or in a client-scheduled availability watch: cheapest listed and freshly observed in-stock offers for one GPU model and exact GPU count, with whole-node/per-GPU hourly USD price, observation time, provider and region. Optional provider and exact provider-reported region filters run before regional aggregation and are echoed in filters. Compare snapshots in client-owned state; ignore timestamp-only changes. The server does not schedule checks or send notifications. One data unit per call; get_usage is free. Stock is not a launch guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | GPUs per node. Prices are for the whole node. Defaults to 1. |
| gpu | string | yes | GPU model name, case-insensitive, e.g. "H100", "RTX 4090". See list_gpus. |
| provider | string | – | Provider name or slug, e.g. "runpod", "lambda". See list_providers. |
| region | string | – | Exact provider-reported region, case-insensitive (e.g. Japan or eu-north1). Obtain labels from get_prices. Not a broad Europe/Asia filter or a placement guarantee. |
No output schema declared.
No examples provided.
get_price_history View GPU price history ~162
Show 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. Pages default to 20 rows, maximum 100; each page costs one data unit. Reuse the same filters and page limit with nextCursor.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | GPUs per node. Prices are for the whole node. Defaults to 1. |
| gpu | string | yes | GPU model name, case-insensitive, e.g. "H100", "RTX 4090". See list_gpus. |
| months | integer | – | UTC months of history per provider, 1-12. Defaults to 12. |
| page | object | – | Pagination. Omit for the first page. |
No output schema declared.
No examples provided.
get_prices Compare GPU prices ~144
List 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. Prices reflect collected data, not a live capacity guarantee. Pages default to 20 rows, maximum 100; each page costs one data unit.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | GPUs per node. Prices are for the whole node. Defaults to 1. |
| gpu | string | yes | GPU model name, case-insensitive, e.g. "H100", "RTX 4090". See list_gpus. |
| page | object | – | Pagination. Omit for the first page. |
No output schema declared.
No examples provided.
get_usage Check account usage ~51
Show this account's usage across REST and MCP: plan allowance, units used and remaining, and UTC reset times. Spends no monthly units and works after the monthly allowance is exhausted, but is still rate limited.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_gpus List GPU models ~86
List 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. Returns canonical GPU identifiers and hardware specifications. Pages default to 20 rows, maximum 100; each page costs one data unit.
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | – | Pagination. Omit for the first page. |
No output schema declared.
No examples provided.
list_providers List GPU providers ~93
List 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. Returns canonical provider identifiers and provider-level summaries. Pages default to 20 rows, maximum 100; each page costs one data unit.
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | – | Pagination. Omit for the first page. |
No output schema declared.
No examples provided.
How do I install the GPU Finder MCP server?
GPU Finder is a hosted endpoint at https://gpufinder.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gpufinder.dev
claude mcp add --transport http dev-gpufinder-gpufinder 'https://gpufinder.dev/mcp'
What is the GPU Finder MCP server?
GPU Finder is an MCP server listed in the public MCP registry as dev.gpufinder/gpufinder. GPU prices, observed stock and seven-day availability history. Read-only; free API key. This page covers its hosted endpoint (https://gpufinder.dev/mcp).
Is the GPU Finder MCP server safe to use?
GPU Finder scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GPU Finder MCP server expose?
GPU Finder exposes 8 tools: list_gpus, list_providers, get_prices, get_availability, get_price_history, and 3 more. Their descriptions and schemas cost roughly 1,004 tokens of context every time the server is loaded.
Does the GPU Finder MCP server require authentication?
Yes. GPU Finder asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the GPU Finder MCP server still maintained?
GPU Finder is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.