Bank Statement Sheet — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

PDF bank statement extraction with reconciliation

What we know

Extract statement transactions and verify running-balance reconciliation. Convert PDF bank statements into transactions that arrive with a pass/fail reconciliation verdict.

Maintenance / activity evidence

143 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Sensitive financial statements are sent to remote processing; package describes short-term retention. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Sensitive access: Account or infrastructure data accessible with supplied credentials

Sensitive financial statements are sent to remote processing; package describes short-term retention.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 143 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package bank-statement-sheet-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have bank-statement-sheet-mcp permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Sensitive financial statements are sent to remote processing; package describes short-term retention.

Sensitive financial statements are sent to remote processing; package describes short-term retention.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Sensitive access: Account or infrastructure data accessible with supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
runtime_installer_exact
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

143 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/bank-statement-sheet-mcp

Exact implementation source: https://www.npmjs.com/package/bank-statement-sheet-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:bank-statement-sheet-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
bank-statement-sheet-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Key optional, anonymous tier 5 conversions/month; financial statements can include sensitive data
BSS_API_KEY is optional: anonymous free tier limited to five conversions/month, document privacy is important.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Key optional, anonymous tier 5 conversions/month; financial statements can include sensitive data | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx -y bank-statement-sheet-mcp
Configure / authenticate
MCP100 setup guide
Publisher-documented connection/installation path shown under install.commands. Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim. Key optional, anonymous tier 5 conversions/month; financial statements can include sensitive data Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `bank-statement-sheet-mcp`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove bank-statement-sheet-mcp

Official Documentation & Sources

What it does

Extract statement transactions and verify running-balance reconciliation. Convert PDF bank statements into transactions that arrive with a pass/fail reconciliation verdict.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: PDF bank statement extraction with reconciliation

Representative uses

Convert bank PDFs
Inspect reconciliation failures

Limitations

Sensitive financial statements are sent to remote processing; package describes short-term retention.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: Sensitive financial statements are sent to remote processing; package describes short-term retention.
Data handling: Sensitive financial statements are sent to remote processing; package describes short-term retention.
Cost: Not verified; check vendor terms
Risk and cautions: Sensitive financial statements are sent to remote processing; package describes short-term retention.

Access scope and cautions

Write actions: Not verified
Sensitive access: Account or infrastructure data accessible with supplied credentials
Risk level: high
Security notes: Sensitive financial statements are sent to remote processing; package describes short-term retention. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Convert bank PDFs; Inspect reconciliation failures.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Sensitive financial statements are sent to remote processing; package describes short-term retention.

What data-handling boundary should I consider?

Sensitive financial statements are sent to remote processing; package describes short-term retention. Recorded sensitive-access context: Account or infrastructure data accessible with supplied credentials.

What limitations and risks should I check before use?

Sensitive financial statements are sent to remote processing; package describes short-term retention. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.