InferIndex
REMOTE · MCP.INFERINDEX.DEV
LLM API prices across 70+ providers: cheapest offer, comparisons, history and cost estimates.
Available components
Last scanned (11 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2759 tokens (~306/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 0
- New tool “provider_ranking” functional
- 18 Oct 26 +1
- Stability: 0.97 → pass security
- 16 Oct 26 +1
- “compare_providers” reworded the description of “sort” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 73. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 0
- Schema quality: 1589 → 2625 ▼ functional
- New tool “gpu_rentals” functional
- New tool “list_gpus” functional
- New tool “self_host_or_api” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.inferindex.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=inferindex.dev | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4106ef29a92df59513cd213b8152ab7e |
| SANs: inferindex.dev, mcp.inferindex.dev, *.mcp.inferindex.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.inferindex.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| inferindex.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.inferindex.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.inferindex.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cheapest Cheapest offers for a model ~508
Cheapest current API offers for one model across direct providers and aggregators, in USD per 1M tokens (input, output, blended 3:1). Stale prices, and flex/batch tiers, are excluded by default. Optional filters (context, tools, JSON, vision, region, no training on prompts, open sign-up) and usage (tokens per request, requests per day) to get an estimated cost per request and per month. Returns the winner in detail and one short line per following offer. A condition that is absent was not published by the provider, it never means "no"; a flag not listed in signals is false.
| Name | Type | Req | Description |
|---|---|---|---|
| cached_ratio | number | – | Share of input tokens served from the provider's prompt cache (0 to 1) |
| detail | string | – | compact (default): the winner in detail and one short line per other offer (provider, prices, signals, training on prompts when published). full: every field of every offer (all published conditions,… |
| include_tiers | string | – | Also include lower-priority service tiers, comma-separated: flex, batch (hidden by default) |
| json | boolean | – | Only offers that support JSON output |
| limit | integer | – | Number of offers to return, winner included (default 5, max 25) |
| min_context | integer | – | Minimum context window in tokens |
| model | string | yes | Model id or name, e.g. 'deepseek-v3.2', 'deepseek/deepseek-v4-pro', 'gpt-5.6-luna'. Use search_models when unsure. |
| no_training | boolean | – | Only providers whose published terms say they do not train on your prompts |
| no_waitlist | boolean | – | Only providers with open sign-up (no waitlist, invitation or country restriction) |
| output_tokens | integer | – | Output tokens per request, for the estimated cost |
| prompt_tokens | integer | – | Input tokens per request, for the estimated cost |
| region | string | – | Only providers that process data in this region: eu, us, … |
| requests_per_day | integer | – | Requests per day, to also get an estimated monthly cost |
| strict | boolean | – | Exclude offers whose provider does not publish the filtered information (by default they are kept and flagged) |
| tools | boolean | – | Only offers that support tool calling |
| vision | boolean | – | Only offers that accept image input |
No output schema declared.
No examples provided.
compare_providers Compare providers for a model ~446
Current offers for one model, one line per provider and source (direct or via an aggregator), cheapest first (10 by default), with price, quantization, signals and training on prompts when published; the cheapest offer comes in detail. Pass detail: "full" for context, every published condition (data regions, sign-up) and reliability from official status pages on each offer.
| Name | Type | Req | Description |
|---|---|---|---|
| cached_ratio | number | – | Share of input tokens served from the provider's prompt cache (0 to 1) |
| detail | string | – | compact (default): the winner in detail and one short line per other offer (provider, prices, signals, training on prompts when published). full: every field of every offer (all published conditions,… |
| include_tiers | string | – | Also include lower-priority service tiers, comma-separated: flex, batch (hidden by default) |
| limit | integer | – | Number of offers to return, cheapest included (default 10, max 50) |
| model | string | yes | Model id or name, e.g. 'deepseek-v3.2', 'deepseek/deepseek-v4-pro', 'gpt-5.6-luna'. Use search_models when unsure. |
| no_training | boolean | – | Only providers whose published terms say they do not train on your prompts |
| no_waitlist | boolean | – | Only providers with open sign-up (no waitlist, invitation or country restriction) |
| output_tokens | integer | – | Output tokens per request, for the estimated cost |
| prompt_tokens | integer | – | Input tokens per request, for the estimated cost |
| region | string | – | Only providers that process data in this region: eu, us, … |
| requests_per_day | integer | – | Requests per day, to also get an estimated monthly cost |
| sort | string | – | Sort order: default blended (3:1 mix), or estimated_cost (the cost of your load) when prompt_tokens or output_tokens is given; estimated_cost needs one of them |
| strict | boolean | – | Exclude offers whose provider does not publish the filtered information (by default they are kept and flagged) |
No output schema declared.
No examples provided.
estimate_cost Estimate the cost of a workload ~273
Estimated cost of a workload on one model at each provider: cost per request, and per month if requests_per_day is given, taking the provider's tiered pricing and prompt-cache price into account. Offers sorted by estimated cost, cheapest first: the cheapest in detail, then one short line per offer with its estimated cost.
| Name | Type | Req | Description |
|---|---|---|---|
| cached_ratio | number | – | Share of input tokens served from the provider's prompt cache (0 to 1) |
| detail | string | – | compact (default): the winner in detail and one short line per other offer (provider, prices, signals, training on prompts when published). full: every field of every offer (all published conditions,… |
| limit | integer | – | Number of offers to return, cheapest included (default 5, max 25) |
| model | string | yes | Model id or name, e.g. 'deepseek-v3.2', 'deepseek/deepseek-v4-pro', 'gpt-5.6-luna'. Use search_models when unsure. |
| output_tokens | integer | – | Output tokens per request, for the estimated cost |
| prompt_tokens | integer | – | Input tokens per request, for the estimated cost |
| requests_per_day | integer | – | Requests per day, to also get an estimated monthly cost |
No output schema declared.
No examples provided.
gpu_rentals Rental offers for one GPU, by tier ~254
Rental offers for one GPU type: provider, price in USD per GPU per hour, number of GPUs in the published configuration, billing and region when published. One block per tier (guaranteed, community, spot), each with its own cheapest offer, also given per configuration (cheapest_by_gpu_count: the price per GPU of a single GPU and of a multi-GPU node are not comparable); tiers are never compared with each other. guaranteed: capacity the provider presents as not interrupted; community: third-party hosts; spot: interruptible capacity. Prices are as published by the provider, and dated. Get the GPU id from list_gpus.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | compact (default): the 3 cheapest offers of each tier. full: up to 50 offers per tier |
| gpu | string | yes | GPU id from list_gpus, for example h100-sxm-80gb |
| gpu_count | integer | – | Only this published configuration: 1, 2, 4, 8 or 16 GPUs |
| region | string | – | Only this region, as published by the provider |
| tier | string | – | Only this tier (default: one block per tier) |
No output schema declared.
No examples provided.
list_gpus GPU types tracked for rental prices ~88
GPU types whose rental price InferIndex tracks (H100, A100, L40S…), with the lowest price per GPU per hour in USD for each tier (guaranteed, community, spot) and the number of GPUs of that configuration. Prices are per GPU per hour, as published by each provider, and dated. Tiers are different products and are never compared with each other.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_history Price history of a model ~240
Price history of one model: every offer tracked by InferIndex (daily or weekly min/max/last price in USD, or raw price changes), plus the official price of the model's lab over time. Give either days, or from/to (YYYY-MM-DD), or at (a date) for the prices in effect that day.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | A single date, YYYY-MM-DD: prices in effect that day |
| days | integer | – | Number of days back from today (default 7) |
| from | string | – | Start date, YYYY-MM-DD (with to, instead of days) |
| granularity | string | – | day (default), week, or raw price changes |
| limit | integer | – | Maximum number of points (default 100, max 500) |
| model | string | yes | Model id or name, e.g. 'deepseek-v3.2', 'deepseek/deepseek-v4-pro', 'gpt-5.6-luna'. Use search_models when unsure. |
| provider | string | – | Only this provider |
| to | string | – | End date, YYYY-MM-DD |
No output schema declared.
No examples provided.
provider_ranking Providers ranked by price gap ~112
Providers ranked by how far below or above the market their prices are: each provider's median gap to the market, in percent (score_pct, negative when below the market), where the market of a model is the median blended 3:1 price of its providers, counted only on models with at least min_providers comparable providers (models_measured). Also the number of models where the provider holds the offer the cheapest tool would select (cheapest_count). Ranked from min_models models measured; refreshed every hour.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_models Search models ~69
Find the exact id of an LLM tracked by InferIndex from a name or partial name (e.g. 'deepseek', 'qwen3 max', 'claude opus'). Returns matching model ids and names, best match first.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Model name or part of it |
No output schema declared.
No examples provided.
self_host_or_api Self-host an open model or use the API? ~694
Is it cheaper to host an open-weights model yourself on rented GPUs, or to use the cheapest API offer? Returns a one-sentence verdict (headline) and the numbers behind it: the break-even volume in million tokens per day, the throughput the whole configuration must deliver for self-hosting to cost less (required_tokens_per_second: compare it with what your setup does), the break-even utilization when a throughput is known, the GPU configuration and its hourly price, and what the verdict rests on (confidence). Without a volume you still get the verdict and the break-even volume. It is an estimate: the throughput is a published measurement (measured), an estimate scaled from one (derived; estimated for a wide range), or a published minimum (lower_bound: a floor, valid for requests of up to 2,048 tokens in total, that can show self-hosting wins, never that the API is cheaper); or you give your own tokens_per_second. When no published figure decides, the headline gives the break-even volume and the required throughput, to compare with yours, rather than a yes or no, and may point out a dearer setup that published figures do decide (settled_alternative: for comparison, not a recommendation). headline_kind and headline_values give the headline as fields. It declines to give a number (status refused, with a reason) when it cannot do so reliably, for example a closed model, weights that do not fit the requested GPU, or a GPU nobody rents. Hardware rental only: the hourly price the provider publishes for the machine. It does not count the engineering to deploy and run the model, monitoring, redundancy, start-up time, or storage and network costs billed separately.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | compact (default): verdict, headline and key numbers. full: also the three throughput scenarios, the model and every assumption |
| gpu | string | – | Impose a GPU: id from list_gpus, for example h100-sxm-80gb |
| gpu_count | integer | – | Impose a number of GPUs: 1, 2, 4, 8 or 16 |
| model | string | yes | Model id or name, e.g. 'deepseek-v3.2', 'deepseek/deepseek-v4-pro', 'gpt-5.6-luna'. Use search_models when unsure. |
| output_tokens | integer | – | Output tokens per request |
| prompt_tokens | integer | – | Input tokens per request |
| quantization | string | – | Precision of the weights (default fp8); must be published by at least one provider unless fp16 or bf16 |
| requests_per_day | integer | – | Requests per day (with prompt_tokens and output_tokens) |
| tier | string | – | GPU rental tier (default guaranteed) |
| tokens_per_day | integer | – | Your volume in tokens per day (input and output together). Or give requests_per_day, prompt_tokens and output_tokens |
| tokens_per_second | number | – | Your own measured throughput for the whole configuration, input and output tokens together, instead of our estimate |
| utilization | number | – | Average share of time the GPUs serve requests, in percent (default 50) |
| weights_margin | integer | – | Percent of the GPU memory the model weights may fill (default 70; the rest is the engine reserve and the context cache) |
No output schema declared.
No examples provided.
How do I install the InferIndex MCP server?
InferIndex is a hosted endpoint at https://mcp.inferindex.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.inferindex.dev
claude mcp add --transport http inferindex-inferindex 'https://mcp.inferindex.dev/mcp'
What is the InferIndex MCP server?
InferIndex is an MCP server listed in the public MCP registry as io.github.InferIndex/inferindex. LLM API prices across 70+ providers: cheapest offer, comparisons, history and cost estimates. This page covers its hosted endpoint (https://mcp.inferindex.dev/mcp).
Is the InferIndex MCP server safe to use?
InferIndex scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the InferIndex MCP server expose?
InferIndex exposes 9 tools: search_models, cheapest, compare_providers, price_history, estimate_cost, and 4 more. Their descriptions and schemas cost roughly 2,684 tokens of context every time the server is loaded.
Does the InferIndex MCP server require authentication?
No. We connected to InferIndex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the InferIndex MCP server still maintained?
InferIndex is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.