flopsindex-mcp
Server Details
Live GPU compute & inference token price indices for AI agents — 591 reference indices across H100/A100/B200/B300 spot+on-demand, Claude/GPT/Llama token pricing, and more. Every value is methodology-versioned and citable via the /v1/verify handshake.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 5 of 5 tools scored. Lowest: 3.6/5.
Each tool has a distinct purpose: get_index for citation, get_price for current value, list_indices for discovery, search_indices for querying, and verify for validation. No overlap in functionality.
Most tools follow a verb_noun pattern (get_index, get_price, list_indices, search_indices), but 'verify' is a lone verb without a noun suffix, making it slightly inconsistent.
With 5 tools covering discovery, query, retrieval, price lookup, and verification, the count is well-scoped for a read-only index server. No excess or deficiency.
The tool set covers all necessary read operations: listing indices, searching, getting citation payload, getting current price, and verifying values. No obvious gaps for the intended domain.
Available Tools
5 toolsget_indexInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| index_id | Yes | FLOPS index id / slug, e.g. 'FLOPS-H100-OD', 'FLOPS-A100-SPOT'. |
get_priceInspect
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 does X trade at right now?' Confidence is a label (HIGH or MED), never a numeric weight. Carries no methodology or source attribution by design — the anonymous surface does not enumerate the tiers or families it withholds.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | FLOPS index slug. Accepts FLOPS-<MODEL>-OD, FLOPS-<MODEL>-SPOT, FLOPS-<MODEL>-DEPIN, or a bare gpu_model. |
list_indicesInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| family_filter | No | Optional family prefix to filter by (e.g. 'FLOPS-H100' or 'FLOPS-B300'). Case-sensitive substring match. |
search_indicesInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Free-text query (e.g. 'h100 spot' or 'b200 on-demand'). | |
| limit | No |
verifyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| value | No | Optional. The number you want checked, e.g. 2.14. Omit it to do a plain lookup. | |
| index_id | Yes | FLOPS index identifier (e.g. 'FLOPS-H100-OD', 'FLOPS-B300-SPOT'). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
[This comment has been deleted]
ooo
Related MCP Servers
AlicenseAqualityBmaintenanceMonitors brand mentions, citations, sentiment, competitor share of voice, and GEO performance across AI search engines.Last updated1MIT- Alicense-qualityAmaintenanceProvides regulatory and compliance intelligence from free government sources, including rules, recalls, enforcement actions, and comment deadlines, classified by industry and severity.Last updatedMIT
- AlicenseAqualityAmaintenanceCompetitive intelligence platform with 24 tools. Monitor competitor pricing, content, positioning, tech stacks, and AI visibility — track how ChatGPT, Claude, and Gemini rank your brand.Last updated332MIT
- Flicense-qualityCmaintenanceEnables users to monitor and analyze competitor LinkedIn posts, extract insights, generate original post concepts, and create graphics-ready content with metadata.Last updated