@inferra-trade/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFERRA_API_KEY | Yes | Required for every tool; `ink_…` from https://api.inferra.trade | |
| INFERRA_API_URL | No | A self-hosted index, or a test stub | https://api.inferra.trade |
| INFERRA_TIMEOUT_MS | No | Per request timeout | 10000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_gpu_priceA | Current rental price of one GPU model in USD per GPU-hour from the Inferra GPU Index, with the timestamp, whether the value is delayed, the model state (live / warming / halt), the number of sources behind it and whether it is attested on Solana mainnet. A halted model returns no price. Models: A100, H100, H200, B200. |
| compare_gpu_pricesA | Compare current rental prices per GPU-hour across models, cheapest first, with each model's multiple of the cheapest one. Omit |
| get_gpu_market_summaryA | One-call overview of the GPU rental market: every model's current price per GPU-hour, its 7-day change and weekly range, how many sources price it, whether its on-chain feed is fresh, plus the health of the index itself (computation, on-chain feeds, Chainlink delivery, API) and the biggest mover of the week. Use this first when asked "what do GPUs cost right now". |
| get_gpu_price_historyA | Price history of one model in USD per GPU-hour over a range (1d, 3d, 7d, 14d, 30d, 90d, 1y, all), with the first and last value, the change, the low and the high, and a thinned list of points. The Free API tier sees 30 days; longer ranges are clamped and the answer says so. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: single-model current price, cross-model price comparison, full market overview, and historical price trends. No two tools overlap in what they return, making misselection unlikely.
Three of four tools follow the 'get_gpu_*' pattern, while 'compare_gpu_prices' uses a verb-object form without 'get'. This is a minor deviation, but the naming is otherwise predictable and readable.
Four tools is well-scoped for a GPU price index server: current price, comparison, summary, and history cover the main use cases without unnecessary redundancy.
The tool surface covers the core lifecycle of price queries (individual, comparative, overview, history). A minor gap is the lack of a dedicated endpoint to list available models, though the summary and comparison tools implicitly provide this information.