Model Price Radar vs Ai Model Experiments
A side-by-side look at the Model Price Radar and Ai Model Experiments MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Model Price Radar for conversational ai work as a local process; choose Ai Model Experiments 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 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.
Choose Ai Model Experiments when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
experiment_models, experiment_estimate, experiment_create.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 53/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| 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 | 5 | 8 |
| Full listing | View Model Price Radar | View Ai Model Experiments |
Tools & capabilities
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
Ai Model Experiments tools 8
experiment_modelsList AI models available for experiments (about 300 across Anthropic, OpenAI, Google, Meta, Mistral, DeepSeek, Qwen and more), with context window and OUR per-token prices (provider cost × 1.5 — what experiments actually bill). Filter by name/vendor search, minimum context, or max price. Use the returned model ids in experiment_create. Example: experiment_models({ search: "claude", min_context: 100000 })experiment_estimateDry-run cost estimate for an experiment BEFORE creating it — cell count and estimated billed cost range (at our 1.5× pricing) for prompts × models × reps. Free to call, no side effects, does not need credit balance. Same spec shape as experiment_create. Example: experiment_estimate({ prompts: ["Summarize: ..."], models: ["anthropic/claude-sonnet-4.5", "openai/gpt-5"], reps: 2 })experiment_createModel Lab: run one prompt across many AI models at once and compare their outputs, cost, and latency side by side. Create and start an experiment: run each prompt against each model (× reps), collecting output, tokens, latency, and billed cost per cell. PREPAID: requires Pipeworx credit balance ≥ max_spend_usd (top up via experiment_topup); bills actual provider cost × 1.5 with a $0.10 minimum per experiment. ASYNC: returns experiment_id immediately — execution starts within ~1 minute; poll experiment_status until complete, then call experiment_results. Do NOT wait synchronously. Set summary:false to skip the AI-written model-comparison summary. Example: experiment_create({ name: "tone test", prompts: ["Rewrite formally: ..."], models: ["anthropic/claude-haiku-4.5", "openai/gpt-5-mini"], reps: 2, max_spend_usd: 2 })experiment_statusProgress of an experiment: cell counts by state (pending/running/ok/error/skipped), spend so far vs cap, and whether it is complete. Poll this after experiment_create (every few seconds). Example: experiment_status({ experiment_id: "..." })experiment_resultsResults of an experiment: per-model aggregates (mean latency, tokens, total billed cost, error rate), per-cell outputs, and the AI-written summary comparing how the models differed (if enabled). Use include_outputs:false for aggregates only. Example: experiment_results({ experiment_id: "..." })experiment_listList your experiments, newest first, with status and spend. Example: experiment_list({ limit: 10 })experiment_cancelCancel a running experiment: pending cells are skipped (not billed); in-flight cells finish and bill. Example: experiment_cancel({ experiment_id: "..." })experiment_topupHow to add prepaid credits for experiments (and your current balance). Payment is x402 — USDC on Base, paid in-band by any wallet-equipped agent: POST https://gateway.pipeworx.io/credits/topup?amount_usd=10 responds HTTP 402 with payment requirements; retry with PAYMENT-SIGNATURE to settle and the credits land instantly. Example: experiment_topup({})
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.
Model Price Radar
{
"mcpServers": {
"model-price-radar": {
"command": "uvx",
"args": [
"model-price-radar-mcp"
]
}
}
}
Ai Model Experiments
{
"mcpServers": {
"ai-model-experiments": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ai-model-experiments"
]
}
}
}
Frequently asked questions
Model Price Radar is categorized under Conversational AI and uses a local stdio subprocess. Ai Model Experiments belongs to Conversational AI and uses a local stdio subprocess. Pick Model Price Radar for conversational ai work and Ai Model Experiments 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.
Model Price Radar is listed as free. Auth: no auth required. Ai Model Experiments has no declared pricing — check the project's own site. 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 model-price-radar and ai-model-experiments as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Model Price Radar has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Ai Model Experiments has 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars.