Skip to main content
Glama
Ownership verified

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.

MCP client
Glama
MCP server

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.

100% free. Your data is private.
Tool DescriptionsA

Average 4.2/5 across 5 of 5 tools scored. Lowest: 3.6/5.

Server CoherenceA
Disambiguation5/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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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 tools
get_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.

ParametersJSON Schema
NameRequiredDescriptionDefault
index_idYesFLOPS 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesFLOPS 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
family_filterNoOptional 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
qYesFree-text query (e.g. 'h100 spot' or 'b200 on-demand').
limitNo
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.

ParametersJSON Schema
NameRequiredDescriptionDefault
valueNoOptional. The number you want checked, e.g. 2.14. Omit it to do a plain lookup.
index_idYesFLOPS index identifier (e.g. 'FLOPS-H100-OD', 'FLOPS-B300-SPOT').

Discussions

?
[deleted]May 27, 2026

[This comment has been deleted]

zeroatflops's avatar
zeroatflops15 days ago

ooo

Related MCP Servers

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources