Compare Cloud Costs
NPM · @COMPARECLOUDCOSTS/MCP-SERVER
Compare cloud and AI model pricing across AWS, Azure, GCP, Oracle, DigitalOcean and more.
Available components
Last scanned (21 hours ago)
Scores higher than 34% of npm servers
Category Cloud Infrastructure
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 453 tokens (~113/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 64
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@comparecloudcosts/mcp-server@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compare_cloud_pricing ~162
Query and compare multi-cloud compute, database, and serverless pricing across AWS, Azure, Google Cloud, Oracle, DigitalOcean, Alibaba, and Cloudflare.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Product category: vm, database, serverless, storage, ai, networking, etc. |
| min_ram_gb | number | – | Minimum required RAM memory in Gigabytes |
| min_vcpu | number | – | Minimum required vCPUs for instance configurations |
| provider | string | – | Filter by provider ID: aws, azure, gcp, oracle, digitalocean, alibaba, cloudflare |
| region | string | – | Target deployment geography or region (e.g. us-east-1, eastus, us-central1, sa-east-1) |
No output schema declared.
No examples provided.
estimate_workload_architecture ~75
Calculates end-to-end multi-cloud cost benchmarks for realistic full-stack architectures (VMs + Managed DB + Load Balancers + Storage + Egress).
| Name | Type | Req | Description |
|---|---|---|---|
| workload_id | string | yes | Pre-modeled workload slug (e.g. three-tier-web-app, ai-rag-pipeline, high-throughput-api, batch-processing) |
No output schema declared.
No examples provided.
lookup_datacenter_compliance ~100
Checks global data center availability, region locations, and compliance certifications (SOC 2, ISO 27001, HIPAA, PCI-DSS, FedRAMP).
| Name | Type | Req | Description |
|---|---|---|---|
| compliance_standard | string | – | Compliance standard code: soc2, iso27001, hipaa, pci-dss, fedramp, gdpr |
| country_or_city | string | – | Filter by geographical location (e.g. Brazil, Germany, Tokyo, Virginia) |
No output schema declared.
No examples provided.
search_ai_models ~116
Search token pricing (Input, Output, Prompt Caching) and context windows for AI LLMs across OpenAI, Anthropic, DeepSeek, Mistral, Meta Llama, and Cohere.
| Name | Type | Req | Description |
|---|---|---|---|
| model_family | string | – | Model family name (e.g. gpt-4o, claude-3-5-sonnet, deepseek-r1, mistral-large) |
| provider | string | – | AI model provider: openai, anthropic, deepseek, mistral, cohere, google |
No output schema declared.
No examples provided.
How do I install the Compare Cloud Costs MCP server?
Compare Cloud Costs runs locally as an npm package, launched with npx -y @comparecloudcosts/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @comparecloudcosts/mcp-server
claude mcp add com-comparecloudcosts-mcp-server -- npx -y @comparecloudcosts/mcp-server
What is the Compare Cloud Costs MCP server?
Compare Cloud Costs is an MCP server listed in the public MCP registry as com.comparecloudcosts/mcp-server. Compare cloud and AI model pricing across AWS, Azure, GCP, Oracle, DigitalOcean and more. This page covers its npm package (@comparecloudcosts/mcp-server).
Is the Compare Cloud Costs MCP server safe to use?
Compare Cloud Costs scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 Compare Cloud Costs MCP server expose?
Compare Cloud Costs exposes 4 tools: compare_cloud_pricing, search_ai_models, estimate_workload_architecture, lookup_datacenter_compliance. Their descriptions and schemas cost roughly 453 tokens of context every time the server is loaded.
Is the Compare Cloud Costs MCP server still maintained?
Compare Cloud Costs is still listed as active in the MCP registry. We last reached this channel on 4 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 Compare Cloud Costs MCP server under?
Compare Cloud Costs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.