GreenOps Scan

io.github.spidgornyPublished by GitHub account spidgornyv0.1.39Updated Nov 11, 2026

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

The publisher's own server: scan.mx Email Diagnostics

VerifiedSTDIODesktop onlyCloud & InfrastructureFinance

Overview

AI-generated overview

Local CLI scanner that inspects an AWS account for idle or over-provisioned resources and reports estimated dollar and CO2 savings.

What you can do
  • Scan an AWS account across EC2, S3, ECS/Fargate, EKS, Lambda, RDS, ElastiCache, CloudFront, EBS snapshots/AMIs, Bedrock and VPC endpoints using read-only APIs
  • Produce a colorized report of estimated monthly savings in dollars and CO2
  • List suggested aws CLI commands for reviewing flagged resources
  • Run non-interactively with JSON output for automation or CI pipelines
When to use it
Useful when you want a quick, free read-only pass over an AWS account to find wasted spend and carbon, or to feed cost findings into CI or automation via JSON output.
Requirements
Runs as a local process via npx, so Node.js and network access are needed. Requires an AWS profile and region selected at run time; no environment variables or headers are declared.
Before you install
It reads your AWS account through your local credentials, so review the package before running it. It only reports findings and suggested commands; acting on them changes infrastructure. The README points to a paid cloud product for team-wide reporting.

Installation

In SourceWeft

  1. Open GreenOps Scan in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

bash
npx greenops-scan

[Demo]

How it works

  1. Run npx greenops-scan in any terminal.
  2. Pick your AWS profile and region.
  3. 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.
  4. Get a colorized report with estimated monthly savings in dollars and CO₂, plus suggested aws CLI commands to review.

For automation or CI:

bash
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

Source: README.md at commit a1b0948

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.39LatestNov 11, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Scan integrations

scan.mx Email Diagnostics

mx.scanOfficial publisher

Remote MCP server that lets an assistant run graded email deliverability and DNS checks on a domain, covering MX, SPF, DKIM, DMARC, blacklists and more.

Streamable HTTPWeb executable
Developer Tools9 toolsOct 25, 2026

Psyseal scan

Published by GitHub account psyseal

A local, read-only MCP server that scans AI agent folders on your machine for exposed plaintext secrets, costly heartbeats and bloated or planted memory.

STDIODesktop only
Security & MonitoringNot validated yetNov 11, 2026

MTG Trade Scan

fr.mtg-trade

Scans Magic: The Gathering binder photos, turning uploaded page images into processed scan jobs, with free daily pages and paid credits.

Streamable HTTPWeb executable
Business & Commerce5 toolsNov 6, 2026

mcp-guard

Published by GitHub account diegoperezg7

Security scanner for MCP servers that checks tool lists for poisoning, shadowing, excessive permissions, leaked secrets and weak transports.

STDIODesktop only
Developer Tools4 toolsNov 4, 2026

PredictionScan

Published by GitHub account JordanKarst

Read-only access to Polymarket prediction-market odds, price history, flow, large trades, trader stats and related news for event research.

Streamable HTTPWeb executable
Web Search & Scraping11 toolsNov 10, 2026