Skip to content

FLOPS Index MCP server

io.github.zeroatflops/flopsindex-mcpzeroatflopsstreamable-httpv0.12.5Scanned

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

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the FLOPS Index MCP server can do

The FLOPS Index MCP server is published by the GitHub account zeroatflops. It has 6 tools. It can create or change data (2 tools: verify and share_feedback), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.12.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • share_feedbackOptional.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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. 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.

    Annotations the server declares

    • title: Share feedback with FLOPS (optional)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • verifyCheck a FLOPS index value against the published index.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 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.

    Annotations the server declares

    • title: Verify a FLOPS value
    • readOnlyHint: true
Only reads 4Show 4 read-only tools
  • get_indexResolve a FLOPS index to its source-opaque PUBLIC citation payload.No findings

    Why it is in this group

    • The name "get_index" says "get": a word for reading.
    Description, as the server wrote it
    Resolve 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.

    Annotations the server declares

    • title: Get a FLOPS index citation
    • readOnlyHint: true
  • get_priceFetch the current published value for a FLOPS compute price index.No findings

    Why it is in this group

    • The name "get_price" says "get": a word for reading.
    Description, as the server wrote it
    Fetch 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.

    Annotations the server declares

    • title: Get a FLOPS index price
    • readOnlyHint: true
  • list_indicesList all public FLOPS compute-price indices.No findings

    Why it is in this group

    • The name "list_indices" says "list": a word for reading.
    Description, as the server wrote it
    List 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.

    Annotations the server declares

    • title: List public FLOPS indices
    • readOnlyHint: true
  • search_indicesResolve a free-text query to canonical FLOPS index slugs.No findings

    Why it is in this group

    • The name "search_indices" says "search": a word for reading.
    Description, as the server wrote it
    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 SPOT family entries. Best paired with get_price to look up + quote a value in one turn.

    Annotations the server declares

    • title: Search FLOPS indices
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.flopsindex.com/mcp: tools/list returned 6 tools to an anonymous client, including verify (write), share_feedback (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2

Install

Pinned to version 0.12.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http flopsindex https://app.flopsindex.com/mcp
claude mcp add --transport http flopsindex https://app.flopsindex.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__flopsindex__list_indices",
      "mcp__flopsindex__get_price",
      "mcp__flopsindex__search_indices",
      "mcp__flopsindex__get_index"
    ],
    "ask": [
      "mcp__flopsindex__verify",
      "mcp__flopsindex__share_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as flopsindex. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.zeroatflops/flopsindex-mcp/verify?hash=2fb75c5ef1f0736fef1db5d9d4c90b3dec5eef46828d389451d56883e46db2c4" | jq -e '.changed == false'

Pinned hash 2fb75c5ef1f0, from Nov 20, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.zeroatflops/flopsindex-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.zeroatflops/flopsindex-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.zeroatflops/flopsindex-mcp.svg)](https://radar.anlyon.com/servers/io.github.zeroatflops/flopsindex-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.

FLOPS Index MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FLOPS Index MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FLOPS Index MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FLOPS Index MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FLOPS Index MCP server have?

6 tools: 2 write, 4 read. verify, share_feedback, list_indices, get_price, search_indices and get_index.

Does the FLOPS Index MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FLOPS Index MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FLOPS Index MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.