Skills/npm/gpufinder

gpufinder@0.1.2

VERIFIED

Publisher claims: "GPU prices, observed stock and seven-day availability history. Read-only; free API key." Observed in sandbox: calls gpufinder.dev only, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher gpufinder · publishing for 27 daysInstalls 0Last detonated 1 h ago
$claude mcp add gpufinder -- npx -y gpufinder
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
GPUFINDER_API_KEYConfiguration, not credentials: GPUFINDER_DEBUG, GPUFINDER_MCP_URL
Where it talks to
gpufinder.dev (its own)
What we saw when it ran
no credential files read · reached only gpufinder.dev (its own)
What we could not test
what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for GPUFINDER_API_KEY and talks to gpufinder.dev. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind.

$vet-skills run --secrets GPUFINDER_API_KEY=gpufinder.dev -- npx -y gpufinder

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-20 and scored it 91/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: calls gpufinder.dev only, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 20 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
20snetworkCONNECT tcp://gpufinder.dev:443
20snetworkCONNECT tcp://gpufinder.dev:443
20snetworkCONNECT tcp://gpufinder.dev:443
20snetworkCONNECT tcp://gpufinder.dev:443
20sclaimed9 tools: list_gpus, list_providers, get_prices, get_availability, get_price_history, get_data_status, get_market_snapshot, get_usage, get_more_tools
20stoolsacece5c309c6e912
20stools975fd859fc5c9488
20stools8d5024ec785e8e59
20stools89fb036e64a6d8be
20stoolsca567fc49e7e5c04
20stools0397bf95d0b5653e
20stoolsdc1cb1a5b09f341b
20stools6adfe0e4454581e9
20stools71a3e5ac54c68dd8
20sprocessscript backend runs setup only
20sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagedist/cli.js:9 · npx invocation of non-well-known package — may execute untrusted codenpx gpufinder --version Print the versionFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/cli.js:8 · npx invocation of non-well-known package — may execute untrusted codenpx -y gpufinder mcp Start the GPU Finder MCP server over stdio (for Claude, Cursor, VS Code, Cline…)Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈69 tok
1 file · 6 in bundle
Tool list per prompt
≈3,584 tok
9 tools · 398 per tool
Handshake
900 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 320

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for gpufinder@0.1.2 as of 47 min ago. This is the package itself, not its dependencies.

gpufinder@0.1.2 safety verdict: Verified — KillerSkills