Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cloudprice

PYPI · CLOUDPRICE-MCP

Multi-cloud + LLM pricing for AI agents: AWS/Azure/GCP/OCI, RI break-even, TCO, price history.

Available components

60 Trust /100

Last scanned (2 hours ago)

Scores higher than 57% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Albaker-Group/cloudprice-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 8572 tokens (~219/item across 39 items; 39 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 47% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "compare_llm_vs_selfhost" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 40 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
Changelog

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.

  • 5 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 7495 → 8572 ▼ functional
    • Package version: 0.25.0 → 0.29.0 functional
    • Package version: 0.25.0 → 0.28.0 functional
    • Package version: 0.25.0 → 0.26.0 functional
  • 4 Nov 26 74

    First indexed and scored.

Diagnostics

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 · Analysed pypi/cloudprice-mcp@0.29.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Albaker-Group/cloudprice-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Albaker-Group/cloudprice-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 3692288401
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:f8c1e6a3b7fb3d08c5f58794215ed110d03bbbdcb27859f1875ea43d94ef927f

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 39 exposed · ~8,472 tokens

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 →

Tool Tokens
analyze_ai_spend ~194

FinOps for AI on the user's actual bill (a local FOCUS 1.x CSV export; nothing is sent anywhere). Finds the generative-AI lines (Amazon Bedrock, Azure OpenAI / AI Foundry, Vertex AI, OCI Generative AI) and gives spend per model split into input, output, cache-read and cache-write tokens; what was paid against list price; the same model's cost on other providers for the same tokens; how much input comes from prompt cache and what more would save; and list price changes for those models from the weekly LLM price archive. Use for: 'what is our LLM spend', 'are we overpaying for this model', 'would caching help'.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.
top_ninteger–How many models to return, largest spend first.

No output schema declared.

No examples provided.

analyze_bill ~188

Analyse the user's actual cloud bill from a FOCUS 1.x CSV export (AWS Data Exports, Azure Cost Management, GCP BigQuery FOCUS view, OCI). Read from local disk only; nothing is sent anywhere. Returns total cost, top cost drivers grouped by service / category / provider / region / SKU / resource, cost by month, the biggest month-over-month movers, list vs effective cost (what discounts saved), and commitment coverage of usage when the export carries commitment columns. Use for: 'where is our cloud money going', 'what jumped last month', 'how much of our usage is covered by RIs / Savings Plans'. Ask the user for the path to their export file.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.
group_bystring––
top_ninteger––

No output schema declared.

No examples provided.

analyze_cost_allocation ~189

FinOps allocation on the user's actual bill (a local FOCUS 1.x CSV export; nothing is sent anywhere). Measures how much allocatable cost carries the tags used for showback / chargeback, coverage per required tag, cost by the values of one tag (e.g. team), cost by sub-account, and the biggest untagged services and resources. Use for: 'how much of our spend is tagged', 'cost per team', 'what is missing a cost-center tag'.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.
required_tagsarray–Tag keys every resource should carry, e.g. ['team', 'env']. Omit to count any tag as tagged.
tag_keystring–Break cost down by the values of this tag.
top_ninteger––

No output schema declared.

No examples provided.

assess_migration ~216

Project cross-cloud cost + payback for moving a workload away from its source cloud. Inputs: source_cloud + workload inventory (compute / storage / object_storage / databases / egress) + optional one_time data to migrate. Returns per-target monthly cost, savings %, exit egress cost, payback months, ranked recommendation by 3-year TCO, and triggered caveats (e.g., 'OCI A1.Flex is ARM — verify your AMIs'). The kind of FinOps decision that normally lives in a half-built spreadsheet — now one tool call.

NameTypeReqDescription
commitmentstring––
computearray––
databasesarray––
egressarray––
multi_azboolean––
object_storagearray––
one_timeobject––
source_cloudstringyesCloud the workload currently runs on.
storagearray––
targetsarray–Target clouds to evaluate. Default: all clouds except source_cloud.

No output schema declared.

No examples provided.

calculate_unit_cost ~207

FinOps unit economics on the user's actual bill (a local FOCUS 1.x CSV export; nothing is sent anywhere). Divides monthly recurring spend by business volumes the user supplies (customers, requests, orders) to give cost per unit by month, and whether spend is growing faster or slower than the business. Optionally scoped to one product or team by tag. Use for: 'cost per customer', 'are we scaling efficiently'. Ask the user for the monthly volumes.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.
tag_keystring–Scope cost to rows with this tag (with tag_value).
tag_valuestring––
unit_namestring–What a unit is, e.g. 'customer' or 'request'.
unitsarrayyesBusiness volume per month, e.g. [{'month': '2026-10', 'units': 120000}].

No output schema declared.

No examples provided.

compare_agent_platforms ~360

Where to host an AI agent, and what a month of it costs: the same agent priced on Amazon Bedrock AgentCore Runtime, Azure AI Foundry Agent Service (prompt agents and hosted agents), Google Vertex AI Agent Engine, and plain serverless (AWS Lambda, Azure Container Apps). Each platform is split into hosting, tools, memory and model tokens, with the model priced on that cloud's own model service (or marked unavailable), and the busy share of a run below which AgentCore costs less than each alternative. Use for: 'AgentCore vs Foundry vs Vertex for our agent', 'should this agent run on Lambda or AgentCore', 'what will hosting 50,000 agent runs a month cost'. For token counts per run, use estimate_agent_cost first.

NameTypeReqDescription
active_cpu_sharenumber–Share of the run the agent is busy, not waiting on the model or tools (0-1].
input_tokens_per_runinteger–Default: estimate_agent_cost's default 8-step run (97,200).
memory_gbnumber––
memory_retrievals_per_runinteger–Long-term memory lookups per run (AgentCore Memory, Agent Engine Memory Bank).
modelstring–Model to price on each cloud, e.g. 'claude-sonnet-5-5' or 'gpt-5'.
output_tokens_per_runinteger–Default: estimate_agent_cost's default 8-step run (3,200).
run_secondsnumber–Wall-clock seconds per run, waiting included.
runs_per_monthinteger––
tool_calls_per_runinteger––
vcpunumber––

No output schema declared.

No examples provided.

compare_carbon_footprint ~187

Multi-cloud carbon footprint comparison — the only FinOps tool that returns both USD cost AND kg CO2e/month side-by-side. For a given vCPU + memory shape (and optional quantity), returns per-cloud best-matching SKU + monthly cost + grid-based kg CO2e + market-based residual kg CO2e (after the cloud's published renewable matching) + power class (x86 vs ARM). Ranked cheapest-carbon-first. Surfaces tradeoffs (AWS/Azure 100% renewable matched, GCP ~64% CFE, OCI unmatched outside EU). Use when the user cares about sustainability, Green FinOps, or carbon-cost dual optimization.

NameTypeReqDescription
memory_gbnumberyes–
quantityinteger––
targetsarray–Optional list of clouds to compare; default all 4.
vcpusintegeryes–

No output schema declared.

No examples provided.

compare_clouds ~120

Find the cheapest equivalent VM across AWS, Azure, GCP, and OCI for a single target spec (vCPUs and memory). Returns the best-fit SKU per cloud sorted by monthly cost, plus the absolute and percent savings of the cheapest vs the most expensive option. OCI A1 Always Free is included — for specs that fit within 4 OCPU + 24 GB Arm, OCI returns $0/mo (real perpetual free tier, not a quirk).

NameTypeReqDescription
memory_gbnumberyes–
vcpusintegeryes–

No output schema declared.

No examples provided.

compare_compute_inventory ~96

Bulk-compare a list of compute workloads across AWS, Azure, GCP, and OCI. Each row is independently sized to the cheapest VM that meets its vCPU/memory spec on each cloud, multiplied by quantity and hours_per_month. Optional os_disk_gb adds attached storage cost. Returns per-row matches, per-cloud totals, and the cheapest cloud overall. Useful for sizing-sheet style inputs.

NameTypeReqDescription
workloadsarrayyes–

No output schema declared.

No examples provided.

compare_egress ~126

Compare data-transfer costs across AWS, Azure, GCP, and OCI for a given monthly volume. Two directions supported: 'out_to_internet' (tiered pricing with free-tier credits — AWS/Azure 100 GB, OCI 10 TB free) and 'inter_region' (flat rate for cross-region transfer within the same cloud). At 50 TB/mo of internet egress OCI is ~12× cheaper than the hyperscalers — a real competitive moat for content/CDN workloads. VPC peering is NOT yet modeled.

NameTypeReqDescription
transfersarrayyes–

No output schema declared.

No examples provided.

compare_gpu_workload ~237

Cross-cloud GPU pricing comparison — finds the cheapest matching SKU per cloud for a (gpu_type, gpu_count) request. Supports NVIDIA T4 / A10 / A10G / L4 / L40S / V100 / A100 / H100 across AWS / Azure / GCP / OCI. Returns absolute hourly cost AND $/GPU/h so users can see both the absolute winner and the per-GPU packaging-efficiency winner (they're often different clouds). Surfaces over-provisioning when the only matching SKU has more GPUs than requested (e.g., asking for 1 H100 but only bare-metal 8x SKUs are available). Use for AI/ML workload pricing decisions — training, inference, fine-tuning.

NameTypeReqDescription
gpu_countinteger––
gpu_typestringyesGPU family name, e.g. 'A100', 'H100', 'L4', 'L40S', 'T4', 'A10', 'A10G', 'V100'. Case-insensitive.
targetsarray–Optional list of clouds to compare; default all 4.

No output schema declared.

No examples provided.

compare_llm_vs_selfhost ~382

Pay per token or rent GPUs and serve the model yourself? Prices a monthly token volume on an LLM API, then the GPU servers needed to serve the same volume on AWS, Azure, GCP and OCI, and the break-even volume. Needs the measured generation throughput of one server (output tokens/second, e.g. from a vLLM benchmark): it decides the answer and is never guessed. Use for: 'should we self-host Llama 3.3 70B instead of paying Together', 'at what volume do H100s beat the DeepSeek API', 'cheapest cloud to serve our open model'. Self-host cost is GPU rental only; see honest_gaps.

NameTypeReqDescription
api_providerstring–Host for the API price. Default: first-party.
gpu_countinteger–GPUs per server.
gpu_typestringyesGPU to self-host on: T4, L4, A10, A10G, L40S, V100, A100, H100.
modelstringyesAPI model ID to price, as in the LLM catalogue, e.g. 'deepseek/deepseek-chat', 'together_ai/meta-llama/Llama-3.3-70B-Instruct-Turbo'.
monthly_input_tokensinteger––
monthly_output_tokensinteger––
output_tokens_per_secondnumberyesMeasured aggregate generation throughput of ONE server of this size for this model, across concurrent requests.
prefill_speedupnumber–How much faster input (prefill) is processed than output is generated.
targetsarray––
utilizationnumber–Share of each hour the server is busy. Real traffic is bursty; 0.4-0.7 is typical.

No output schema declared.

No examples provided.

compare_object_storage ~138

Compare object-storage pricing across AWS S3, Azure Blob, GCP Cloud Storage, and OCI Object Storage. Each request specifies capacity_gb and access tier (hot/cool/archive); the tool picks the cheapest SKU per cloud at that tier. OCI offers 20 GB Always Free in the 'hot' tier — surfaced when capacity fits. NOTE: egress, request, and retrieval costs are not modeled (often the actual hidden killer). Prices are hand-entered list prices (as of 2026-05-04), not part of the weekly refresh — verify against the provider's page before deciding.

NameTypeReqDescription
volumesarrayyes–

No output schema declared.

No examples provided.

compare_postgres_database ~107

Compare managed PostgreSQL pricing across AWS RDS, Azure Database for PostgreSQL, GCP Cloud SQL, and OCI Database with PostgreSQL. Each request specifies vCPUs, memory, and storage_gb; the tool picks the cheapest matching SKU per cloud and totals compute + storage. Prices are hand-entered estimates (as of 2026-05-04), not part of the weekly refresh — verify against the provider's page before deciding.

NameTypeReqDescription
databasesarrayyes–

No output schema declared.

No examples provided.

compare_spot ~141

Compare spot / preemptible pricing for a vCPU + memory shape across AWS, Azure, GCP, and OCI. Returns per-cloud best-matching SKU + on-demand cost + spot cost + savings + eviction characteristics, ranked cheapest-first. The only multi-cloud spot comparison anyone publishes openly — AWS Spot vs Azure Spot vs GCP Spot VMs vs OCI Preemptible all use different pricing + eviction models, and this tool surfaces every one of them with their tradeoffs.

NameTypeReqDescription
memory_gbnumberyes–
targetsarray–Optional list of clouds to compare; default all 4.
vcpusintegeryes–

No output schema declared.

No examples provided.

compare_storage_inventory ~105

Bulk-compare a list of block-storage volumes across AWS, Azure, GCP, and OCI. Each row picks the cheapest SKU matching its disk_type (ssd or hdd) on each cloud, then prices it at capacity_gb × quantity. Returns per-row matches, per-cloud totals, and cheapest cloud. IOPS and throughput are accepted but not used for SKU matching. Snapshot pricing is upper-bound (real-world incremental snapshots cost less).

NameTypeReqDescription
volumesarrayyes–

No output schema declared.

No examples provided.

compare_token_pricing ~297

Cross-provider LLM token pricing comparison — the only FinOps tool that returns per-1M input/output rates AND monthly cost for the same model on each provider that hosts it (Claude on Anthropic vs Bedrock vs Vertex; GPT on OpenAI vs Azure OpenAI; Llama on Bedrock; Gemini on Google vs Vertex; Mistral / DeepSeek direct). Filter by model_family ('claude', 'gpt', 'gemini', 'llama', 'mistral', 'deepseek'), exact model_id, or provider list. If monthly_input_tokens + monthly_output_tokens are provided, ranks by total monthly USD. Otherwise ranks by per-1M output cost (output tokens dominate most workloads). Surfaces cache_read / cache_write rates when published — most workloads see 30-90% input cost reduction with proper prompt caching.

NameTypeReqDescription
model_familystring–Filter to one model family. Optional.
model_idstring–Exact model ID (e.g. 'claude-4-sonnet', 'gpt-4o', 'gemini-2.0-flash'). Optional.
monthly_input_tokensinteger–Monthly input token volume. Required to get monthly_total_usd in result.
monthly_output_tokensinteger–Monthly output token volume. Required to get monthly_total_usd in result.
providersarray–Optional list of providers to include.

No output schema declared.

No examples provided.

compare_total_cost_of_ownership ~195

Project per-cloud per-year cost over a configurable horizon (default 3 years), with linear YoY growth assumptions for compute / storage / egress. Returns cumulative TCO per cloud, year-by-year breakdown by category, and sensitivity analysis identifying the most impactful growth variable. The kind of number that goes into board decks and budget conversations — now computed from a public catalog instead of a spreadsheet.

NameTypeReqDescription
commitmentstring––
computearray––
databasesarray––
egressarray––
growthobject––
horizon_yearsinteger–Years to project (default 3 — FinOps standard).
multi_azboolean––
object_storagearray––
one_timeobject––
storagearray––
targetsarray–Clouds to project. Default: all 4 clouds.

No output schema declared.

No examples provided.

compare_workload ~245

Combined compute + block-storage compare across AWS, Azure, GCP, and OCI. Pass a compute list and a storage list (either may be empty). Returns nested per-row breakdowns plus combined per-cloud totals and the overall cheapest cloud. Mirrors the structure of a two-sheet sizing workbook (compute BoM + storage BoM). Optional `commitment` parameter estimates 1-year or 3-year Reserved Instance / Savings Plan / Committed Use discount on compute (storage stays at on-demand). For object storage, use compare_object_storage. For managed databases, use compare_postgres_database.

NameTypeReqDescription
commitmentstring–Compute commitment tier. 'none' = on-demand only. '1yr_no_upfront' applies a representative 30% compute discount. '3yr_partial_upfront' applies 50%. Storage and snapshots are not discounted.
computearray––
multi_azboolean–If true, double compute cost on every cloud to model Multi-AZ / HA deployments (sync replicas across two zones). Storage stays at 1x because object/block storage is usually cross-AZ at base price alr…
storagearray––

No output schema declared.

No examples provided.

detect_bill_anomalies ~164

FinOps anomaly management on the user's actual bill (a local FOCUS 1.x CSV export; nothing is sent anywhere). Compares each service's daily (or monthly) cost with its own recent normal and reports spikes, drops and new spend as events, ranked by excess cost, flagging events still going in the latest period. Use for: 'what blew up our bill', 'did anything unusual happen last week', 'what new spend appeared'.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.
group_bystring––
limitinteger––
min_impactnumber–Ignore moves smaller than this, in billing currency.
sensitivitystring––

No output schema declared.

No examples provided.

detect_price_anomalies ~207

Statistical anomaly detection over the bundled price-history dataset. Compounds the v0.7.1 history archive: as snapshots accumulate weekly, this tool auto-flags unusual price moves without you having to manually inspect every SKU. Two methods, auto-selected by dataset density: percent_change (for <5 snapshots) and z_score (>=5). Sensitivities: strict (10% / z>=2.5), moderate (5% / z>=2.0, default), permissive (2% / z>=1.5). Use for 'what changed this week?' and 'anything weird across any cloud since {date}?' queries. Excellent source for weekly LinkedIn / blog content auto-generation.

NameTypeReqDescription
cloudstring–Filter to one cloud. Optional.
limitinteger––
methodstring––
sensitivitystring––
sincestring–ISO date — restrict to snapshots on or after this date. Optional.

No output schema declared.

No examples provided.

estimate_agent_cost ~465

Estimate what one run of an AI agent costs, and a month of runs. Models what per-call math misses: each agent step re-sends the whole conversation (system prompt, tool definitions, earlier outputs and tool results), so input tokens grow every step. Returns cost per run and per month, the per-step token breakdown, how much of the input is context growth, what prompt caching saves, and the same run priced on other current models (Claude, GPT, Gemini, DeepSeek by default). Use for: 'what will my agent cost at 50k runs a month', 'is Sonnet or Haiku cheaper for this agent', 'how much does caching save', 'budget for an AgentCore / LangGraph / Agents SDK agent'. Defaults describe a typical 8-step tool-using agent; pass measured token counts for a real figure.

NameTypeReqDescription
compare_modelsarray–Model IDs to price the same run on. Default: popular current Claude, GPT, Gemini and DeepSeek models.
hostingobject–Add hosting to the token cost: prices the run on AgentCore Runtime (+ Gateway, Memory) and on Lambda, and returns full per-run and monthly totals. AgentCore bills CPU only while active; Lambda bills…
modelstringyesModel ID as in the LLM catalogue, e.g. 'claude-sonnet-5-5', 'gpt-5-mini', 'gemini/gemini-2.5-flash'. Find IDs with lookup_extended_model_pricing.
output_tokens_per_stepinteger–Average model output tokens per step.
providerstring–Host to price on, e.g. 'anthropic', 'bedrock', 'vertex'. Default: the model's first-party provider.
runs_per_monthinteger–Agent runs per month.
stepsinteger–LLM calls per run, including the final answer.
system_prompt_tokensinteger–Tokens in the system prompt.
tool_definition_tokensinteger–Tokens in the tool/function definitions sent with every call.
tool_result_tokens_per_stepinteger–Average tokens a tool returns per step.
user_input_tokensinteger–Tokens in the user's request.

No output schema declared.

No examples provided.

export_focus ~377

Emit FOCUS 1.3-shaped rows from any pricing query, ready to import into Vantage Custom Providers / Microsoft Cost Mgmt / OpenCost / Apptio / any FinOps tool that consumes the FinOps Foundation's open billing schema (ratified Dec 2025). The rows populate the list-price columns (ListCost, ListUnitPrice, PricingQuantity, etc.) and leave billed/contracted/effective columns NULL since cloudprice produces projections, not real bills — that's explicitly documented in the result's notes field. Use this when the user says 'export my comparison to FOCUS', 'send this to Vantage', 'plug this into our FinOps stack'. Supports query_kind: compute_workload (calls assess_migration), token_pricing (compare_token_pricing), extended_model_lookup (lookup_extended_model_pricing). Format is 'json' (default) or 'csv'.

NameTypeReqDescription
billing_period_startstring–ISO date YYYY-MM-DD for the synthetic billing period start. Defaults to current month.
commitmentstring––
computearray––
databasesarray––
egressarray––
formatstring––
modestring––
model_familystring––
model_idstring––
monthly_input_tokensinteger––
monthly_output_tokensinteger––
multi_azboolean––
object_storagearray––
providerstring––
providersarray––
querystring––
query_kindstringyesWhich underlying pricing tool to run before FOCUS-shaping.
sourcestring––
source_cloudstring––
storagearray––
targetsarray––

No output schema declared.

No examples provided.

find_commitment_gaps ~150

FinOps rate optimisation on the user's actual bill (a local FOCUS 1.x CSV export; nothing is sent anywhere). Returns commitment coverage of eligible compute and database usage, utilisation of existing Savings Plans / RIs / CUDs (and what unused commitment cost), and per cloud the steady on-demand spend that could be committed, with the $/hour commitment and annual saving for 1-year and 3-year no-upfront terms. Use for: 'are we under-committed', 'how much would a Savings Plan save us', 'are our reservations being used'.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.

No output schema declared.

No examples provided.

find_egress_arbitrage ~156

Specialized assess_migration scoped to egress patterns. Useful when a team's largest cost line is data transfer (CDN workloads, video streaming, content distribution). Returns per-target egress cost, monthly + annual savings, payback months on any one-time exit cost, and recommendation. The OCI 12× moat is the headline finding: at 50 TB/month internet egress, OCI is roughly $340 vs $4,000+ on the hyperscalers because of OCI's 10 TB/month free tier + $0.0085/GB beyond.

NameTypeReqDescription
egressarrayyes–
one_timeobject––
source_cloudstringyes–
targetsarray––

No output schema declared.

No examples provided.

forecast_spend ~139

FinOps forecasting on the user's actual bill (a local FOCUS 1.x CSV export; nothing is sent anywhere). Projects month-end spend and the next months from the trend in recurring spend, each with a 95% range, and lists the services whose spend is growing fastest. Daily exports (28+ days) give a daily trend and a month-end estimate. Use for: 'what will this month's bill be', 'where is spend heading next quarter', 'what is driving growth'.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.
horizon_monthsinteger––

No output schema declared.

No examples provided.

generate_decision_report ~254

Generate a CFO-grade FinOps decision report in markdown. Combines assess_migration + compare_carbon_footprint into a single structured artifact the user can paste into a wiki / PR / Slack / email. Sections: executive summary, per-cloud cost table, carbon comparison (optional), the workload spec, aggregated honest_gaps, and an audit trail (package version, catalog as_of, requester, reproduce command). The 'trust' angle commercial FinOps tools can't easily replicate because their reports live in their UI; this one is markdown the user owns. Use when the question is 'we need a decision artifact a CFO can sign off on'.

NameTypeReqDescription
commitmentstring––
computearray––
databasesarray––
egressarray––
include_carbonboolean––
multi_azboolean––
object_storagearray––
one_timeobject––
requesterstring–Optional name/email for the audit trail.
source_cloudstringyesCloud the workload currently runs on.
storagearray––
targetsarray–Optional list of target clouds to compare against the source.

No output schema declared.

No examples provided.

get_aws_price ~218

Look up the on-demand Linux hourly + monthly price for an AWS EC2 instance type in us-east-1. Returns vCPUs, memory, hourly USD, and monthly USD (730 hours). For multi-cloud comparisons including OCI, Azure, and GCP, use compare_clouds instead.

NameTypeReqDescription
instance_typestringyesEC2 instance type, e.g. 't3.medium'. Available: c5.2xlarge, c5.large, c5.xlarge, g4dn.xlarge, g5.xlarge, g6.xlarge, g6e.xlarge, m5.2xlarge, m5.4xlarge, m5.large, m5.xlarge, p3.2xlarge, p4d.24xlarge,…

No output schema declared.

No examples provided.

get_azure_price ~190

Look up the on-demand Linux hourly + monthly price for an Azure VM size in eastus. Returns vCPUs, memory, hourly USD, and monthly USD.

NameTypeReqDescription
vm_sizestringyesAzure VM size, e.g. 'D4s_v5'. Available: B1s, B2ms, B2s, B4ms, D16s_v5, D2s_v5, D4s_v5, D8s_v5, E2s_v5, E4s_v5, E8s_v5, F2s_v2, F4s_v2, F8s_v2, NC24ads_A100_v4, NC40ads_H100_v5, NC4as_T4_v3, ND96asr_…

No output schema declared.

No examples provided.

get_gcp_price ~206

Look up the on-demand Linux hourly + monthly price for a GCP Compute Engine machine type in us-east1. Returns vCPUs, memory, hourly USD, and monthly USD.

NameTypeReqDescription
machine_typestringyesGCP machine type, e.g. 'e2-standard-4'. Available: a2-highgpu-1g, a2-highgpu-8g, a2-ultragpu-1g, a3-highgpu-8g, c2-standard-4, c2-standard-8, e2-medium, e2-micro, e2-small, e2-standard-16, e2-standar…

No output schema declared.

No examples provided.

get_price_history ~185

Return the multi-cloud price history for a specific (cloud, sku). cloudprice-mcp persists every weekly auto-refresh as a dated snapshot, so this is the only FinOps tool that can answer 'what did m5.xlarge cost in May?' — neither AWS Calculator nor GCP Estimator preserves historical pricing. Returns the timeseries, total change %, and the earliest/latest data points. Useful for: validating commitment timing, spotting quiet price increases, citing audit-traceable historical numbers to a CFO.

NameTypeReqDescription
cloudstringyes–
sincestring|null–Optional ISO date (YYYY-MM-DD); restricts to snapshots on or after this date.
skustringyesInstance type / SKU name, e.g. m5.xlarge, D2s_v5, e2-standard-2, VM.Standard.E5.Flex.1OCPU

No output schema declared.

No examples provided.

list_tracked_skus ~99

List every (cloud, sku) pair present in the bundled price-history dataset, with how many weekly snapshots exist for each. Use this to discover which SKUs you can call get_price_history on, or to find the biggest-mover SKUs since a given date. Filter by cloud to scope.

NameTypeReqDescription
cloudstring|null––
sincestring|null–Optional ISO date; only consider snapshots on or after this date.

No output schema declared.

No examples provided.

llm_price_changes ~280

What changed in LLM token pricing between two weeks: models that were repriced (with old and new $/1M input and output, and % move), models added, and models removed, across ~3,600 model/provider rows from LiteLLM (direct provider prices) and OpenRouter (routed prices). Backed by a weekly archive kept since 2026-05-23. Use for: 'what got cheaper this week', 'did Anthropic or Bedrock change prices since October', 'new models on Groq this month', 'has Mistral Large's price moved'. Defaults to the latest week vs the week before.

NameTypeReqDescription
limitinteger––
providerstring–Case-insensitive substring of the provider, e.g. 'bedrock', 'anthropic', 'groq'.
querystring–Case-insensitive substring of the model ID, e.g. 'claude', 'llama-3.3'.
sincestring–ISO date. Compare from the latest archived week on or before this date. Default: the week before 'until'.
sourcestring–Restrict to one upstream. Default: both.
untilstring–ISO date. Compare to the latest archived week on or before this date. Default: the latest week.

No output schema declared.

No examples provided.

lookup_extended_model_pricing ~441

Search the extended LLM catalog (~2300 model/provider combinations auto-ingested weekly from two upstreams: LiteLLM's public JSON (direct-provider retail prices for Together AI, Fireworks, Replicate, Groq, Cerebras, Perplexity, regional Bedrock/Azure variants, etc.) and OpenRouter's /api/v1/models (routed prices including OpenRouter's margin). Every row tagged source='litellm' or source='openrouter' so callers can compare direct vs routed pricing for the same model. Complements compare_token_pricing (hand-curated, 19 vetted models). Use this when the user asks about: (a) a model or provider compare_token_pricing doesn't know — 'cheapest place to host Llama 3.1 405B', 'Together AI pricing', 'what Groq charges for Mixtral' — or (b) whether OpenRouter routing is cheaper or more expensive than going direct to Bedrock/Anthropic/OpenAI ('does OpenRouter add margin for Claude 3 Haiku?').

NameTypeReqDescription
limitinteger––
max_context_tokensinteger–Skip models with smaller context. Useful for 'cheapest models that support 200K+ context'.
modestring–Mode filter. Default: any (catalog already excludes embedding/image/audio).
monthly_input_tokensinteger––
monthly_output_tokensinteger––
providerstring–Filter to one provider: 'bedrock', 'fireworks_ai', 'together_ai', 'groq', 'perplexity', 'replicate', 'openrouter' (for routed prices), etc.
querystring–Case-insensitive substring matched against the model ID. E.g. 'llama-3.1-70b' matches every Llama 3.1 70B variant on every host.
sourcestring–Filter to one upstream source. 'litellm' = direct-provider retail prices. 'openrouter' = OpenRouter routed prices (includes their margin). Default: both — useful for cross-source comparison.

No output schema declared.

No examples provided.

model_retirements ~250

Which LLMs providers are retiring: models whose retirement date (from LiteLLM's feed, refreshed weekly) falls within the window, across Bedrock, Azure OpenAI / AI Foundry, Vertex AI, OpenAI, Anthropic and others, plus those retired in the last 90 days. For each: the date, days left, and the newest same-family model on the same provider that is not retiring, with its list price change. Use for: 'which of our models are being retired', 'is Claude 3.5 Sonnet on Bedrock going away', 'what replaces gpt-4o on Azure'. analyze_ai_spend and review_agentcore flag retiring models on your bill and in your deployment automatically.

NameTypeReqDescription
modelstring–A model name to check, e.g. 'claude 3.5 sonnet' or 'gpt-4o'.
providerstring–Catalogue provider, e.g. 'bedrock', 'azure_openai', 'vertex', 'openai'.
top_ninteger–How many models to return, soonest first.
within_daysinteger–Look this many days ahead.

No output schema declared.

No examples provided.

optimize_commitment ~249

Compute per-scenario cost / savings / payback for compute commitment options (none, 1yr_no_upfront, 1yr_all_upfront, 3yr_no_upfront, 3yr_partial_upfront, 3yr_all_upfront). Returns each scenario's monthly cost, upfront, 3-year total, savings %, and payback months — plus the recommended scenario by lowest 3-year TCO. Compute-only (storage / database / object / egress are not discounted because most clouds don't offer meaningful commitments on these). Per-family RI tiers come in v0.6.x; v0.6.0 uses cloud-level conservative averages.

NameTypeReqDescription
cloudstring–Cloud to evaluate (default: source_cloud, then 'aws').
computearrayyes–
databasesarray––
egressarray––
multi_azboolean––
object_storagearray––
one_timeobject––
scenariosarray–Subset of commitment scenarios to evaluate. Default: all 6.
source_cloudstring–Cloud the workload currently runs on.
storagearray––

No output schema declared.

No examples provided.

reprice_bill ~172

FinOps benchmarking on the user's actual bill (a local FOCUS 1.x CSV export; nothing is sent anywhere). Works out the vCPU-hours and memory the bill's compute actually used and prices that same capacity at list price on AWS, Azure, GCP and OCI, per instance type and in total, next to what the user really paid. Reports what it could not reprice (GPUs, licensed OS, unknown types) with its cost. Use for: 'what would our bill cost on another cloud', 'are we on the cheapest cloud for this compute', 'is a migration worth looking at'.

NameTypeReqDescription
file_pathstringyesLocal path to a FOCUS export, .csv or .csv.gz.
top_ninteger–How many workload lines to return, largest first.

No output schema declared.

No examples provided.

review_agentcore ~273

Well-Architected review of an Amazon Bedrock AgentCore deployment, run locally on `terraform show -json` output (a saved plan or state; nothing is sent anywhere, no AWS credentials). Coded rules check every Runtime, Harness and Gateway and the IAM, logs and alarms around them: public network, unauthenticated or debug gateways, InvokeModel on every model, secrets in environment variables, idle and lifetime settings, harness caps, log retention, alarms and cost tags. Each finding has severity, pillar, resource address, a Terraform fix and the AWS doc it rests on. Given a FOCUS bill (and a tag such as agent=genie) it adds what the agent costs by component and the prompt-caching and over-list-price savings. Use for: 'review our AgentCore setup', 'is this agent production-ready', 'what does this agent cost and what should we fix'.

NameTypeReqDescription
bill_pathstring–Optional local FOCUS export (.csv or .csv.gz).
plan_pathstringyesLocal path to `terraform show -json` output (.json).
skipsarray–Findings accepted on purpose, reported as skipped.
tagstring–Optional key=value tag that marks this agent's lines in the bill, e.g. agent=genie.

No output schema declared.

No examples provided.

watch_workload ~267

Cost Drift Sentinel — turns cloudprice from query tool into agent capability. First call (no baseline): captures the current per-cloud monthly cost for the workload as a baseline JSON the caller persists. Subsequent calls (with the saved baseline): compute today's cost, compare to baseline, return a structured drift report with per-cloud delta + SKU-level attribution from the price-history dataset. Stateless — no database, no server-side storage. Drop the baseline JSON into a git repo or any durable location. Designed for scheduled agents (GitHub Actions cron, Claude Code's autonomous mode, etc.) to detect 'has this cost moved since I signed off?' between runs.

NameTypeReqDescription
alert_threshold_pctnumber–Drift % that triggers an alert. Defaults to 5%.
baselineobject|null–Previously returned baseline JSON. Pass null on first call to capture a fresh baseline; pass it back on subsequent calls to detect drift.
commitmentstring––
computearray––
databasesarray––
egressarray––
multi_azboolean––
object_storagearray––
one_timeobject––
source_cloudstringyesCloud the workload currently runs on.
storagearray––

No output schema declared.

No examples provided.

Install

How do I install the Cloudprice MCP server?

Cloudprice runs locally as a PyPI package, launched with uvx cloudprice-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · cloudprice-mcp

# add to Claude Code
claude mcp add albaker-group-cloudprice-mcp -- uvx cloudprice-mcp
Common questions

What is the Cloudprice MCP server?

Cloudprice is an MCP server listed in the public MCP registry as io.github.Albaker-Group/cloudprice-mcp. Multi-cloud + LLM pricing for AI agents: AWS/Azure/GCP/OCI, RI break-even, TCO, price history. This page covers its PyPI package (cloudprice-mcp).

Is the Cloudprice MCP server safe to use?

Cloudprice scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Cloudprice MCP server expose?

Cloudprice exposes 39 tools: get_aws_price, get_azure_price, get_gcp_price, compare_clouds, compare_compute_inventory, and 34 more. Their descriptions and schemas cost roughly 8,472 tokens of context every time the server is loaded.

Is the Cloudprice MCP server still maintained?

Cloudprice 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.

What licence is the Cloudprice MCP server under?

Cloudprice declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.