io.github.theluckystrike/aging
MCPB · STATEMENT-OF-ACCOUNT.MCPB · SCANNED SEP 20
Age your receivables into 0-30, 31-60, 61-90 and over 90 day buckets by due date.
Available components
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 Security22
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 63 of 157 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 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 1015 tokens (~112/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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · statement-of-account.mcpb
Download bundleEvery 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 7 Sept 26 49
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 20 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.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 |
Background: How many MCP packages publish verified provenance →
Dependencies 157 packages
| Packages resolved | 157 |
|---|---|
| Deprecated | 2 |
| Stale | 63 |
| 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 ~196
Write a payment chaser for one client at level 1 friendly, 2 firm or 3 final demand, listing every overdue invoice with its age and total, plus your bank details when the profile has them. 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 ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| 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 ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
statement_aging Age the open invoices ~142
Break what is owed into 0-30, 31-60, 61-90 and over 90 days past the invoice due date as at a chosen date, for one client or for every client, per currency. Free and unlimited.
| 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 ~136
Build one client's statement of account for a period: opening balance, invoices issued, payments received, credit notes, deposits applied and closing balance, in minor units and formatted.
| 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 ~189
Call this tool to write one client's A4 statement of account and return the file path. Titled STATEMENT OF ACCOUNT, every movement in date order, closing with the balance outstanding. 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 ~184
Turn one client's statement into a plain-text ledger with every movement in date order, the opening and closing balances and a sign-off, ready to paste into an email.
| 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 ~78
Show what is outstanding across every client, totalled per currency and aged, with the oldest overdue invoice and the clients carrying it. Pro.
| 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.
What is the io.github.theluckystrike/aging MCP server?
io.github.theluckystrike/aging is an MCP server listed in the public MCP registry as io.github.theluckystrike/aging. Age your receivables into 0-30, 31-60, 61-90 and over 90 day buckets by due date. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/statement-of-account.mcpb).
Is the io.github.theluckystrike/aging MCP server safe to use?
io.github.theluckystrike/aging scores 55 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 io.github.theluckystrike/aging MCP server expose?
io.github.theluckystrike/aging exposes 8 tools: statement_build, statement_aging, statement_text, statement_pdf, dunning_text, and 3 more. Their descriptions and schemas cost roughly 990 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/aging MCP server under?
io.github.theluckystrike/aging declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.