io.github.theluckystrike/deposits
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Security and retainer deposits per client: hold, apply to an invoice, refund, statement.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 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 1532 tokens (~117/item across 13 items; 11 tools + 2 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
How do I install the io.github.theluckystrike/deposits MCP server?
io.github.theluckystrike/deposits is a hosted endpoint at https://mcp.zovo.one/mcp/deposits, 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-deposits 'https://mcp.zovo.one/mcp/deposits'
{
"mcpServers": {
"theluckystrike-deposits": {
"url": "https://mcp.zovo.one/mcp/deposits"
}
}
} {
"servers": {
"theluckystrike-deposits": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/deposits"
}
}
} [mcp_servers.theluckystrike-deposits] url = "https://mcp.zovo.one/mcp/deposits"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-deposits": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/deposits",
"enabled": true
}
}
} openclaw mcp add theluckystrike-deposits --url 'https://mcp.zovo.one/mcp/deposits' --transport streamable-http
mcp_servers:
theluckystrike-deposits:
url: "https://mcp.zovo.one/mcp/deposits" {
"McpServers": {
"theluckystrike-deposits": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/deposits"
}
}
} assistant mcp add theluckystrike-deposits -t streamable-http -u 'https://mcp.zovo.one/mcp/deposits'
{
"mcpServers": {
"theluckystrike-deposits": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/deposits"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +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.
- 17 Sept 26 +1
- Server version: 0.21.0 → 0.22.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “deposit_balance” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 9 Sept 26 +1
- Tool “deposit_apply” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “deposits_report” rewrote its description, which is the text the model reads security
- Tool “deposit_statement_text” rewrote its description, which is the text the model reads security
- Tool “deposit_list” rewrote its description, which is the text the model reads security
- Tool “deposit_delete” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 8 Sept 26 +41
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Tool coverage: 100 functional
- 5 Sept 26 36
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/deposits
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/deposits | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/deposits | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/deposits |
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 ~151
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.
| 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 | – | 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 |
No output schema declared.
No examples provided.
deposit_statement_text Plain-text deposit statement ~153
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.
| 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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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 hosted endpoint (https://mcp.zovo.one/mcp/deposits).
Is the io.github.theluckystrike/deposits MCP server safe to use?
io.github.theluckystrike/deposits 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/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,465 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/deposits MCP server require authentication?
Yes. io.github.theluckystrike/deposits 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/deposits MCP server still maintained?
io.github.theluckystrike/deposits is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.