LLM Pricing
by skakumanu · remote · no sign-in to list tools · v1.73.2 · published by GitHub user skakumanu
Real-time, drift-verified LLM pricing across 26 providers with cost+quality model routing.
Deletes · 3Changes · 11
29 tools: 3 can delete or cancel things, 11 change things and 15 only read.
Scanned Oct 21, 2026
- Deletes or cancels3Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things11Claude Code: ask: see these tools
- Only reads15Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http llm-pricing https://llm-pricing-api.fly.dev/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
29 tools
Deletes or cancels 3Claude Code: deny
delete_budget_alertDelete a registered budget-spend alert by its ID.No findings
Why it is in this group
- The name "delete_budget_alert" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete a registered budget-spend alert by its ID.
delete_conversationDelete a specific chat conversation by its ID.No findings
Why it is in this group
- The name "delete_conversation" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete a specific chat conversation by its ID. Use when the user asks to delete, clear, or remove a past conversation. Use list_conversations first to find the conversation ID.
delete_price_alertDelete a registered price-change alert by its ID.No findings
Why it is in this group
- The name "delete_price_alert" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete a registered price-change alert by its ID.
Changes things 11Claude Code: ask
ask_agentAsk the LLM Pricing AI agent a question in natural language.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Ask the LLM Pricing AI agent a question in natural language. Use for complex queries about pricing, model recommendations, cost optimisation advice, or anything that benefits from multi-step reasoning.
check_price_driftAudit this server's own pricing data against an external reference registry.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Audit this server's own pricing data against an external reference registry. Prices here are hand-maintained and go stale silently; a price that disagrees with the registry by more than the threshold is automatically withheld from serving the moment it's detected, not just when this tool runs. This reports what's currently withheld and why. The price value itself is never overwritten by the registry. Use when the user asks whether the pricing data is accurate or up to date, or wants to audit a specific provider's rates.
estimate_costEstimate the cost of using a specific LLM modelNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Estimate the cost of using a specific LLM model
get_pricing_export_urlGenerate a download URL for the pricing history export.No findings
Why it is in this group
- The name "get_pricing_export_url" says "get": a word for reading.
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate a download URL for the pricing history export. Returns a URL the user can open in their browser to download snapshot history as CSV (for spreadsheets) or JSON (for code). Use this when the user asks to export, download, or save pricing data.
import_session_usageBulk-import a completed session's usage in a single call — the retroactive counterpart to record_usage, for when a session wasn't instrumented live.No findings
Why it is in this group
- The name "import_session_usage" says "import": a word for a change.
Description, as the server wrote it Bulk-import a completed session's usage in a single call — the retroactive counterpart to record_usage, for when a session wasn't instrumented live. Use when a calling agent (e.g. VS Code Copilot Chat) already has a session's turn-by-turn history in its own local store and wants this server to report on it exactly as if it had been tracked live. Accepts a list of entries under one shared session_id; each entry resolves its input and output tokens independently, either from exact counts when known or by estimating from raw turn text using this server's existing token counter. Cost is always computed server-side from current pricing, never trusted from the caller. A malformed entry (no usable tokens/text on one side, or an unresolvable model_name) is reported as its own per-entry failure and does not fail the rest of the batch. Idempotent like record_usage — resubmitting the same entries (same request_id, or the same session_id/model/occurred_at/token-or-text when request_id is omitted) is a no-op. Recorded usage is then readable via analyze_session_usage and GET /usage/session/{session_id}.
optimize_workloadOptimise a multi-task LLM workload by assigning the cheapest qualifying model to each task instead of running everything through one model.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Optimise a multi-task LLM workload by assigning the cheapest qualifying model to each task instead of running everything through one model. Takes a list of workloads (task type + monthly volume + optional quality floor and capability requirements) and returns a per-task model allocation, the total monthly cost, and the saving versus the best single-model deployment. If a monthly budget is given, leftover headroom is spent on the most cost-efficient quality upgrades. Use when the user asks how to cut LLM spend across several task types, or whether tiered model routing is worth it.
predict_costPredict the real cost of an LLM call from your actual prompt text — no need to know token counts in advance.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Predict the real cost of an LLM call from your actual prompt text — no need to know token counts in advance. Counts tokens locally, infers the task type (or accepts one explicitly), estimates output length from empirical I/O profiles, and returns all models ranked cheapest-first with effective cost after prompt-cache savings. Also surfaces the best quality-per-dollar pick. Use this before making any LLM API call to avoid surprise bills.
recommend_modelRecommend the optimal LLM model from a free-text description of your use case — no need to already know the routing engine's task_type vocabulary.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Recommend the optimal LLM model from a free-text description of your use case — no need to already know the routing engine's task_type vocabulary. Classifies the description into a task type, then runs it through the same routing engine behind /router/recommend (live pricing + benchmark quality, hard filters for cost/quality/context window, scored by quality-per-dollar). Returns the best match plus up to 3 alternatives. Read-only — use predict_cost first if you also want per-model cost estimates for an actual prompt, and optimize_workload if you have several distinct task types to route at once.
record_usageRecord actual token usage for a completed LLM call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Record actual token usage for a completed LLM call. Cost is computed server-side from current pricing, never trusted from the caller — this is the 'actual spend' counterpart to estimate_cost's hypothetical numbers. Optionally scope to an org_id for per-org spend tracking. Resubmitting the same request_id for the same org is a no-op. Use when the user wants to log or track real LLM spend, not just estimate it.
register_budget_alertRegister a webhook URL to receive notifications when actual recorded spend (from record_usage) crosses a USD threshold within a rolling window.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Register a webhook URL to receive notifications when actual recorded spend (from record_usage) crosses a USD threshold within a rolling window. Optionally scope to a specific org_id (omit for total spend across all orgs). Fires at most once per period_days while spend stays over threshold. Returns the alert ID.
register_price_alertRegister a webhook URL to receive notifications when a model's price changes by more than a specified percentage.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Register a webhook URL to receive notifications when a model's price changes by more than a specified percentage. Optionally scope the alert to a specific provider or model. Returns the alert ID.
Only reads 15Claude Code: allow
analyze_session_usageAnalyze one specific session's actual recorded LLM usage (tagged via record_usage's session_id) on demand: total input/output tokens, total actual cost, and a per-model breakdown i…No findings
Why it is in this group
- The name "analyze_session_usage" says "analyze": a word for reading.
Description, as the server wrote it Analyze one specific session's actual recorded LLM usage (tagged via record_usage's session_id) on demand: total input/output tokens, total actual cost, and a per-model breakdown if more than one model was used. Also runs the session's own observed token pattern through the same routing engine behind recommend_model / POST /router/recommend to produce a grounded recommendation — or confirm the current choice is already optimal — with the estimated dollar savings or increase versus this session's actual cost. Returns has_data: false with no recommendation if the session_id has no recorded usage. Advisory only — never switches or reroutes anything.
compare_costsCompare costs for multiple LLM modelsNo findings
Why it is in this group
- The name "compare_costs" says "compare": a word for reading.
Description, as the server wrote it Compare costs for multiple LLM models
get_all_pricingGet current pricing for all LLM models from all providersNo findings
Why it is in this group
- The name "get_all_pricing" says "get": a word for reading.
Description, as the server wrote it Get current pricing for all LLM models from all providers
get_cache_statsReport process-lifetime hit/miss counts, total lookups, and hit rate for the ~5-minute recommendation cache, separately for the recommend_model tool and POST /router/recommend (nev…No findings
Why it is in this group
- The name "get_cache_stats" says "get": a word for reading.
Description, as the server wrote it Report process-lifetime hit/miss counts, total lookups, and hit rate for the ~5-minute recommendation cache, separately for the recommend_model tool and POST /router/recommend (never combined). Server-operations introspection for confirming the cache is reducing recomputation in production, not a pricing question. Counts reset on process restart; reading them never changes them.
get_data_qualityReport an aggregate accuracy summary for the pricing catalogue: what percentage of models have a confirmed, fresh price, how many are currently withheld due to price drift, how man…No findings
Why it is in this group
- The name "get_data_quality" says "get": a word for reading.
Description, as the server wrote it Report an aggregate accuracy summary for the pricing catalogue: what percentage of models have a confirmed, fresh price, how many are currently withheld due to price drift, how many are newly discovered and not yet priced, and how many confirmed prices are over 90 days old. A single trust signal, distinct from check_price_drift which lists individual disputes. Use when the user asks how accurate or trustworthy the pricing data is, overall.
get_ide_pricingGet subscription pricing for AI coding IDE tools: GitHub Copilot, Cursor, Windsurf, Claude.ai, JetBrains AI, Amazon Q Developer, and Tabnine.No findings
Why it is in this group
- The name "get_ide_pricing" says "get": a word for reading.
Description, as the server wrote it Get subscription pricing for AI coding IDE tools: GitHub Copilot, Cursor, Windsurf, Claude.ai, JetBrains AI, Amazon Q Developer, and Tabnine. Returns monthly subscription cost, inline completion support, context window, and per-tool strengths. Use this when the user asks to compare IDE AI tools, subscription-based coding assistants, or wants to know which IDE AI fits their budget.
get_performance_metricsGet performance metrics (throughput, latency, context window) for modelsNo findings
Why it is in this group
- The name "get_performance_metrics" says "get": a word for reading.
Description, as the server wrote it Get performance metrics (throughput, latency, context window) for models
get_pricing_historyQuery historical pricing snapshots recorded over time.No findings
Why it is in this group
- The name "get_pricing_history" says "get": a word for reading.
Description, as the server wrote it Query historical pricing snapshots recorded over time. Use this to look up past prices for a model or provider, or to see how prices have changed over a given number of days.
get_pricing_trendsFind models whose prices changed the most over a given period.No findings
Why it is in this group
- The name "get_pricing_trends" says "get": a word for reading.
Description, as the server wrote it Find models whose prices changed the most over a given period. Returns models sorted by absolute percentage price change with a direction label ('increased', 'decreased', or 'unchanged'). Use this to answer questions like 'which models got cheaper this month?' or 'which providers raised prices recently?'
get_telemetryGet MCP server telemetry and usage statistics including tool usage, response times, and error ratesNo findings
Why it is in this group
- The name "get_telemetry" says "get": a word for reading.
Description, as the server wrote it Get MCP server telemetry and usage statistics including tool usage, response times, and error rates
get_usage_summaryGet a summary of actual recorded LLM spend: total cost, request count, and breakdowns by model and provider, from usage events previously logged via record_usage.No findings
Why it is in this group
- The name "get_usage_summary" says "get": a word for reading.
Description, as the server wrote it Get a summary of actual recorded LLM spend: total cost, request count, and breakdowns by model and provider, from usage events previously logged via record_usage. Use when the user asks what they've actually spent, as opposed to a hypothetical cost estimate.
get_use_casesGet recommended use cases and strengths for LLM modelsNo findings
Why it is in this group
- The name "get_use_cases" says "get": a word for reading.
Description, as the server wrote it Get recommended use cases and strengths for LLM models
list_budget_alertsList all registered budget-spend webhook alerts with their IDs and settings.No findings
Why it is in this group
- The name "list_budget_alerts" says "list": a word for reading.
Description, as the server wrote it List all registered budget-spend webhook alerts with their IDs and settings.
list_conversationsList stored chat conversation sessions with their IDs, last-updated timestamp, turn count, and a preview of the most recent user message.No findings
Why it is in this group
- The name "list_conversations" says "list": a word for reading.
Description, as the server wrote it List stored chat conversation sessions with their IDs, last-updated timestamp, turn count, and a preview of the most recent user message. Use this when the user asks to see their past conversations or chat history.
list_price_alertsList all registered price-change webhook alerts with their IDs and settings.No findings
Why it is in this group
- The name "list_price_alerts" says "list": a word for reading.
Description, as the server wrote it List all registered price-change webhook alerts with their IDs and settings.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.73.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http llm-pricing https://llm-pricing-api.fly.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__llm-pricing__get_all_pricing",
"mcp__llm-pricing__compare_costs",
"mcp__llm-pricing__get_performance_metrics",
"mcp__llm-pricing__get_use_cases",
"mcp__llm-pricing__get_telemetry",
"mcp__llm-pricing__get_pricing_history",
"mcp__llm-pricing__get_pricing_trends",
"mcp__llm-pricing__list_price_alerts",
"mcp__llm-pricing__list_conversations",
"mcp__llm-pricing__get_ide_pricing",
"mcp__llm-pricing__get_data_quality",
"mcp__llm-pricing__get_cache_stats",
"mcp__llm-pricing__get_usage_summary",
"mcp__llm-pricing__analyze_session_usage",
"mcp__llm-pricing__list_budget_alerts"
],
"ask": [
"mcp__llm-pricing__estimate_cost",
"mcp__llm-pricing__register_price_alert",
"mcp__llm-pricing__get_pricing_export_url",
"mcp__llm-pricing__predict_cost",
"mcp__llm-pricing__optimize_workload",
"mcp__llm-pricing__recommend_model",
"mcp__llm-pricing__check_price_drift",
"mcp__llm-pricing__record_usage",
"mcp__llm-pricing__import_session_usage",
"mcp__llm-pricing__register_budget_alert",
"mcp__llm-pricing__ask_agent"
],
"deny": [
"mcp__llm-pricing__delete_price_alert",
"mcp__llm-pricing__delete_conversation",
"mcp__llm-pricing__delete_budget_alert"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as llm-pricing. Review it before you use it.