McpStamp Statement of Account
MCPB · STATEMENT-OF-ACCOUNT.MCPB · 2 COMPONENTS
Client statements of account, ageing of open invoices and payment chasers as text or PDF.
Available components
Last scanned (3 hours ago)
Scores higher than 98% of MCPB 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 Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 153 of 153 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 57 of 153 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 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 1127 tokens (~125/item across 9 items; 8 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 2 Nov 26 +58
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.81 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- Package version: 0.22.0 → 0.21.0 functional
- 31 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 30 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 27 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 26 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 25 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 24 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 22 Oct 26 0
- Package version: 0.22.0 → 0.22.5 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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/statement-of-account.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 153 packages
| Packages resolved | 153 |
|---|---|
| Deprecated | 2 |
| Stale | 57 |
| 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 →
dunning_text Write a dunning letter ~201
Write a payment chaser at level 1 friendly, 2 firm or 3 final demand: every OVERDUE invoice with its age, the total and your bank details. Refused if nothing is overdue. No interest is stated. Level 3 is Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Age the invoices as at this date, YYYY-MM-DD. Defaults to today |
| client | string | yes | Client id from the invoice server, an exact client name, or a name containing this text |
| currency | string | – | Only needed when the client has documents in more than one currency. Currencies are never added together |
| greeting | string | – | Opening line, default "Hello" and the client name |
| level | integer | yes | 1 friendly reminder, 2 firm reminder, 3 final demand. Level 3 is Pro |
| sign_off | string | – | Closing line, default your business name from the shared profile |
No output schema declared.
No examples provided.
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
statement_aging Age the open invoices ~144
Age open invoices into 0-30, 31-60, 61-90 and over 90 days past DUE date at a date, per client and currency, with the invoices themselves. Free. statements_report rolls up the whole book instead.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Age the invoices as at this date, YYYY-MM-DD. Defaults to today |
| client | string | – | One client id or name. Omit to age every client in the books |
| currency | string | – | Only this currency. Omit for every currency, each aged separately |
| limit | integer | – | Maximum invoice rows returned, default and ceiling 2000 |
No output schema declared.
No examples provided.
statement_build Build a statement of account ~144
Build one client's statement for a period: opening, invoices, payments with deposits applied broken out, credit notes and closing, formatted and in minor units. Free: 5 a month; a rebuild is free.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Client id from the invoice server, an exact client name, or a name containing this text |
| currency | string | – | Only needed when the client has documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD. Everything dated before it becomes the opening balance |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
statement_pdf Render the statement of account as a PDF ~196
Call this tool to write one client's A4 statement of account and return the path. Titled STATEMENT OF ACCOUNT, movements in date order, BALANCE OUTSTANDING at the foot, and no VAT re-added. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date printed on the statement, YYYY-MM-DD. Defaults to today |
| client | string | yes | Client id from the invoice server, an exact client name, or a name containing this text |
| currency | string | – | Only needed when the client has documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD |
| out_path | string | – | Where to write the PDF; defaults to this server's data directory under pdf/. Use a .pdf path: the bytes written are always PDF |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
statement_text Plain-text statement of account ~198
Turn one client's statement into a plain-text letter for an email: movements in date order, opening and closing balances, deposit held, a sign-off. It counts toward the 5 a month; statement_pdf writes the A4 page.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date printed on the statement, YYYY-MM-DD. Defaults to today |
| client | string | yes | Client id from the invoice server, an exact client name, or a name containing this text |
| currency | string | – | Only needed when the client has documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD |
| greeting | string | – | Opening line, default "Hello" and the client name |
| sign_off | string | – | Closing line, default your business name from the shared profile |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
statements_report What every client owes ~94
Receivables across every client at a date: totals and aging per currency, clients ranked by how much is OVERDUE, and the oldest overdue invoice. Pro. statement_aging is the free per-client view.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Age the invoices as at this date, YYYY-MM-DD. Defaults to today |
| limit | integer | – | How many clients to list, worst first. Default 20 |
No output schema declared.
No examples provided.
How do I install the McpStamp Statement of Account MCP server?
McpStamp Statement of Account ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, e44de5893904e42303b174e1abc47f9ae1d5cfc880097501bb3824a12a5c0267; the commands to do that are on this page. If it does not match, do not open it.
mcpb · statement-of-account.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
e44de5893904e42303b174e1abc47f9ae1d5cfc880097501bb3824a12a5c0267
macOS / Linux
echo "e44de5893904e42303b174e1abc47f9ae1d5cfc880097501bb3824a12a5c0267 statement-of-account.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\statement-of-account.mcpb).Hash -eq "e44de5893904e42303b174e1abc47f9ae1d5cfc880097501bb3824a12a5c0267"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Statement of Account MCP server?
McpStamp Statement of Account is an MCP server listed in the public MCP registry as io.github.theluckystrike/statement-of-account. Client statements of account, ageing of open invoices and payment chasers as text or PDF. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/statement-of-account.mcpb).
Is the McpStamp Statement of Account MCP server safe to use?
McpStamp Statement of Account scores 63 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 McpStamp Statement of Account MCP server expose?
McpStamp Statement of Account exposes 8 tools: statement_build, statement_aging, statement_text, statement_pdf, dunning_text, and 3 more. Their descriptions and schemas cost roughly 1,102 tokens of context every time the server is loaded.
What licence is the McpStamp Statement of Account MCP server under?
McpStamp Statement of Account declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.