General Tools
pickgpu.com
Provides GPU benchmarks, pricing, and comparison data for selecting or analyzing GPUs.
ENDPOINT 1
https://pickgpu.com/mcp
MCP server metadata
- Name
- PickGPU
- Version
- 1.0.0
Known tools 5
get_top_picksReturns GPUs on the price/performance efficiency frontier, sorted highest-performance first.
Inferred read-onlycompare_gpusSide-by-side comparison of two GPUs: benchmark scores at every resolution, specs, current prices, and a value verdict.
Inferred read-onlyget_price_historyHistorical price data for a specific GPU — daily prices over time for new and used conditions.
Inferred read-onlyget_gpu_detailsGet full specs, benchmark scores (raster and ray tracing at 1080p/1440p/4K), current prices, and value context for a specific GPU.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pickgpu]
url = "https://pickgpu.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pickgpu": {
"type": "http",
"url": "https://pickgpu.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pickgpu
Remote MCP URL: https://pickgpu.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pickgpu": {
"url": "https://pickgpu.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pickgpu": {
"type": "http",
"url": "https://pickgpu.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pickgpu",
"transport": "streamable-http",
"url": "https://pickgpu.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for pickgpu.com was fetched 2026-08-23T11:02:35.950Z and is being refreshed.
pickgpu.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.