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

Security and retainer deposits per client: hold, apply to an invoice, refund, statement.

- Trust score: 47/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 83/100, [markdown](https://verifymcp.io/servers/theluckystrike-deposits/mcp-deposits.md), [page](https://verifymcp.io/servers/theluckystrike-deposits/mcp-deposits)
- mcpb · `deposits.mcpb`: 47/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-deposits/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-deposits-m.md), [page](https://verifymcp.io/servers/theluckystrike-deposits/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-deposits-m)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/deposits.mcpb`
- Version: `0.22.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-21.

- **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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/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 1455 tokens (~121/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.

**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.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.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-17 (score 47)

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` (~135 tokens)

List deposits

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.

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` (~176 tokens)

Apply a deposit to an invoice

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.

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` (~72 tokens)

Delete a deposit recorded by mistake

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.

Input parameters:

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

### `deposit_balance` (~99 tokens)

What is held for a client

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.

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` (~143 tokens)

Plain-text deposit statement

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.

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` (~111 tokens)

What is held, and for how long

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.

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` (~54 tokens)

License status

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.

### `license_activate` (~71 tokens)

Activate license

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.

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-deposits/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-deposits-m#diagnostics

## Score history

- 2026-09-21: 47
- 2026-09-20: 47
- 2026-09-19: 47
- 2026-09-18: 47
- 2026-09-17: 47

## Common questions

### What is the io.github.theluckystrike/deposits MCP server?

io.github.theluckystrike/deposits is an MCP server listed in the public MCP registry as io.github.theluckystrike/deposits. Security and retainer deposits per client: hold, apply to an invoice, refund, statement. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/deposits.mcpb).

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

io.github.theluckystrike/deposits scores 47 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/deposits MCP server expose?

io.github.theluckystrike/deposits 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/deposits MCP server under?

io.github.theluckystrike/deposits 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-deposits/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-deposits-m.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-deposits/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-deposits-m.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-deposits/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-deposits-m