io.github.theluckystrike/cash-book
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
One double-entry ledger derived from your invoices, bank, expenses, deposits and assets.
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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1148 tokens (~104/item across 11 items; 9 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "period_delete" implies "delete" 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 10 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/cash-book MCP server?
io.github.theluckystrike/cash-book is a hosted endpoint at https://mcp.zovo.one/mcp/cash-book, 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-cash-book 'https://mcp.zovo.one/mcp/cash-book'
{
"mcpServers": {
"theluckystrike-cash-book": {
"url": "https://mcp.zovo.one/mcp/cash-book"
}
}
} {
"servers": {
"theluckystrike-cash-book": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/cash-book"
}
}
} [mcp_servers.theluckystrike-cash-book] url = "https://mcp.zovo.one/mcp/cash-book"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-cash-book": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/cash-book",
"enabled": true
}
}
} openclaw mcp add theluckystrike-cash-book --url 'https://mcp.zovo.one/mcp/cash-book' --transport streamable-http
mcp_servers:
theluckystrike-cash-book:
url: "https://mcp.zovo.one/mcp/cash-book" {
"McpServers": {
"theluckystrike-cash-book": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/cash-book"
}
}
} assistant mcp add theluckystrike-cash-book -t streamable-http -u 'https://mcp.zovo.one/mcp/cash-book'
{
"mcpServers": {
"theluckystrike-cash-book": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/cash-book"
}
}
} 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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +56
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.30 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Server version: 0.21.0 → 0.22.0 functional
- 17 Sept 26 −55
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Stability: 0.23 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 14 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “month_close” rewrote its description, which is the text the model reads security
- Tool “ledger_lines” 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
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- Tool “ledger_report” 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 “license_status” rewrote its description, which is the text the model reads security
- Tool “month_close” rewrote its description, which is the text the model reads security
- Tool “ledger_build” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: 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
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: pass functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: fail functional
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/cash-book
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/cash-book | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/cash-book | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/cash-book |
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 →
ledger_build Build the ledger for a period ~112
Derive the double-entry ledger for one period in ONE currency from the invoice, credit note, deposit, expense, bank and asset stores, and register it. Nothing is written back. Free: 3 periods a month.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Needed when the period holds documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
ledger_export_csv Export the ledger as CSV ~143
Return the period's ledger lines as RFC 4180 CSV, one row per leg, as a download link valid for one hour. Pro, but ledger_lines returns these same fields free and unlimited; this only lays them out as CSV columns.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Only this account or category prefix |
| currency | string | – | Needed when the period holds documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD |
| source | string | – | Only lines derived from this server |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
ledger_lines List ledger lines ~252
List the ledger lines for a period, filtered by account, source server, source_id or date; each carries its debit, credit and bank_ref, with the totals of the rows returned. Filtered totals do not balance. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Only this account, e.g. cash, receivables, vat_output, or a category prefix such as "expenses" |
| currency | string | – | Needed when the period holds documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD |
| limit | integer | – | Maximum rows, default and ceiling 5000 |
| since | string | – | Only lines dated on or after this date, YYYY-MM-DD |
| source | string | – | Only lines derived from this server: invoice, billing-docs, deposits, expense-tracker or asset-register |
| source_id | string | – | Only lines derived from this document, e.g. INV-2026-0001 |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
| until | string | – | Only lines dated on or before this date, YYYY-MM-DD |
No output schema declared.
No examples provided.
ledger_report Report movement and balance per account ~107
Report a built period account by account: debits, credits, movement and closing balance, plus purchase commitments held as memos and the period's exceptions. Pro; ledger_lines gives the lines free.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Needed when the period holds documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
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.
month_close Close a month ~112
List what a month leaves unposted or unbalanced, with its trial balance and bank reconciliation, then store the close as a snapshot; a later call names any drift against it. dry_run writes nothing. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Needed when the period holds documents in more than one currency. Currencies are never added together |
| dry_run | boolean | – | Report the exceptions and the trial balance without writing the close. Default false |
| month | string | yes | The month to close, YYYY-MM |
No output schema declared.
No examples provided.
period_delete Delete a built period ~101
Delete one built period from the register and give its free-tier slot back. Refused when a closed month's snapshot covers the period, and that month is named. No sibling book is touched.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Needed only when the same date range was built in more than one currency |
| from | string | yes | First day of the period, YYYY-MM-DD |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
trial_balance Prove the ledger balances ~113
Total the debits and the credits for a period and prove they are equal to the minor unit. When they are not, name the entries whose own legs do not add up and the source document behind each. Free and unlimited.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Needed when the period holds documents in more than one currency. Currencies are never added together |
| from | string | yes | First day of the period, YYYY-MM-DD |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/cash-book MCP server?
io.github.theluckystrike/cash-book is an MCP server listed in the public MCP registry as io.github.theluckystrike/cash-book. One double-entry ledger derived from your invoices, bank, expenses, deposits and assets. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/cash-book).
Is the io.github.theluckystrike/cash-book MCP server safe to use?
io.github.theluckystrike/cash-book scores 82 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/cash-book MCP server expose?
io.github.theluckystrike/cash-book exposes 9 tools: ledger_build, period_delete, trial_balance, ledger_lines, month_close, and 4 more. Their descriptions and schemas cost roughly 1,071 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/cash-book MCP server require authentication?
Yes. io.github.theluckystrike/cash-book 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/cash-book MCP server still maintained?
io.github.theluckystrike/cash-book 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.