GPUvec
REMOTE · GPUVEC.COM
Compare GPU specs and cloud rental offers, check CUDA support, and estimate Qdrant resources.
Available components
Last scanned (17 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 4 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 614 tokens (~68/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 65
First indexed and scored.
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 4 Nov 2026 · Probed https://gpuvec.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gpuvec.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 1da0ac6671db19850eafd3f3e0944e8e |
| SANs: gpuvec.com, *.gpuvec.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gpuvec.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gpuvec.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gpuvec.com/mcp | Verified | 200 | |
| http (plaintext) | http://gpuvec.com/mcp | HTTPS enforced | 301 | https://gpuvec.com/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 →
compare_accelerators ~37
Compare 2–4 distinct exact models side by side; no invented performance score or compatibility ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
compute_capability ~75
Retrieve source-backed NVIDIA CUDA hardware compute capability context; non-CUDA is not assigned a CC. No toolkit/framework guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| search | string | – | – |
| segment | string | – | – |
| status | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
estimate_qdrant ~43
Calculate deterministic Qdrant capacity using the site's shared real engine. KiB inputs, byte outputs; not measured capacity or QPS sizing.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_offers ~149
Find recorded offers with bounded price/count/VRAM filters. Unknown units, scope or counts never pass numeric filters. Billing is a case-insensitive substring; availability is recorded, not live.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | – | – |
| billing_model | string | – | – |
| limit | integer | – | – |
| max_instance_price_per_hour | – | – | – |
| max_price_per_gpu_hour | – | – | – |
| min_gpu_count | – | – | – |
| min_vram_per_gpu | – | – | – |
| min_vram_total | – | – | – |
| model | string | – | – |
| offset | integer | – | – |
| provider | string | – | – |
| sort | string | – | – |
| source_backed_only | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_accelerator ~35
Get one exact accelerator model or canonical slug. Unknown models are errors, not guessed specifications.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_accelerators ~59
List recorded accelerator specifications, with units, field provenance and unknowns. At most 50 per page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| manufacturer | string | – | – |
| offset | integer | – | – |
| search | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_price_history ~75
Read actual approved GPU price observations, newest first. UTC dates filter capture time; distinct configurations are not one price trend.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | – |
| limit | integer | – | – |
| model | string | – | – |
| offset | integer | – | – |
| provider | string | – | – |
| start | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_providers ~49
List GPU compute services with field-scoped official provenance, independent of priced offers and live stock.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| search | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_qdrant_pricing ~55
List dated official managed Cloud package quotes, not live prices or hardware recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| provider | string | – | – |
| region | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the GPUvec MCP server?
GPUvec is a hosted endpoint at https://gpuvec.com/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 · gpuvec.com
claude mcp add --transport http abdelkareemkobo-gpuvec 'https://gpuvec.com/mcp'
What is the GPUvec MCP server?
GPUvec is an MCP server listed in the public MCP registry as io.github.abdelkareemkobo/gpuvec. Compare GPU specs and cloud rental offers, check CUDA support, and estimate Qdrant resources. This page covers its hosted endpoint (https://gpuvec.com/mcp).
Is the GPUvec MCP server safe to use?
GPUvec scores 66 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 GPUvec MCP server expose?
GPUvec exposes 9 tools: list_accelerators, get_accelerator, compare_accelerators, list_providers, find_offers, and 4 more. Their descriptions and schemas cost roughly 577 tokens of context every time the server is loaded.
Does the GPUvec MCP server require authentication?
No. We connected to GPUvec without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GPUvec MCP server still maintained?
GPUvec is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.