Finopsmcp
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.
Is Finopsmcp safe? Strong public trust posture, backed by multiple independent signals.
Compare Finopsmcp
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Finopsmcp scores 83.4/100 (Grade A), ranked #107 of 1325 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.4/10; 73% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Finopsmcp compares in MCP Servers
- #42 Reversecore MCP 83.6 +0.2
- #43 Google Flights MCP (fli) 83.5 +0.1
- #44 Finopsmcp 83.4 this agent
- #45 Markdown Vault MCP 83.4 ±0
- #46 Zotero MCP 83.4 ±0
Bars show each HVTrust score; the tick marks Finopsmcp’s 83.4.
Where the 83.4 comes from
HVTrust dimensions vs the MCP Servers average
83.4 / 100 · 100.0% confidenceFinopsmcp MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
59.1 / 100Supply Chain Trust
Common questions about Finopsmcp
Does Finopsmcp publish package provenance?
Does Finopsmcp have an OpenSSF Scorecard?
Is Finopsmcp actively maintained?
What license does Finopsmcp use?
Are Finopsmcp's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/finopsmcp)
<a href="https://hvtracker.net/agents/finopsmcp"><img src="https://hvtracker.net/badge/finopsmcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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