cloudcostwise

Name: cloudcostwise
Author: cloudwise-app

作者：cloudwise-app版本 0.1.18i★ –i在你的电脑上运行

注册名称io.github.cloudwise-app/cloudcostwise

安装

概览

作者提供的说明（英文原文）

Find AWS waste with your own read-only credentials. Runs locally. Nothing is sent unless you opt in.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： AWS_PROFILE

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "cloudcostwise": {
      "command": "uvx",
      "args": [
        "cloudcostwise",
        "mcp"
      ],
      "env": {
        "AWS_PROFILE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add cloudcostwise --env AWS_PROFILE=your-value -- uvx cloudcostwise mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "cloudcostwise": {
      "command": "uvx",
      "args": [
        "cloudcostwise",
        "mcp"
      ],
      "env": {
        "AWS_PROFILE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "cloudcostwise": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "cloudcostwise",
        "mcp"
      ],
      "env": {
        "AWS_PROFILE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

AWS_PROFILE env
AWS profile to scan with (read-only access is enough). Defaults to the standard credential chain.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 cloudwise-app 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 1385 个服务器的 0%
发布到注册中心的时间比此分类中其他 1385 个服务器的 96% 更新
基础检查结果等于或优于此分类中其他 1385 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

cloudcostwise 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.18）于昨天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

cloudcostwise

Find AWS waste from your terminal or your AI assistant. cloudcostwise runs CloudWise's free waste checks on your own machine, with your own read-only AWS credentials.

See it first: a real scan of our own test account, with its findings, fixes and dollars, and nothing to install: cloudcostwise.io/sample-scan.

Nothing is sent to CloudWise unless you choose to share a summary at the end. The only network calls are AWS API calls in your account, plus that one optional POST. No signup, no IAM role for a third party, no tracking. Used through an AI assistant (MCP), the findings go to that assistant like any tool output. See Sharing a summary.
It cannot change anything. Every AWS call goes through a guard that refuses any operation that isn't a Describe, List, Get, Search or Lookup, whatever your credentials allow.
20 of CloudWise's 46 service checks: EC2, Lambda, SageMaker, WorkSpaces, Lightsail, EBS, S3, EFS, ECR, RDS, DynamoDB, ElastiCache, Elastic IPs, NAT gateways and load balancers, VPC endpoints, dangling DNS records, CloudWatch logs and dashboards, security posture, RI/Savings Plans opportunities, and Compute Optimizer.

Install and run

pipx install cloudcostwise          # or: uvx cloudcostwise scan

cloudcostwise scan # us-east-1 plus your profile's region cloudcostwise scan --profile prod --regions all cloudcostwise scan --format json > waste.json

Options:

Option	Meaning
`--profile NAME`	AWS profile; otherwise the standard credential chain (env vars, SSO, instance role)
`--regions LIST`	Comma-separated regions, or `all` for every enabled region. Account-level checks (CloudWatch dashboards, orphaned DNS records, RI/Savings Plans) run once, in us-east-1, and are skipped with a warning if it is not listed
`--format table\	markdown\	json`	Output format
`--no-cost-explorer`	Make no Cost Explorer call. AWS bills those at $ 0.01 per request and a scan makes about 8 . Skips the RI/Savings Plans checks
`--parallel N`	Regions scanned at once, each in its own process (default 4 ; `--regions all` takes ~2–3 min instead of ~10)
`--verbose`	Show data warnings (checks that could not read a metric report it as missing, never as zero)

What AWS's free tools don't flag

This tool has 53 proven checks (L2 or above in VALIDATION.md: each fired on a real AWS resource built to trigger it and stayed silent on a healthy twin). 19 of them flag waste that none of AWS's own tools flag, and 11 more go further than the closest AWS check, going by AWS's lists of what its tools cover (Trusted Advisor, Cost Optimization Hub, Compute Optimizer; checked 2026-10-11).

Check	What it finds	Closest AWS check
`ami_orphaned_snapshot`	EBS snapshots left behind by an AMI that was deregistered	None
`classic_lb_migration`	Classic Load Balancers that would cost less as an ALB or NLB	None
`elasticache_data_tiering_opportunity`	Redis OSS or Valkey replication groups on r6g/r7g nodes that would cost less on data-tiering r6gd nodes	None
`elasticache_engine_migration`	Redis OSS or Memcached clusters that would cost about 20% less on Valkey	None
`elasticache_extended_support_cost`	ElastiCache engine versions billed the Extended Support surcharge	None
`empty_log_group`	CloudWatch log groups that have stored nothing for 30+ days	None
`idle_lightsail`	Stopped or idle Lightsail instances that still bill their bundle price	None
`lambda_arm64_migration`	Lambda functions that would cost about 20% less on arm64 (Graviton)	None
`lambda_provisioned_concurrency_idle`	Lambda provisioned concurrency that is paid for and barely used	None
`lightsail_idle_load_balancer`	Idle Lightsail load balancers	None
`lightsail_unattached_disk`	Lightsail disks attached to nothing	None
`lightsail_unattached_static_ip`	Lightsail static IPs attached to nothing	None
`low_traffic_alb`	Application Load Balancers carrying almost no traffic	None
`multiple_eips_per_instance`	Extra Elastic IPs on one instance, each billed as a public IPv4 address	None
`no_lifecycle_efs`	Large EFS file systems with no Infrequent Access or Archive tiering	None
`orphaned_ebs_snapshot`	EBS snapshots whose source volume no longer exists	None
`previous_gen_sagemaker_instance`	SageMaker instances on a previous generation with a cheaper current one	None
`s3_empty_bucket`	Empty S3 buckets left behind for 30+ days	None
`stopped_sagemaker_notebook_storage`	Stopped SageMaker notebook instances whose ML storage volume keeps billing	None
`elasticache_replication_waste`	Replicas kept on non-production ElastiCache replication groups, each billed like a full node	Amazon ElastiCache Multi-AZ clusters: Trusted Advisor's check looks at the same clusters with the opposite aim, alerting when Multi-AZ is inactive and recommending at least one replica per shard. Compute Optimizer, the source of Cost Optimization Hub's idle recommendations, calls a Redis or Valkey cluster idle only when all its nodes are idle over 14 days. None of the three tools documents a check for replicas on a non-production group that is in use (checked 2026-11-02).
`excessive_retention_log_group`	Log groups keeping a year or more of data they are billed to store	Amazon CloudWatch Log Group Retention Period: Trusted Advisor checks log group retention but flags retention shorter than a minimum (365 days by default) for compliance, so long, costly retention passes it.
`idle_efs`	EFS file systems with no mount targets: nothing can read them, and they still bill	Amazon EFS no mount target redundancy: Trusted Advisor checks EFS mount targets for multi-AZ redundancy, not file systems with no mount targets at all, and EFS is not among the resources Compute Optimizer or Cost Optimization Hub cover.
`idle_load_balancer`	Idle Application and Network Load Balancers	Idle Load Balancers: Trusted Advisor flags idle Classic Load Balancers only (Business Support+ or higher); its documentation says Application and Network Load Balancers are not included.
`incomplete_multipart`	Incomplete S3 multipart uploads whose stored parts keep billing	Amazon S3 Incomplete Multipart Upload Abort Configuration: Trusted Advisor flags buckets whose lifecycle configuration lacks a rule to abort incomplete multipart uploads after 7 days; it does not find the incomplete uploads that are already stored and billing.
`lambda_excessive_timeout`	Lambda timeouts set far above what the function needs	AWS Lambda functions with excessive timeouts: Trusted Advisor flags functions where more than 10% of invocations time out; it does not flag a configured timeout set far above the function's real duration.
`no_retention_log_group`	Log groups set to never expire, so they grow every month	Amazon CloudWatch Log Group Retention Period: Trusted Advisor checks log group retention but flags retention below a minimum, so a log group set to never expire passes it.
`old_ecr_images`	Old ECR images still billed for storage	Amazon ECR Repository without lifecycle policy configured: Trusted Advisor checks that an ECR repository has a lifecycle policy; it does not flag the old images already stored.
`oversized_sagemaker_endpoint`	SageMaker endpoints serving traffic on bigger instances than they need	Idle recommendation for SageMaker endpoints: Compute Optimizer flags SageMaker endpoints with zero invocations over 14 days but gives no rightsizing for endpoints that serve traffic on oversized instances.
`s3_rapid_growth`	S3 buckets whose Standard storage at least doubled in 30 days and grew by 10 GB or more	Amazon S3 Bucket Lifecycle Policy Configured: Trusted Advisor's S3 cost checks (lifecycle policy configured, incomplete multipart upload abort, version-enabled buckets without a lifecycle policy) look at bucket configuration, not at how fast a bucket is growing. Neither Compute Optimizer nor Cost Optimization Hub lists S3 among its resource types, so none of the three tools documents a check for a bucket that grows quickly (checked 2026-11-03).
`untagged_ecr_images`	Untagged ECR images still billed for storage	Amazon ECR Repository without lifecycle policy configured: Trusted Advisor checks that an ECR repository has a lifecycle policy; it does not flag the untagged images already stored.

For idle EC2, RDS and NAT gateways, rightsizing and Savings Plans, AWS's tools cover the same ground: use them too. Trusted Advisor's cost checks need a Business, Enterprise or Unified Operations support plan; Cost Optimization Hub and Compute Optimizer are free.

The hosted CloudWise product adds 22 more proven checks that none of AWS's tools flag, across AWS Backup, AppSync, CloudFront, Elastic Beanstalk, FSx, Glue, KMS, Kinesis, Route 53, Step Functions.

Excerpt of a real scan of our test account (cloudcostwise 0.1.15, us-east-1, 2026-10-27). The resources there are deliberately tiny, which is why the amounts are cents:

no_retention_log_group  x6  $0.06/mo

us-east-1 /aws/lambda/cwfx-clo464-docdb-connect $0.01/mo us-east-1 /aws/lambda/cwfx-ec-hold-driver $0.01/mo us-east-1 /aws/sagemaker/Endpoints/cwfx-w8b-ep-big $0.01/mo us-east-1 /aws/sagemaker/Endpoints/cwfx-w8b-ep-big-control $0.01/mo us-east-1 /aws/sagemaker/Endpoints/cwfx-w8b-ep-idle $0.01/mo us-east-1 /aws/sagemaker/Endpoints/cwfx-w8b-ep-idle-control $0.01/mo old_ecr_images x1 $0.06/mo us-east-1 cwfx-old-ecr-images $0.06/mo untagged_ecr_images x1 $0.02/mo us-east-1 cwfx-untagged-ecr-images $0.02/mo idle_efs x1 $0.01/mo us-east-1 fs-090bfb32bd49de8b7 $0.01/mo

Use it from Claude Code, Codex or

只显示了开头部分；其余内容请在仓库中阅读

cloudcostwise

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“开发者工具”中的其他服务器比较i

常见问题

替代选择

GitHub

Desktop Commander

Cloudflare MCP

作者的 README

cloudcostwise

Install and run

What AWS's free tools don't flag

Use it from Claude Code, Codex or