Apipriceindex MCP vs Model Price Radar
A side-by-side look at the Apipriceindex MCP and Model Price Radar MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Apipriceindex MCP for conversational ai work as a local process; choose Model Price Radar for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Apipriceindex MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_models, get_price, estimate_cost.
Choose Model Price Radar when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
find_models, estimate_cost, model_price_history.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 48/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 5 |
| Full listing | View Apipriceindex MCP | View Model Price Radar |
Tools & capabilities
Apipriceindex MCP tools 3
search_modelsFind model ids by name/provider, filter by context window or open weightsget_priceVerified price of one model: input/output/cached input USD per Mtok, `verified_at`, `confidence`, sourceestimate_costMonthly bill of a workload; ranks chosen models — or the whole catalog — cheapest first
Model Price Radar tools 5
find_modelsSearch the live catalog by name, capabilities (tools, vision, reasoning, structured outputs, audio, free), price ceilings, contextestimate_costCost of a workload (tokens per call × calls) on up to 10 models, cheapest firstmodel_price_historyEvery price change of one model since it appeared, with % changesprice_changesSince a month: biggest drops and increases, newly free models, models added/removedcompare_providersSame model across providers: price, context, max output, quantization, uptime
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Apipriceindex MCP
{
"mcpServers": {
"mcp-281": {
"command": "uvx",
"args": [
"apipriceindex-mcp"
]
}
}
}
Model Price Radar
{
"mcpServers": {
"model-price-radar": {
"command": "uvx",
"args": [
"model-price-radar-mcp"
]
}
}
}
Frequently asked questions
Apipriceindex MCP is categorized under Conversational AI and uses a local stdio subprocess. Model Price Radar belongs to Conversational AI and uses a local stdio subprocess. Pick Apipriceindex MCP for conversational ai work and Model Price Radar for conversational ai.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Apipriceindex MCP has no declared pricing — check the project's own site. Model Price Radar is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-281 and model-price-radar as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Apipriceindex MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Model Price Radar has 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars.