# io.github.theluckystrike/retainer (mcpb · deposits.mcpb)

Client retainers held on account: record one, draw it down against invoices, refund it.

- Trust score: 54/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `deposits.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-retainer/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-deposits-m.md), [page](https://verifymcp.io/servers/theluckystrike-retainer/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-deposits-m)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/deposits.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 22/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 63 of 157 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1353 tokens (~112/item across 12 items; 11 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/deposits.mcpb`

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 52, +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.

### 2026-09-14 (score 51, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-07 (score 48)

First indexed and scored.

## MCP tools (11)

### `deposit_record` (~273 tokens)

Record a deposit received

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.

Input parameters:

- `amount_minor` (integer, required): What was received, in MINOR units: 50000 = 500.00 EUR, 50000 = JPY 50000. Never a decimal
- `client` (string, required): 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, required): 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

### `deposit_list` (~125 tokens)

List deposits

List deposits with what was received, applied, refunded and still held on each. Filter by client, by status held, applied or refunded, by kind and by received date range.

Input parameters:

- `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

### `deposit_apply` (~169 tokens)

Apply a deposit to an invoice

Apply part or all of a held deposit to one invoice: records that amount as a payment on the invoice through the invoice engine. Refuses more than is held or more than the invoice still owes.

Input parameters:

- `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, required): Deposit id such as DEP-2026-0001, or an exact client name
- `invoice` (string, required): The invoice number to apply it to, e.g. INV-2026-0001
- `note` (string): Free text kept on the application row

### `deposit_refund` (~164 tokens)

Refund a deposit

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.

Input parameters:

- `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, required): 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

### `deposit_delete` (~74 tokens)

Delete a deposit recorded by mistake

Delete a deposit recorded by mistake and free that month's free-tier slot again. Only a deposit with nothing applied to an invoice and nothing refunded can go; one whose money moved is refused, naming what holds it.

Input parameters:

- `id` (string, required): Deposit id such as DEP-2026-0001, or an exact client name

### `deposit_balance` (~91 tokens)

What is held for a client

Answer "how much of theirs am I holding?" for one client or for everyone: received, applied to invoices, refunded and still held, one row per currency, never added across currencies.

Input parameters:

- `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

### `deposit_statement_text` (~135 tokens)

Plain-text deposit statement

Turn one client's deposits into a plain-text statement with every movement in date order and the closing balance, ready to paste into an email. Free on every tier.

Input parameters:

- `as_of` (string): YYYY-MM-DD printed as the statement date. Defaults to today
- `client` (string, required): 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

### `deposit_statement_pdf` (~140 tokens)

Render the deposit statement as a PDF

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.

Input parameters:

- `as_of` (string): YYYY-MM-DD printed as the statement date. Defaults to today
- `client` (string, required): 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

### `deposits_report` (~100 tokens)

What is held, and for how long

What is held per currency, the oldest held deposits, and every deposit received more than N days ago with none of it applied to an invoice. Pro.

Input parameters:

- `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

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-retainer/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-deposits-m#diagnostics

## Score history

- 2026-09-20: 54
- 2026-09-19: 53
- 2026-09-18: 53
- 2026-09-17: 52
- 2026-09-16: 52
- 2026-09-15: 52
- 2026-09-14: 51
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 48
- 2026-09-10: 48
- 2026-09-09: 48
- 2026-09-08: 48
- 2026-09-07: 48

## Common questions

### 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.21.0/deposits.mcpb).

### Is the io.github.theluckystrike/retainer MCP server safe to use?

io.github.theluckystrike/retainer scores 54 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,336 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.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/deposits
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-retainer/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-deposits-m.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-retainer/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-deposits-m.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-retainer/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-deposits-m