Public, source-opaque reference-rate SDKs and MCP server for FLOPS compute price
Public, source-opaque reference-rate SDKs and MCP server for FLOPS compute price indices — every value carries a verify URL.
active Production-safe Score 93/100 http no auth
At a glance
| Endpoint | https://app.flopsindex.com/mcp |
|---|---|
| Source | https://github.com/zeroatflops/flopsindex |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-07-31 21:14:18 |
| Last checked | 2026-11-17 21:52:38 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 489 / 747 ms |
| Last successful check | 2026-11-17 21:52:38 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
list_indices— List all public FLOPS compute-price indices. Returns {count, indices[]} where each row is {index_id, family, value, unit, as_of, confidence,verify— Check a FLOPS index value against the published index. Pass `value` with a number you are about to cite (or already hold) and the response tget_price— Fetch the current published value for a FLOPS compute price index. Returns {value, unit, as_of, data_tier, confidence, verify_url, citation_search_indices— Resolve 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 SPOget_index— Resolve a FLOPS index to its source-opaque PUBLIC citation payload. Returns exactly {index_id, value, unit, as_of, data_tier, confidence, meshare_feedback— Optional. Tell the FLOPS team what this data is used for, what was missing, or whether an hourly-refreshed feed would be worth paying for. W
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:52:38 | ✓ | ✓ | 705 ms | 90 | active |
| 2026-11-17 21:37:26 | ✓ | ✓ | 500 ms | 90 | active |
| 2026-11-17 21:22:12 | ✓ | ✓ | 865 ms | 90 | active |
| 2026-11-17 21:07:00 | ✓ | ✓ | 607 ms | 90 | active |
| 2026-11-17 20:51:51 | ✓ | ✓ | 452 ms | 90 | active |
| 2026-11-17 20:36:50 | ✓ | ✓ | 440 ms | 90 | active |
| 2026-11-17 20:21:49 | ✓ | ✓ | 441 ms | 90 | active |
| 2026-11-17 20:06:47 | ✓ | ✓ | 542 ms | 90 | active |
| 2026-11-17 19:51:00 | ✓ | ✓ | 678 ms | 90 | active |
| 2026-11-17 19:35:51 | ✓ | ✓ | 543 ms | 90 | active |
| 2026-11-17 19:20:41 | ✓ | ✓ | 639 ms | 90 | active |
| 2026-11-17 19:05:28 | ✓ | ✓ | 433 ms | 90 | active |
| 2026-11-17 18:50:08 | ✓ | ✓ | 631 ms | 90 | active |
| 2026-11-17 18:34:52 | ✓ | ✓ | 494 ms | 90 | active |
| 2026-11-17 18:19:50 | ✓ | ✓ | 534 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://app.flopsindex.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/app-flopsindex-com-mcp # JSON