Skip to content
Official MCP RegistryListed

FLOPS Index

Part ofFLOPS Indexlisted on 2 directories

GPU rental reference prices (spot, on-demand, DePIN), key-free; every value carries a verify URL.

First seen 2 Oct 2026. Evidence as of 6 Nov 2026.

6
Tools
From an anonymous probe
1
Source listings
Each with its own history
20
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
get_indexResolve a FLOPS index to its source-opaque PUBLIC citation payload. Returns exactly {index_id, value, unit, as_of, data_tier, confidence, methodology_url, verify_url, citation_url, permalink} — no source-level detail. Prefer get_index when you intend to CITE the value.Read-only
get_priceFetch the current published value for a FLOPS compute price index. Returns {value, unit, as_of, data_tier, confidence, verify_url, citation_url}. Cheapest way to answer 'what is the latest public reference price for X?' (refreshed every 6 hours). Confidence is a label (HIGH or MED; LOW only for a labelled thin-market index, with publication=thin_market), never a numeric weight. Carries no methodology or source attribution by design — the anonymous surface does not enumerate the tiers or families it withholds.Read-only
list_indicesList all public FLOPS compute-price indices. Returns {count, indices[]} where each row is {index_id, family, value, unit, as_of, confidence, change_24h, delayed}. Use this to discover available indices before calling get_price or verify. No auth required.Read-only
search_indicesResolve a free-text query to canonical FLOPS index slugs. Use when you don't know the exact slug — e.g. 'H100 spot' returns the matching SPOT family entries. Best paired with get_price to look up + quote a value in one turn.Read-only
share_feedbackOptional. Tell the FLOPS team what this data is used for, what was missing, or whether an hourly-refreshed feed would be worth paying for. Would you or your user pay for fresher FLOPS data? If not, why not (field why_not)? Only include what your user is comfortable sharing; no personal details. Nothing is sold or charged.Changes data
verifyCheck a FLOPS index value against the published index. Pass `value` with a number you are about to cite (or already hold) and the response tells you whether it is right: `verified` true/false, `expected` (what you submitted), `actual_value` (what FLOPS publishes) and `delta_pct`. Omit `value` to simply look up the current published value — then `verified` is null, which means 'not checked', NOT 'correct'. Without an API key you are checked against the public value, which is rounded to 2 decimals and delayed onto a 6-hour grid, so a full-precision real-time number will not match anonymously. No source list or source-count is exposed.Read-only

Change history

  1. share_feedback: input schema changed (+why_not)
  2. share_feedback: description changed (+"Would you or your user pay for fresher FLOPS data? If not, why not (field why_not)?")
  3. share_feedback: tool added
  4. get_price: description changed (+"MED; LOW only for a labelled thin-market index, with publication=thin_market)," -"MED),")
  5. verify: title changed
  6. verify: input schema changed
  7. verify: annotations changed
  8. search_indices: title changed
  9. search_indices: annotations changed
  10. list_indices: title changed
  11. list_indices: annotations changed
  12. get_price: title changed
  13. get_price: description changed (+"is the latest public reference price for X?' (refreshed every 6 hours)." -"does X trade at right now?'")
  14. get_price: annotations changed
  15. get_index: title changed
  16. get_index: annotations changed
  17. Website changed from "https://flopsindex.com" to "https://app.flopsindex.com/i/" (registry)
  18. MCP URL changed (registry)
  19. Name changed from "FLOPS Compute Intelligence" to "FLOPS Index" (registry)
  20. Description changed (registry)
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.zeroatflops/flopsindex-mcp2 Oct 20266 Nov 20262