Finagent — Financial Reports
PYPI · OPEN-FINANCE-MCP
Read-only profit, cash-flow and balance reports. Demo included; client sources need local setup.
Available components
Last scanned (13 hours ago)
Scores higher than 53% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to finuchetai/finagent-mcp). View diagnostics → Pass
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 518 tokens (~86/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (13)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (3)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/open-finance-mcp@0.7.0rc2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | finuchetai/finagent-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/finuchetai/finagent-mcp/.github/workflows/publish-pypi.yml@refs/heads/main |
| Rekor log index | 3881230847 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:75004aae09080abae200bbfc0e9dc3e081a153a2a0a3dc9c759dafcc613021f2 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_balances ~38
Opening/movement/closing balances. as_of is the data-state date; received_at is only retrieval time.
| Name | Type | Req | Description |
|---|---|---|---|
| months | array | yes | – |
No output schema declared.
No examples provided.
get_cashflow ~38
Cash movements, not profit. Unknown as_of cannot be replaced by received_at or used to claim fresh data.
| Name | Type | Req | Description |
|---|---|---|---|
| months | array | yes | – |
No output schema declared.
No examples provided.
get_month_notes ~27
Methodological notes for a single closed YYYY-MM period.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | – |
No output schema declared.
No examples provided.
get_passport ~22
Read the methodology, data origin, completeness and demo limitations first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pnl ~43
Accrual P&L for closed periods. as_of=null means unknown data date; received_at is retrieval time, not freshness.
| Name | Type | Req | Description |
|---|---|---|---|
| months | array | yes | – |
No output schema declared.
No examples provided.
list_months ~25
List periods, closed/open state and available reports. Open periods cannot be queried.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Finagent — Financial Reports MCP server?
Finagent — Financial Reports runs locally as a PyPI package, launched with uvx open-finance-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · open-finance-mcp
claude mcp add finuchetai-finagent-mcp -- uvx open-finance-mcp
What is the Finagent — Financial Reports MCP server?
Finagent — Financial Reports is an MCP server listed in the public MCP registry as io.github.finuchetai/finagent-mcp. Read-only profit, cash-flow and balance reports. Demo included; client sources need local setup. This page covers its PyPI package (open-finance-mcp).
Is the Finagent — Financial Reports MCP server safe to use?
Finagent — Financial Reports scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Finagent — Financial Reports MCP server expose?
Finagent — Financial Reports exposes 6 tools: get_passport, list_months, get_pnl, get_cashflow, get_balances, get_month_notes. Their descriptions and schemas cost roughly 193 tokens of context every time the server is loaded.
Is the Finagent — Financial Reports MCP server still maintained?
Finagent — Financial Reports is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Finagent — Financial Reports MCP server?
VerifyMCP ran 13 checks on Finagent — Financial Reports, covering Known CVEs, Install scripts, Dependency health, Source repository and 9 more. 3 items could not be completed, a gap on our side rather than a finding about Finagent — Financial Reports: Malware scan, License and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.