Flopsindex MCP Server

Connect Flopsindex to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Python SDK for FLOPS Index — live GPU compute pricing reference rates. The flopsindex mcp server is what makes that connection.

What the server does

Or to your agent: "Get me the current FLOPS price for an H100 on-demand and show me the verify URL."

• Five key-free tools — — list_indices, search_indices, get_price, get_index, verify. No API key, no signup, no configuration
• Every value carries a verify URL — — check any published number against the index from your own code. verify returns whether a cited value matches
• Spot, on-demand and DePIN — reference prices per chip and market type
• Three vendors — — NVIDIA data-center and workstation GPUs, AMD MI300X, and Intel Gaudi 2. Enumerate the live set via /v2/catalog/public
• Source-opaque by contract — — the value plus citation and verify links, never the inputs behind it
• Delayed onto a ~6h grid — (00/06/12/18 UTC), 2dp values, banded 24h change, label confidence. Indicative reference — not for settlement

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Source — opaque by contract** — the value plus citation and verify links, never the inputs behind it
• Path — What
• Endpoint — What
• Package — Channel
• flopsindex-mcp — pypi.org/project/flopsindex-mcp/

Credentials and setup notes

Configuration is passed through the environment: INDEX_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Flopsindex's toolset — Source, Path, Endpoint and 2 more — is a fair guide to whether it matches your workflow.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.