Monarch MCP Server

Modern MCP server for accessing Monarch Money financial data using AI agents, like Claude. Token-efficient, smart tool d

MCP Servers Python Grade C Listed MIT
56.8/100
Rank #550 of 1320
Compare Monarch MCP Server

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-06-30 · 66d ago
Recent change
Rank +5

Is Monarch MCP Server safe? Monarch MCP Server scores 56.8/100 (Grade C), ranked #550 of 1320 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; no OSSF Scorecard result yet; 65% of recent commits are signed; last pushed 2026-06-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 14 spots (#536 → #550)
2026-09-03
Rank Moved
Rank dropped 26 spots (#510 → #536)
2026-09-02
Rank Moved
Rank dropped 15 spots (#495 → #510)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Refresh maintenance signals The repo was last pushed 66 days ago. Fresh activity helps separate stable projects from stale ones.
28.5
Activity sub-score · out of 100
#259

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →

Signals refreshed 2026-09-04 23:12 UTC · Repo last pushed 66 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
20
Forks
10
Last Push
2026-06-30
66 days ago
Commits (4 wk)
0
Downloads (7d)
102
pypi
HN mentions (30d)
Open Issues
2
Rank Change
▼14
was #536

Analysis

HVTrust Dimensions vs MCP Servers

56.8 / 100 · 100.0% confidence

Monarch MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
1.2 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
7.6 / 20
4.6 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.9 / 20
in line with avg 6.3

Activity Inputs

28.5 / 100
StarsRepository reach
7.9 / 30
FreshnessLast push recency
15.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.8 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
Not available
Signed Commits
65%
of last 100 commits verified

Is Monarch MCP Server safe?

Monarch MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Monarch MCP Server publish package provenance?
Yes. Monarch MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Monarch MCP Server have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Monarch MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Monarch MCP Server actively maintained?
Slowing down. Last push was 66 days ago — keep an eye on whether activity resumes.
What license does Monarch MCP Server use?
Monarch MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Monarch MCP Server's commits signed?
65% of the last 100 commits to Monarch MCP Server 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
Monarch MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
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

Maintain Monarch MCP Server?

For maintainers

HVTrust scores Monarch MCP Server 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
Rank 16Listed 1
2026-09-04
Rank Moved
Rank dropped 14 spots (#536 → #550)
2026-09-03
Rank Moved
Rank dropped 26 spots (#510 → #536)
2026-09-02
Rank Moved
Rank dropped 15 spots (#495 → #510)
2026-09-01
Rank Moved
Rank dropped 17 spots (#478 → #495)
2026-08-31
Rank Moved
Rank dropped 28 spots (#450 → #478)
2026-08-29
Rank Moved
Rank dropped 17 spots (#439 → #456)
2026-08-27
Rank Moved
Rank dropped 13 spots (#423 → #436)
2026-08-26
Rank Moved
Rank dropped 43 spots (#380 → #423)
2026-08-24
Rank Moved
Rank dropped 17 spots (#362 → #379)
2026-08-22
Rank Moved
Rank rose 19 spots (#380 → #361)
2026-08-19
Rank Moved
Rank dropped 12 spots (#366 → #378)
2026-08-17
Rank Moved
Rank rose 16 spots (#383 → #367)
2026-08-16
Rank Moved
Rank dropped 10 spots (#373 → #383)
2026-08-13
Rank Moved
Rank dropped 19 spots (#350 → #369)
2026-08-12
Rank Moved
Rank rose 16 spots (#366 → #350)
2026-08-10
Rank Moved
Rank dropped 20 spots (#344 → #364)
2026-08-08
Newly Listed
First tracked at rank #346

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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