LIVE ENDPOINT
https://gpu.blog/api/mcp
Connect to this endpoint to inspect the live schema for search_gpus and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT 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.gpu-blog]
url = "https://gpu.blog/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"gpu-blog": {
"type": "http",
"url": "https://gpu.blog/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: gpu-blog
Remote MCP URL: https://gpu.blog/api/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": {
"gpu-blog": {
"url": "https://gpu.blog/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"gpu-blog": {
"type": "http",
"url": "https://gpu.blog/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "gpu-blog",
"transport": "streamable-http",
"url": "https://gpu.blog/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_gpu— Full specifications for one GPU by slug — architecture, memory, throughput at each precision, power, physical form, interconnect.find_pricing— Current rental offers, cheapest first, each with the source URL it was read from and when.compare_gpus— Put two or more GPUs side by side with their headline specifications and cheapest current offer.list_vendors— Every cloud provider in the index, with how many GPUs each rents.