Is Finopsmcp safe to use?

Finopsmcp has an HVTrust score of 49.2/100 (Grade D), ranked #465 of 1283 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 49.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 15 GitHub stars and is categorized under MCP Servers.

Finopsmcp

getnable/finopsmcp

The headless FinOps intelligence layer: API-first, agent-first cost control for cloud + AI. Connect your cloud stack in

MCP Servers Python Grade D Listed Apache-2.0

49.2/100

Rank #465 of 1283

Compare Finopsmcp

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-12 · 0d ago

Recent change

Rank +1

Is Finopsmcp safe? Finopsmcp scores 49.2/100 (Grade D), ranked #465 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.9/10; 56% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#155 FAOSTAT MCP — 50.4 (C) → #156 Marketplaces MCP (RU) — Wildberries & Ozon — 50.0 (C) → #158 SharePoint MCP Server — 48.9 (D) → #159 p6xer MCP Server — 48.8 (D) →

Quick Trust Read

What Would Improve It

Expose more independent signals, such as package metadata, provenance, or public usage evidence.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 17 spots (#449 → #466)

2026-08-08

Newly Listed

First tracked at rank #448

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.9/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for Finopsmcp View MCP Servers Report missing data

58.6

Activity sub-score · out of 100

#157

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-12

today

Commits (4 wk)

123

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #466

Analysis

HVTrust Dimensions vs MCP Servers

49.2 / 100 · 67.0% confidence

Finopsmcp MCP Servers average (761 agents)

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

18.9 / 25

13.9 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

14.4 / 17

5.6 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.6 above avg 12.4

AdoptionLog-scaled stars · package downloads

2.9 / 20

2.9 below avg 5.8

Activity Inputs

58.6 / 100

StarsRepository reach

7.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

6.9 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

56%

of last 100 commits verified

Security-Policy 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Code-Review 0

Maintained 0

Token-Permissions 10

Binary-Artifacts 10

Pinned-Dependencies 5

Vulnerabilities 10

CII-Best-Practices 0

Signed-Releases -1

SAST 10

Branch-Protection -1

Fuzzing 0

Packaging 10

License 10

Contributors 0

CI-Tests 10

Is Finopsmcp safe?

Public trust evidence for Finopsmcp is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

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 6.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?

Actively maintained. The repository was pushed to within the last 1 day(s).

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?

56% 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

medium confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

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

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-08-10

Rank Moved

Rank dropped 17 spots (#449 → #466)

2026-08-08

Newly Listed

First tracked at rank #448

GitHub → 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.3 · Raw JSON