updated 2026-09-26 06:32 UTC

Zenmoney MCP

artarasov/zenmoney-mcp

MCP server for ZenMoney — manage your personal finances from Claude, Cursor, and other AI clients

MCP Servers TypeScript Listed MIT

Is Zenmoney MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.7 / 10
Provenance None
Signed commits 27%
Last push 22d ago
Compare Zenmoney MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Zenmoney MCP scores 41.6/100 (Grade D), ranked #1136 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.7/10; 27% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Zenmoney MCP compares in MCP Servers

  1. #668 idealo MCP Server 41.6 ±0
  2. #669 Awesome Agent Skills MCP 41.6 ±0
  3. #670 Zenmoney MCP 41.6 this agent
  4. #671 Just MCP Server 41.5 −0.1
  5. #672 PostgreSQL performance Tuner MCP Server 41.4 −0.2

Bars show each HVTrust score; the tick marks Zenmoney MCP’s 41.6.

Where the 41.6 comes from

HVTrust dimensions vs the MCP Servers average

41.6 / 100 · 100.0% confidence

Zenmoney MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.5 / 25
6.8 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
9.9 / 17
2.3 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.2 above avg 12.1
AdoptionLog-scaled stars · package downloads
3.1 / 20
4.1 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 440 spots (#691 → #1131)
2026-09-23
HVTrust Changed
HVTrust up 10.8pts (31.0 → 41.8)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Zenmoney MCP View MCP Servers Report missing data
42.2
Activity sub-score · out of 100
#670
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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 22 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
19
Forks
5
Last Push
2026-09-04
22 days ago
Commits (4 wk)
4
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▼1
was #1135

Analysis

Activity Inputs

42.2 / 100
StarsRepository reach
7.8 / 30
FreshnessLast push recency
21.9 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
3.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
1.7 / 10
OpenSSF Scorecard · scanned Sep 20, 2026
Signed Commits
27%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 3
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions -1
Vulnerabilities 0

Common questions about Zenmoney MCP

Public trust evidence for Zenmoney MCP 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 Zenmoney MCP publish package provenance?
No published build provenance is currently detected for Zenmoney MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Zenmoney MCP have an OpenSSF Scorecard?
Zenmoney MCP has an OpenSSF Scorecard score of 1.7/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 Zenmoney MCP actively maintained?
Maintained. Last push was 22 days ago.
What license does Zenmoney MCP use?
Zenmoney MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Zenmoney MCP's commits signed?
26% of the last 100 commits to Zenmoney MCP 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
Zenmoney MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Zenmoney MCP'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
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-04
Activity Resumed
Activity resumed
2026-08-26
Activity Went Stale
No commits for 90 days
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: Anthropic

Maintain Zenmoney MCP?

For maintainers

HVTrust scores Zenmoney MCP 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
Rank 17HVTrust 3Listed 2Surface 1Surface 1Stale 1Scorecard 1Score 1Fresh 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 440 spots (#691 → #1131)
2026-09-23
HVTrust Changed
HVTrust up 10.8pts (31.0 → 41.8)
2026-09-22
Newly Listed
First tracked at rank #691
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank rose 15 spots (#1129 → #1114)
2026-09-07
Rank Moved
Rank dropped 25 spots (#1086 → #1111)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1072 → #1086)
2026-09-05
Rank Moved
Rank dropped 46 spots (#1026 → #1072)
2026-09-04
Activity Resumed
Activity resumed
2026-09-04
Rank Moved
Rank rose 128 spots (#1154 → #1026)
2026-09-04
HVTrust Changed
HVTrust up 7.4pts (33.9 → 41.3)
2026-09-04
Activity Score Changed
Activity score up 22pts (22 → 45)
2026-09-03
Rank Moved
Rank dropped 42 spots (#1112 → #1154)
2026-09-02
Rank Moved
Rank dropped 46 spots (#1066 → #1112)
2026-09-01
Rank Moved
Rank dropped 40 spots (#1026 → #1066)
2026-08-31
Rank Moved
Rank dropped 34 spots (#992 → #1026)
2026-08-30
Rank Moved
Rank dropped 52 spots (#940 → #992)
2026-08-29
Rank Moved
Rank dropped 52 spots (#888 → #940)
2026-08-28
Scorecard Added
OSSF Scorecard: 1.5/10
2026-08-28
Rank Moved
Rank rose 382 spots (#1270 → #888)
2026-08-28
HVTrust Changed
HVTrust up 18.2pts (16.1 → 34.3)
2026-08-26
Activity Went Stale
No commits for 90 days
2026-08-26
Rank Moved
Rank dropped 26 spots (#1237 → #1263)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1207 → #1232)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-08-12
Rank Moved
Rank dropped 17 spots (#1185 → #1202)
2026-08-10
Rank Moved
Rank dropped 72 spots (#1112 → #1184)
2026-08-08
Newly Listed
First tracked at rank #1124
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 41.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/zenmoney-mcp.svg)](https://hvtracker.net/agents/zenmoney-mcp)
HTML:
<a href="https://hvtracker.net/agents/zenmoney-mcp"><img src="https://hvtracker.net/badge/zenmoney-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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