# io.github.theluckystrike/statement-of-account (remote · mcp.zovo.one)

Statements of account, aging buckets and dunning letters from your invoices.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 84/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-statement-of-account/mcp-statement-of-account.md), [page](https://verifymcp.io/servers/theluckystrike-statement-of-account/mcp-statement-of-account)
- mcpb · `statement-of-account.mcpb`: 49/100, [markdown](https://verifymcp.io/servers/theluckystrike-statement-of-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-statement.md), [page](https://verifymcp.io/servers/theluckystrike-statement-of-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-statement)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/statement-of-account`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## 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-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/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 1215 tokens (~121/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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/statement-of-account MCP server?

io.github.theluckystrike/statement-of-account is a hosted endpoint at https://mcp.zovo.one/mcp/statement-of-account, 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-statement-of-account 'https://mcp.zovo.one/mcp/statement-of-account'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-statement-of-account": {
      "url": "https://mcp.zovo.one/mcp/statement-of-account"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-statement-of-account": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/statement-of-account"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-statement-of-account]
url = "https://mcp.zovo.one/mcp/statement-of-account"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-statement-of-account --url 'https://mcp.zovo.one/mcp/statement-of-account' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-statement-of-account:
    url: "https://mcp.zovo.one/mcp/statement-of-account"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-statement-of-account": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/statement-of-account"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-statement-of-account -t streamable-http -u 'https://mcp.zovo.one/mcp/statement-of-account'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-statement-of-account": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/statement-of-account"
    }
  }
}
```

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-20 (score 84, +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.

### 2026-09-17 (score 83, +1)

- [functional] Server version: 0.21.0 → 0.22.0

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

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

### 2026-09-13 (score 81, +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-11 (score 80, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “dunning_text” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 79, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 78, +42)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-09-05 (score 36)

First indexed and scored.

## MCP tools (8)

### `statement_build` (~144 tokens)

Build a statement of account

Build one client's statement for a period: opening, invoices, payments with deposits applied broken out, credit notes and closing, formatted and in minor units. Free: 5 a month; a rebuild is free.

Input parameters:

- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `from` (string, required): First day of the period, YYYY-MM-DD. Everything dated before it becomes the opening balance
- `to` (string, required): Last day of the period, YYYY-MM-DD, inclusive

### `statement_aging` (~144 tokens)

Age the open invoices

Age open invoices into 0-30, 31-60, 61-90 and over 90 days past DUE date at a date, per client and currency, with the invoices themselves. Free. statements_report rolls up the whole book instead.

Input parameters:

- `as_of` (string): Age the invoices as at this date, YYYY-MM-DD. Defaults to today
- `client` (string): One client id or name. Omit to age every client in the books
- `currency` (string): Only this currency. Omit for every currency, each aged separately
- `limit` (integer): Maximum invoice rows returned, default and ceiling 2000

### `statement_text` (~209 tokens)

Plain-text statement of account

Turn one client's statement into a plain-text letter for an email: movements in date order, opening and closing balances, deposit held, a sign-off. It is also a .txt download link valid one hour and counts toward the 5 a month; statement_pdf writes the A4 page.

Input parameters:

- `as_of` (string): Date printed on the statement, YYYY-MM-DD. Defaults to today
- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `from` (string, required): First day of the period, YYYY-MM-DD
- `greeting` (string): Opening line, default "Hello" and the client name
- `sign_off` (string): Closing line, default your business name from the shared profile
- `to` (string, required): Last day of the period, YYYY-MM-DD, inclusive

### `statement_pdf` (~202 tokens)

Render the statement of account as a PDF

Call this tool to render one client's A4 statement of account and return a download link valid for one hour. Titled STATEMENT OF ACCOUNT, movements in date order, BALANCE OUTSTANDING at the foot. Pro.

Input parameters:

- `as_of` (string): Date printed on the statement, YYYY-MM-DD. Defaults to today
- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `from` (string, required): First day of the period, YYYY-MM-DD
- `out_path` (string): Name for the downloaded file, e.g. acme-statement. Defaults to the client, currency and period; the statement comes back as a download link valid for one hour
- `to` (string, required): Last day of the period, YYYY-MM-DD, inclusive

### `dunning_text` (~214 tokens)

Write a dunning letter

Write a payment chaser at level 1 friendly, 2 firm or 3 final demand: every OVERDUE invoice with its age, the total and your bank details. Refused if nothing is overdue. No interest is stated. The letter is also a .txt download link valid one hour. Level 3 is Pro.

Input parameters:

- `as_of` (string): Age the invoices as at this date, YYYY-MM-DD. Defaults to today
- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `greeting` (string): Opening line, default "Hello" and the client name
- `level` (integer, required): 1 friendly reminder, 2 firm reminder, 3 final demand. Level 3 is Pro
- `sign_off` (string): Closing line, default your business name from the shared profile

### `statements_report` (~94 tokens)

What every client owes

Receivables across every client at a date: totals and aging per currency, clients ranked by how much is OVERDUE, and the oldest overdue invoice. Pro. statement_aging is the free per-client view.

Input parameters:

- `as_of` (string): Age the invoices as at this date, YYYY-MM-DD. Defaults to today
- `limit` (integer): How many clients to list, worst first. Default 20

### `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-statement-of-account/mcp-statement-of-account#diagnostics

## Score history

- 2026-09-20: 84
- 2026-09-19: 83
- 2026-09-18: 83
- 2026-09-17: 83
- 2026-09-16: 82
- 2026-09-15: 82
- 2026-09-14: 81
- 2026-09-13: 81
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36

## Common questions

### What is the io.github.theluckystrike/statement-of-account MCP server?

io.github.theluckystrike/statement-of-account is an MCP server listed in the public MCP registry as io.github.theluckystrike/statement-of-account. Statements of account, aging buckets and dunning letters from your invoices. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/statement-of-account).

### Is the io.github.theluckystrike/statement-of-account MCP server safe to use?

io.github.theluckystrike/statement-of-account scores 84 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/statement-of-account MCP server expose?

io.github.theluckystrike/statement-of-account exposes 8 tools: statement_build, statement_aging, statement_text, statement_pdf, dunning_text, and 3 more. Their descriptions and schemas cost roughly 1,138 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/statement-of-account MCP server require authentication?

Yes. io.github.theluckystrike/statement-of-account 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/statement-of-account MCP server still maintained?

io.github.theluckystrike/statement-of-account 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.

## Links

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