Is Finopsmcp safe to use?

Finopsmcp has an HVTrust score of 81.0/100 (Grade A), ranked #163 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Finopsmcp?

Finopsmcp scores 81.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 20 GitHub stars and is categorized under MCP Servers.

Finopsmcp

Repository

Website

The headless FinOps intelligence layer: API-first, agent-first cost control for cloud + AI. Connect your cloud stack in Claude, Cursor, or the terminal, and gate what agents do to your infra before they act. Propose-only. Open source, local-first.

MCP Servers Python Listed Apache-2.0

Is Finopsmcp safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.9 / 10

Provenance Attested

Signed commits 100%

Last push 10d ago

Advisories None known

Compare Finopsmcp

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Finopsmcp scores 81.0/100 (Grade A), ranked #163 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.9/10; 100% of recent commits are signed; no published advisory affects its latest release (finops-mcp); last pushed 2026-10-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Finopsmcp could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 7.9 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +2.3 → 83.3 A · #53 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Finopsmcp and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/getnable/finopsmcp, Apache-2.0, last pushed 2026-10-31. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Strong

OpenSSF Scorecard rates the repository's practices 7.9/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protectionn/a
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies5
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection -1

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10
Published packages Linked and attested
- PyPI finops-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: finops-mcp 0.12.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-09-23 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Finopsmcp’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Finopsmcp compares in MCP Servers

Bars show each HVTrust score; the tick marks Finopsmcp’s 81.0.

Where the 81.0 comes from

HVTrust dimensions vs the MCP Servers average

81.0 / 100 · 100.0% confidence

Finopsmcp MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

22.4 / 25

11.6 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

15.2 / 17

2.9 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

15.5 / 20

3.3 above avg 12.2

AdoptionLog-scaled stars · package downloads

6.2 / 20

1.4 below avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-09

Rank Moved

Rank rose 10 spots (#166 → #156)

2026-11-02

Rank Moved

Rank dropped 17 spots (#129 → #146)

2026-11-01

Rank Moved

Rank rose 19 spots (#148 → #129)

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with another agent View MCP Servers Report missing data

46.1

Activity sub-score · out of 100

#79

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-10-31

10 days ago

Commits (4 wk)

Downloads (7d)

202

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #156

Analysis

Activity Inputs

46.1 / 100

StarsRepository reach

7.9 / 30

FreshnessLast push recency

23.6 / 25

ActivityRecent commits

13.0 / 25

CommunityFork signal

1.4 / 20

Common questions about Finopsmcp

Public supply-chain signals for Finopsmcp are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Finopsmcp carries less obvious unverified-evidence risk than projects with thin signals.

Does Finopsmcp publish package provenance?

Yes. Finopsmcp's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Finopsmcp have an OpenSSF Scorecard?

Finopsmcp has an OpenSSF Scorecard score of 7.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Finopsmcp actively maintained?

Maintained. Last push was 10 days ago.

What license does Finopsmcp use?

Finopsmcp ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Finopsmcp's commits signed?

100% of the last 100 commits to Finopsmcp are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Finopsmcp appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

3 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Finopsmcp's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Finopsmcp?

For maintainers

HVTrust scores Finopsmcp from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-09

Rank Moved

Rank rose 10 spots (#166 → #156)

2026-11-02

Rank Moved

Rank dropped 17 spots (#129 → #146)

2026-11-01

Rank Moved

Rank rose 19 spots (#148 → #129)

2026-10-31

Rank Moved

Rank rose 16 spots (#164 → #148)

2026-10-29

Rank Moved

Rank dropped 13 spots (#145 → #158)

2026-10-27

Rank Moved

Rank dropped 14 spots (#125 → #139)

2026-10-25

Rank Moved

Rank dropped 34 spots (#91 → #125)

2026-10-25

HVTrust Changed

HVTrust down 3.1pts (85.3 → 82.2)

2026-10-25

Activity Score Changed

Activity score down 11pts (59 → 48)

2026-09-27

Rank Moved

Rank rose 21 spots (#107 → #86)

2026-09-25

Grade Changed

Trust grade B → A

2026-09-25

Rank Moved

Rank rose 104 spots (#209 → #105)

2026-09-25

HVTrust Changed

HVTrust up 7.6pts (75.9 → 83.5)

2026-09-25

Activity Score Changed

Activity score up 12pts (47 → 59)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 511 spots (#725 → #214)

2026-09-23

HVTrust Changed

HVTrust up 45.2pts (30.3 → 75.5)

2026-09-22

Newly Listed

First tracked at rank #725

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 10 spots (#156 → #166)

2026-09-16

Grade Changed

Trust grade A → B

2026-09-15

Rank Moved

Rank dropped 11 spots (#128 → #139)

2026-09-12

Grade Changed

Trust grade B → A

2026-09-12

Rank Moved

Rank rose 18 spots (#138 → #120)

2026-09-10

Grade Changed

Trust grade A → B

2026-09-10

Rank Moved

Rank dropped 27 spots (#111 → #138)

2026-09-05

Rank Moved

Rank dropped 21 spots (#74 → #95)

2026-09-02

Grade Changed

Trust grade D → A

2026-09-02

Rank Moved

Rank rose 628 spots (#701 → #73)

2026-09-02

HVTrust Changed

HVTrust up 33.4pts (49.0 → 82.4)

2026-09-01

Rank Moved

Rank dropped 32 spots (#669 → #701)

2026-08-31

Rank Moved

Rank dropped 36 spots (#633 → #669)

2026-08-30

Rank Moved

Rank dropped 14 spots (#619 → #633)

2026-08-29

Rank Moved

Rank dropped 36 spots (#583 → #619)

2026-08-28

Rank Moved

Rank dropped 18 spots (#565 → #583)

2026-08-27

Rank Moved

Rank dropped 15 spots (#550 → #565)

2026-08-26

Rank Moved

Rank dropped 81 spots (#469 → #550)

2026-08-24

Rank Moved

Rank dropped 15 spots (#454 → #469)

2026-08-22

Rank Moved

Rank rose 17 spots (#473 → #456)

2026-08-19

Rank Moved

Rank dropped 10 spots (#465 → #475)

2026-08-17

Rank Moved

Rank rose 12 spots (#477 → #465)

2026-08-13

Rank Moved

Rank dropped 15 spots (#453 → #468)

GitHub → Website → PyPI: finops-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/finopsmcp.svg)](https://hvtracker.net/agents/finopsmcp)
            
HTML:
            <a href="https://hvtracker.net/agents/finopsmcp"><img src="https://hvtracker.net/badge/finopsmcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Finopsmcp

How Finopsmcp could raise its score

Chain of custody

Source Signed

Review and release Strong

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Finopsmcp compares in MCP Servers

Where the 81.0 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Finopsmcp

AI agent surface

Maintain Finopsmcp?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers