# io.github.theluckystrike/retainer (remote · mcp.zovo.one)

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

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

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

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/deposits-retainer`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-30.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/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 1532 tokens (~117/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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

### How do I install the io.github.theluckystrike/retainer MCP server?

io.github.theluckystrike/retainer is a hosted endpoint at https://mcp.zovo.one/mcp/deposits-retainer, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-retainer 'https://mcp.zovo.one/mcp/deposits-retainer'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-retainer": {
      "url": "https://mcp.zovo.one/mcp/deposits-retainer"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-retainer": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/deposits-retainer"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-retainer]
url = "https://mcp.zovo.one/mcp/deposits-retainer"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-retainer": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/deposits-retainer",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-retainer --url 'https://mcp.zovo.one/mcp/deposits-retainer' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-retainer:
    url: "https://mcp.zovo.one/mcp/deposits-retainer"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-retainer": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/deposits-retainer"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-retainer -t streamable-http -u 'https://mcp.zovo.one/mcp/deposits-retainer'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-retainer": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/deposits-retainer"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-30 (score 83, +1)

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

### 2026-09-28 (score 82, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 82, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-26 (score 81)

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` (~153 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. Also a .txt download link valid one hour. 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` (~151 tokens)

Render the deposit statement as a PDF

Call this tool to render one client's A4 deposit statement and return a download link valid for one hour. 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): Name for the downloaded file, e.g. acme-deposits. Defaults to the client and currency; the statement comes back as a download link valid for one hour

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

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-retainer/mcp-deposits-retainer#diagnostics

## Score history

- 2026-09-30: 83
- 2026-09-29: 82
- 2026-09-28: 82
- 2026-09-27: 82
- 2026-09-26: 81

## 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 hosted endpoint (https://mcp.zovo.one/mcp/deposits-retainer).

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

io.github.theluckystrike/retainer scores 83 out of 100 on VerifyMCP. 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,465 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/retainer MCP server require authentication?

Yes. io.github.theluckystrike/retainer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/retainer MCP server still maintained?

io.github.theluckystrike/retainer is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/deposits-retainer
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/deposits-retainer
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/deposits
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-retainer/mcp-deposits-retainer.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-retainer/mcp-deposits-retainer.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-retainer/mcp-deposits-retainer