io.github.spidgorny/greenops-scan

greenops-scan

Find wasted cloud spend and carbon emissions across your AWS or GCP account.

494/wk GitHub npm

No known CVEs

MIT license

Maintained

Last commit 73d ago

Works with most clients

Transport: stdio, sse

0 tools

Grade F

MCPpedia last refreshed this data 17h ago

Edit this pageView history

io.github.spidgorny/greenops-scan is an MCP server that find wasted cloud spend and carbon emissions across your AWS or GCP account. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 54/100 on MCPpedia's security, maintenance and efficiency rubric.

Cloud

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-spidgorny-greenops-scan": {
      "args": [
        "-y",
        "greenops-scan"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-spidgorny-greenops-scan)](https://mcppedia.org/s/io-github-spidgorny-greenops-scan)

Read me

What io.github.spidgorny/greenops-scan does

Find wasted cloud spend and carbon emissions across your AWS or GCP account.

Test This Server

This server supports HTTP transport. Be the first to test it - help the community know if it works.

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

54/100across 5 weighted dimensions

How we score →

0255075100

−46

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked greenops-scan against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.spidgorny/greenops-scan safe to use?: io.github.spidgorny/greenops-scan has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under MIT.
How do I install io.github.spidgorny/greenops-scan?: io.github.spidgorny/greenops-scan supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.spidgorny/greenops-scan?: io.github.spidgorny/greenops-scan is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is io.github.spidgorny/greenops-scan actively maintained?: io.github.spidgorny/greenops-scan is recently maintained - last commit was 73 days ago.

Similar servers

Others in cloud

View all →

io.github.firebase/firebase-mcp94

Gives AI development tools Firebase-specific capabilities and expertise.

4.5k 3

io.github.ruvnet/flow-nexus94

Cloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation

106 4

io.github.patrickchugh/terravision91

Draw cloud architecture diagrams with official AWS, Azure and GCP icons from a prompt or Terraform.

1.7k 9

Mcp Server Kubernetes90

MCP Server for kubernetes management commands

1.6k 22

MCP Security Weekly

Get CVE alerts and security updates for io.github.spidgorny/greenops-scan and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

How it works

Run npx greenops-scan in any terminal.

Pick your AWS profile and region.

The scanner uses read-only AWS APIs to check EC2, S3, ECS/Fargate, EKS, Lambda, RDS, ElastiCache, CloudFront, EBS snapshots/AMIs, Bedrock, and VPC endpoints.

Get a colorized report with estimated monthly savings in dollars and CO₂, plus suggested aws CLI commands to review.

For automation or CI:

npx greenops-scan --non-interactive --json --profile prod --region eu-west-1

Common findings

Idle EC2 instances — running at low CPU for 30 days

Orphaned EBS volumes and old snapshots — paying for storage no one uses

Over-provisioned Fargate services — sized for peak traffic that never happens

x86 Lambda functions that could run on Graviton/ARM

Old RDS databases and non-production Multi-AZ deployments

Untiered S3 data and accumulating object versions

Empty ECS/EKS clusters and missing autoscaling

Idle Bedrock provisioned throughput and stale agents

Frequently Asked Questions

Is io.github.spidgorny/greenops-scan safe to use?

io.github.spidgorny/greenops-scan has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under MIT.

How do I install io.github.spidgorny/greenops-scan?

io.github.spidgorny/greenops-scan supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.spidgorny/greenops-scan?

io.github.spidgorny/greenops-scan is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.

Is io.github.spidgorny/greenops-scan actively maintained?

io.github.spidgorny/greenops-scan is recently maintained - last commit was 73 days ago.

Find AWS cost waste in one command

Free CLI that scans your AWS account for idle and over-provisioned resources, then shows how much money and carbon you can save.

npx greenops-scan

How it works

Run npx greenops-scan in any terminal.
Pick your AWS profile and region.
The scanner uses read-only AWS APIs to check EC2, S3, ECS/Fargate, EKS, Lambda, RDS, ElastiCache, CloudFront, EBS snapshots/AMIs, Bedrock, and VPC endpoints.
Get a colorized report with estimated monthly savings in dollars and CO₂, plus suggested aws CLI commands to review.

For automation or CI:

npx greenops-scan --non-interactive --json --profile prod --region eu-west-1

Common findings

Idle EC2 instances — running at low CPU for 30 days
Orphaned EBS volumes and old snapshots — paying for storage no one uses
Over-provisioned Fargate services — sized for peak traffic that never happens
x86 Lambda functions that could run on Graviton/ARM
Old RDS databases and non-production Multi-AZ deployments
Untiered S3 data and accumulating object versions
Empty ECS/EKS clusters and missing autoscaling
Idle Bedrock provisioned throughput and stale agents

Security

greenops-scan runs locally and uses read-only AWS APIs. Your credentials never leave your machine.

Need team-wide reporting?

GreenOps Cloud adds recurring scans, shared dashboards, and remediation workflows: https://greenops.cloud