Deposit

io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.5Updated Oct 24, 2026

Take a client deposit, hold it, set it against an invoice or give it back.

VerifiedSTDIODesktop onlyFinance Business & Commerce

Server details

Identifier: io.github.theluckystrike/deposit
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account theluckystrike for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.theluckystrike%2Fdeposit.svg)](https://sourceweft.com/mcp/io.github.theluckystrike%2Fdeposit?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that records client security and retainer deposits, applies them to invoices, refunds them, and reports what is held.

What you can do: Record deposits received, with amount, currency, date and reference, and delete ones entered by mistake that never moved money (deposit_record, deposit_delete). List deposits filtered by client, status, kind or date, and show held balances per client and currency (deposit_list, deposit_balance). Apply part or all of a held deposit to an invoice as a payment, or refund it with date and method (deposit_apply, deposit_refund). Produce plain-text and A4 PDF deposit statements, and a report of held amounts, oldest deposits and unapplied money (deposit_statement_text, deposit_statement_pdf, deposits_report). Check or activate a licence tier (license_status, license_activate).
When to use it: Useful for freelancers and small businesses that hold client security or retainer money and need it tracked against invoices, so invoice lists and overdue reports stop chasing money already received. It is meant to run alongside the mcp-invoice server, whose clients and invoices it reads and writes.
Requirements: Runs as a local process on the desktop; the npm package is not yet published, so the .mcpb bundle or a clone-and-build is the working install path. Requires the mcp-invoice server running alongside it, sharing a business profile. An optional Pro licence key is supplied through the MCP_LICENSE_KEY environment variable and verified offline. No account, API key or network access otherwise.

Before you install

It writes to the invoice store shared with mcp-invoice, recording payments on invoices and changing paid amount, paid date and status; the README notes the invoice server's own payment tool overwrites prior payments, so check how the shared store is written. deposit_delete removes records, though only ones never applied or refunded. Pro features (PDF statements, reports) need a paid one-time licence; the free tier caps new deposits at five per calendar month. All data stays local.

Installation

In SourceWeft

Open Deposit in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-deposits

Security and retainer deposits, held per client, on the same engine as your invoices.

A deposit is the client's money sitting on your account. It has to be recorded when it arrives, set against an invoice when the work is billed, given back when it is not, and answered for at any point in between: how much of theirs are you holding, in which currency, since when. This server does those four things, against the invoices and the clients the mcp-invoice server already holds. When a deposit is applied to an invoice, the payment is recorded on that invoice, so invoice_list and overdue_report stop chasing money you already have. Everything stays on your machine.

Built on @theluckystrike/mcp-invoice/lib for the money, currency and store code, and on @theluckystrike/mcp-billing-docs/lib for the A4 page, so a deposit statement looks like the credit note and the invoice next to it and agrees with them to the minor unit.

In the official MCP Registry (io.github.theluckystrike/deposits).

[deposits demo]

npm publish for @theluckystrike/mcp-deposits is pending, so npx -y @theluckystrike/mcp-deposits returns 404 today. Until then, the .mcpb one-click bundle or a clone+build is the working path.

Install

Claude Desktop (claude_desktop_config.json):

json

{  "mcpServers": {    "deposits": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-deposits"]    }  }}

{  "mcpServers": {    "deposits": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-deposits"]    }  }}

Claude Code:

Cursor (.cursor/mcp.json):

json

{  "mcpServers": {    "deposits": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-deposits"]    }  }}

{  "mcpServers": {    "deposits": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-deposits"]    }  }}

Run mcp-invoice alongside it: this server reads that server's invoices and clients, writes the payment an applied deposit makes onto the invoice, and both take their name, address, VAT id and default currency from one shared business profile.

Tools

tool	what it does
`deposit_record`	Record a security or retainer deposit received: amount in minor units, currency, date, reference
`deposit_list`	Every deposit with received, applied, refunded and held. Filter by client, status, kind or date
`deposit_apply`	Apply part or all of a held deposit to an invoice, as a payment on that invoice
`deposit_refund`	Give part or all of a held deposit back, with the date and the method
`deposit_delete`	Remove a deposit recorded by mistake, if none of it was ever applied or refunded
`deposit_balance`	What is held, per client and per currency: received, applied, refunded, held
`deposit_statement_text`	The plain-text statement to paste into an email
`deposit_statement_pdf`	The A4 PDF, titled DEPOSIT STATEMENT (Pro)
`deposits_report`	Held per currency, the oldest held deposits, and what has sat unapplied for N days (Pro)
`license_status`, `license_activate`	Free or Pro, and how to upgrade

One resource, deposits://held, and one prompt, settle_deposits.

Free vs Pro

	Free	Pro
Deposits recorded per calendar month	5	Unlimited
Applying to invoices, refunds, balances, lists	Yes, unlimited	Yes
`deposit_delete` for a deposit that never moved money	Yes, unlimited	Yes
`deposit_statement_text`	Yes, unlimited	Yes
`deposit_statement_pdf`	No	Yes, plus your logo and no footer credit
`deposits_report`	No	Yes

The free cap is on recording new deposits only. Money already held can always be applied, refunded and accounted for, on any tier: a limit that trapped a client's deposit would be a limit on their money, not on yours.

The cap counts the deposits stored with a received date in that month, so deposit_delete gives the slot straight back: a deposit typed in twice or with the wrong amount costs nothing but the id. deposit_record also refuses a deposit that matches one already stored on client, amount, currency, kind, received date and reference, names that id and stores nothing, so the same money is never held twice and no free slot is spent on a retry.

Get Pro: https://mcp.zovo.one/buy/deposits ($19 one-time for this server, $39 for the bundle).

A measured thing

The invoice server's own payment tool SETS the amount paid, so routing a deposit through it erases the payment that came before. Measured against servers/invoice/dist/index.js on a EUR 1,000.00 invoice: invoice_mark_paid {amount: 200} for a bank transfer, then invoice_mark_paid {amount: 300} for the deposit, leaves paid_minor at 30000 and the reply reads "balance due EUR 700.00". The EUR 200.00 that actually arrived is gone from the record, and the client gets chased for it.

deposit_apply writes the same three fields on the same record, paid_minor, paid_date, status, but ADDS: the same two payments leave paid_minor at 50000 and a balance due of EUR 500.00. Asserted in test/unit.test.mjs, "a second application ADDS to paid_minor, it does not replace it".

The general form: a store shared between two servers is safe to write only if you have read how the owning server writes it. The field names matching is not the contract; the arithmetic on them is.

Privacy

All data stays local: ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/deposits/. No account, no API key, no network call, ever. Licence keys are verified offline.

Built by theluckystrike. Support: [email protected]

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-deposits

Source: servers/deposits/README.md at commit 1bd9d69

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.22.5LatestOct 14, 2026
v0.21.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts