io.github.theluckystrike/retainer
MCPB · DEPOSITS.MCPB · 2 COMPONENTS · SCANNED SEP 30
Client retainers held on account: record one, draw it down against invoices, refund it.
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
- 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
- 63 of 153 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency39
- 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
- Maintenance history not yet determined.Unverified
- 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 1455 tokens (~121/item across 12 items; 11 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deposit_refund" implies "refund" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
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.
How do I install the io.github.theluckystrike/retainer MCP server?
io.github.theluckystrike/retainer 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. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · deposits.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
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 Sept 26 −1
- Maintenance: pass → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 47
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 30 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/deposits.mcpb@0.22.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 | 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 →
deposit_apply Apply a deposit to an invoice ~176
Apply part of a held deposit to one invoice: it records that amount as a PAYMENT through the invoice server. amount_minor defaults to the lesser of held and owed. More than either, or a pre-arrival date, is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | – | How much of the deposit to apply, in minor units. Defaults to the smaller of what is held and what the invoice still owes |
| date | string | – | YYYY-MM-DD, the day the deposit was set against the invoice. Defaults to today |
| id | string | yes | Deposit id such as DEP-2026-0001, or an exact client name |
| invoice | string | yes | The invoice number to apply it to, e.g. INV-2026-0001 |
| note | string | – | Free text kept on the application row |
No output schema declared.
No examples provided.
deposit_balance What is held for a client ~99
Answer "how much of theirs am I holding?" for one client or everyone: received, applied to invoices, refunded and still held, one row per currency, never added across them. Reads only; deposit_list shows each deposit.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD, count only deposits received on or before this day |
| client | string | – | Client id, exact name or a name containing this text. Leave out for every client |
No output schema declared.
No examples provided.
deposit_delete Delete a deposit recorded by mistake ~72
Delete a deposit that never moved money, freeing that month's free-tier slot. One with anything applied or refunded is refused, naming it, since a payment or refund would be left with nothing behind it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Deposit id such as DEP-2026-0001, or an exact client name |
No output schema declared.
No examples provided.
deposit_list List deposits ~135
List deposits newest first: DEP number, client, kind, date, reference and what was received, applied, refunded and still held, with the same four totalled per currency. Filter by client, status, kind, date.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Only deposits for this client id, exact name, or a name containing this text |
| from | string | – | YYYY-MM-DD, earliest received date |
| kind | string | – | Default "all" |
| status | string | – | Default "all". held means some of the money is still held |
| to | string | – | YYYY-MM-DD, latest received date |
No output schema declared.
No examples provided.
deposit_record Record a deposit received ~273
Record a security or retainer deposit received from a client, in minor units, with its currency, the date it arrived and the bank reference. Returns the DEP-YYYY-NNNN id.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | What was received, in MINOR units: 50000 = 500.00 EUR, 50000 = JPY 50000. Never a decimal |
| client | string | yes | Client name or client id. A name the invoice server already knows brings its address, email and VAT id onto the deposit |
| client_address | string | – | Postal address for the statement's client block, newlines allowed |
| client_email | string | – | Only if the user gave it; otherwise the stored client's email is used |
| client_vat_id | string | – | Client VAT / tax registration id |
| currency | string | – | Defaults to your business default currency |
| kind | string | yes | security: held against damage or non-payment. retainer: held against work not yet invoiced |
| notes | string | – | Free text kept on the record and printed on the statement |
| received_date | string | – | YYYY-MM-DD, the day the money arrived. Defaults to today |
| reference | string | – | Bank reference, transfer note or cheque number the money arrived with |
No output schema declared.
No examples provided.
deposit_refund Refund a deposit ~164
Give part or all of a held deposit back to the client, with the date and how it was sent. Refuses more than is still held. The invoice server is not touched: a refund is not a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | – | How much to give back, in minor units. Defaults to everything still held |
| date | string | – | YYYY-MM-DD, the day the money went back. Defaults to today |
| id | string | yes | Deposit id such as DEP-2026-0001, or an exact client name |
| method | string | – | How it was sent, e.g. "bank transfer to the account it came from". Printed on the statement |
| note | string | – | Free text kept on the refund row |
No output schema declared.
No examples provided.
deposit_statement_pdf Render the deposit statement as a PDF ~140
Call this tool to write one client's A4 deposit statement and return the file path. Titled DEPOSIT STATEMENT, every movement in date order, closing with what is still held. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD printed as the statement date. Defaults to today |
| client | string | yes | Client id, exact name or a name containing this text |
| currency | string | – | Only needed when the client has deposits in more than one currency |
| out_path | string | – | Where to write the PDF; defaults to the deposits data directory under pdf/. Use a .pdf path: the bytes written are always PDF |
No output schema declared.
No examples provided.
deposit_statement_text Plain-text deposit statement ~143
Turn one client's deposits into a plain-text statement to paste into an email: every movement in date order and the closing balance held. Pass currency when they have more than one. Free on every tier.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD printed as the statement date. Defaults to today |
| client | string | yes | Client id, exact name or a name containing this text |
| currency | string | – | Only needed when the client has deposits in more than one currency |
| greeting | string | – | Opening line, default "Hello" plus the client name |
| sign_off | string | – | Closing line, default your business name from the shared profile |
No output schema declared.
No examples provided.
deposits_report What is held, and for how long ~111
The deposit book at a date: held per currency, received, applied and refunded, the oldest holdings with days held, and every deposit older than N days with nothing applied. Pro; deposit_balance is free.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD to count from. Defaults to today |
| limit | integer | – | How many oldest held deposits to list. Default 10 |
| older_than_days | integer | – | Flag deposits received this many days ago or more with nothing applied. Default 90 |
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.
What is the io.github.theluckystrike/retainer MCP server?
io.github.theluckystrike/retainer is an MCP server listed in the public MCP registry as io.github.theluckystrike/retainer. Client retainers held on account: record one, draw it down against invoices, refund it. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/deposits.mcpb).
Is the io.github.theluckystrike/retainer MCP server safe to use?
io.github.theluckystrike/retainer scores 46 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/retainer MCP server expose?
io.github.theluckystrike/retainer exposes 11 tools: deposit_record, deposit_list, deposit_apply, deposit_refund, deposit_delete, and 6 more. Their descriptions and schemas cost roughly 1,438 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/retainer MCP server under?
io.github.theluckystrike/retainer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.