cloudcostwise
PYPI · CLOUDCOSTWISE
Find AWS waste with your own read-only credentials. Runs locally. Nothing is sent unless you opt in.
Available components
Last scanned (7 hours ago)
Scores higher than 91% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to cloudwise-app/cloudcostwise). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 391 tokens (~97/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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 +18
- Tool safety: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: fail → pass ▲ functional
- Licence: FSL-1.1-ALv2 → Apache-2.0 functional
- Package version: 0.1.17 → 0.1.18 functional
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.16 → 0.1.17 functional
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.1.15 → 0.1.16 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.1.14 → 0.1.15 functional
- 26 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.13 → 0.1.14 functional
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 pypi/cloudcostwise@0.1.18
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 | cloudwise-app/cloudcostwise |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/cloudwise-app/cloudcostwise/.github/workflows/release.yml@refs/tags/v0.1.18 |
| Rekor log index | 3691685881 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:93ae14126b76d5d1d3510f9bcfb433309c487e91dee9558480edce8f144ad55d |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| No linked repository | 1 |
| 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 →
explain_finding ~49
Explain one finding: what was detected, the threshold, the pricing used, why it is waste, the risk of acting, and how validated this check is.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
fix_guidance ~48
How to fix one finding: the recommended action and, where known, the AWS CLI command, as text for the user to review. Never executes anything.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_findings ~49
List findings from the last scan, with ids, optionally filtered by waste type or a minimum monthly saving in USD.
| Name | Type | Req | Description |
|---|---|---|---|
| min_monthly_savings | number | – | – |
| waste_type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan ~134
Scan the user's AWS account for waste with their local credentials (read-only; any non-read AWS call is refused). Takes 30-60 s per region; up to 4 regions run at once. COST: the RI/Savings Plans checks call Cost Explorer, billed by AWS at $0.01 per request (a few cents a scan); tell the user before running, and pass include_cost_explorer=false to skip them. regions: comma-separated, or 'all'; default us-east-1 plus the profile's region.
| Name | Type | Req | Description |
|---|---|---|---|
| include_cost_explorer | boolean | – | – |
| profile | – | – | – |
| regions | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the cloudcostwise MCP server?
cloudcostwise runs locally as a PyPI package, launched with uvx cloudcostwise. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cloudcostwise
claude mcp add cloudwise-app-cloudcostwise -- uvx cloudcostwise
What is the cloudcostwise MCP server?
cloudcostwise is an MCP server listed in the public MCP registry as io.github.cloudwise-app/cloudcostwise. Find AWS waste with your own read-only credentials. Runs locally. Nothing is sent unless you opt in. This page covers its PyPI package (cloudcostwise).
Is the cloudcostwise MCP server safe to use?
cloudcostwise scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 cloudcostwise MCP server expose?
cloudcostwise exposes 4 tools: scan, list_findings, explain_finding, fix_guidance. Their descriptions and schemas cost roughly 280 tokens of context every time the server is loaded.
Is the cloudcostwise MCP server still maintained?
cloudcostwise 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 cloudcostwise MCP server under?
cloudcostwise declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.