io.github.sebastienrousseau/bankstatementparser-mcp
PYPI · BANKSTATEMENTPARSER-MCP
MCP server for parsing bank statements (BAI2, MT940/MT942, CAMT.053, OFX) via stdio.
Available components
Last scanned (19 hours ago)
Scores higher than 98% 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs poetry.core.masonry.api at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sebastienrousseau/bankstatementparser-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0 OR MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1298 tokens (~216/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
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 4 Nov 2026 · Analysed pypi/bankstatementparser-mcp@0.0.19
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 | sebastienrousseau/bankstatementparser-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sebastienrousseau/bankstatementparser-mcp/.github/workflows/release.yml@refs/tags/v0.0.19 |
| Rekor log index | 2674411820 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3caf0b810d2ed21faed7576e6481f2bd1d2595938ec1fa3ce2bd09ac60ff0d08 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | poetry.core.masonry.api |
Background: Why install scripts are a supply-chain risk →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Stale | 1 |
| 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 →
detect_format Detect statement format ~216
Detect which bank statement format an inline payload is. Use this when you hold statement text but do not yet know its format, to resolve the ``format`` identifier from the content plus filename hint. Once the format is known, call ``parse_statement`` to read the transactions instead of calling this again. Args: content: The raw statement text. filename: Original filename; its extension is the primary hint. Returns: The detected format identifier. Raises: ValueError: If the format cannot be detected.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The raw statement text to inspect, inline (not a file path). Supported formats include ISO 20022 CAMT.053 and pain.001 XML, SWIFT MT940, CSV exports, and OFX/QFX. |
| filename | string | – | Original filename of the payload; its extension is the primary detection hint. Recognised extensions: .xml, .csv, .ofx, .qfx, .mt940, .sta. Defaults to 'statement.xml'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_supported_formats List supported statement formats ~79
List every bank statement format identifier this server can parse. Use this first to discover the valid ``format`` strings before calling ``detect_format`` or ``parse_statement``. For the file extensions and a human-readable description of each format, read the ``bankstatementparser://formats`` resource instead. Returns: The supported format identifiers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
parse_statement Parse statement transactions and summary ~383
Parse an inline statement payload into transaction rows and a summary. Use this to read the full transaction detail plus the statement balances from a payload. When you only need the balances/totals use ``summarize_statement`` instead, and to merely confirm a payload parses without returning any rows use ``validate_statement``. Args: content: The raw statement text. filename: Original filename; its extension selects the format when ``format`` is omitted. format: Explicit format override. limit: Optional cap on returned transaction rows. Returns: A dict with the resolved ``format``, ``columns``, full ``transaction_count``, the (possibly truncated) ``transactions`` as row dicts, and the statement ``summary``. Raises: ValueError: If the format is unsupported or cannot be detected.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The raw statement text to parse, inline (not a file path). Accepts ISO 20022 CAMT.053 and pain.001 XML, SWIFT MT940, CSV exports, and OFX/QFX payloads. |
| filename | string | – | Original filename of the payload; its extension (.xml, .csv, .ofx, .qfx, .mt940, .sta) selects the format when 'format' is omitted. Defaults to 'statement.xml'. |
| format | – | – | Explicit format identifier that overrides detection from the filename. Must be exactly one of: 'camt', 'pain001', 'csv', 'ofx', 'qfx', 'mt940' (see list_supported_formats). When omitted, the format i… |
| limit | – | – | Optional maximum number of transaction rows to return. The full 'transaction_count' is always reported even when the returned rows are truncated. When omitted, all rows are returned. |
Structured output declared, but exposes no named fields.
No examples provided.
summarize_statement Summarize statement balances ~285
Summarize an inline statement's balances and totals only. Use this when you need just the opening/closing balances, currency, and other summary fields without the per-transaction rows. For the full transaction detail alongside the summary, use ``parse_statement`` instead. Args: content: The raw statement text. filename: Original filename; its extension selects the format. format: Explicit format override. Returns: The summary record with Decimal values stringified. Raises: ValueError: If the format is unsupported or cannot be detected.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The raw statement text to summarize, inline (not a file path). Accepts ISO 20022 CAMT.053 and pain.001 XML, SWIFT MT940, CSV exports, and OFX/QFX payloads. |
| filename | string | – | Original filename of the payload; its extension (.xml, .csv, .ofx, .qfx, .mt940, .sta) selects the format when 'format' is omitted. Defaults to 'statement.xml'. |
| format | – | – | Explicit format identifier that overrides detection from the filename. Must be exactly one of: 'camt', 'pain001', 'csv', 'ofx', 'qfx', 'mt940' (see list_supported_formats). When omitted, the format i… |
Structured output declared, but exposes no named fields.
No examples provided.
validate_statement Validate statement (dry run) ~308
Dry-run parse an inline statement to check it parses cleanly. Use this to confirm a payload is well-formed and parseable before committing to a full read; it returns a structured pass/fail with the transaction count but never the rows themselves, and never raises on a parse error. To actually read the transactions use ``parse_statement``. Args: content: The raw statement text. filename: Original filename; its extension selects the format. format: Explicit format override. Returns: A dict with ``is_valid``, the resolved ``format``, the ``transaction_count`` on success, and an ``error`` on failure.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The raw statement text to validate, inline (not a file path). Accepts ISO 20022 CAMT.053 and pain.001 XML, SWIFT MT940, CSV exports, and OFX/QFX payloads. |
| filename | string | – | Original filename of the payload; its extension (.xml, .csv, .ofx, .qfx, .mt940, .sta) selects the format when 'format' is omitted. Defaults to 'statement.xml'. |
| format | – | – | Explicit format identifier that overrides detection from the filename. Must be exactly one of: 'camt', 'pain001', 'csv', 'ofx', 'qfx', 'mt940' (see list_supported_formats). When omitted, the format i… |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.sebastienrousseau/bankstatementparser-mcp server?
io.github.sebastienrousseau/bankstatementparser-mcp runs locally as a PyPI package, launched with uvx bankstatementparser-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 · bankstatementparser-mcp
claude mcp add sebastienrousseau-bankstatementparser-mcp -- uvx bankstatementparser-mcp
What is the io.github.sebastienrousseau/bankstatementparser-mcp server?
io.github.sebastienrousseau/bankstatementparser-mcp is listed in the public MCP registry as io.github.sebastienrousseau/bankstatementparser-mcp. MCP server for parsing bank statements (BAI2, MT940/MT942, CAMT.053, OFX) via stdio. This page covers its PyPI package (bankstatementparser-mcp).
Is the io.github.sebastienrousseau/bankstatementparser-mcp server safe to use?
io.github.sebastienrousseau/bankstatementparser-mcp scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.github.sebastienrousseau/bankstatementparser-mcp server expose?
io.github.sebastienrousseau/bankstatementparser-mcp exposes 5 tools: list_supported_formats, detect_format, parse_statement, validate_statement, summarize_statement. Their descriptions and schemas cost roughly 1,271 tokens of context every time the server is loaded.
Is the io.github.sebastienrousseau/bankstatementparser-mcp server still maintained?
io.github.sebastienrousseau/bankstatementparser-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.sebastienrousseau/bankstatementparser-mcp server under?
io.github.sebastienrousseau/bankstatementparser-mcp declares the Apache-2.0 OR MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.