Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/statement-of-account

REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20

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

Available components

remote · mcp.zovo.one 84 mcpb · statement-of-account.mcpb 49
+3 this week 84 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
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 (excellent).Pass
  • 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. See how to fix → Fail
  • 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

remote · mcp.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-statement-of-account 'https://mcp.zovo.one/mcp/statement-of-account'
// .cursor/mcp.json
{
  "mcpServers": {
    "theluckystrike-statement-of-account": {
      "url": "https://mcp.zovo.one/mcp/statement-of-account"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "theluckystrike-statement-of-account": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/statement-of-account"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add theluckystrike-statement-of-account --url 'https://mcp.zovo.one/mcp/statement-of-account' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  theluckystrike-statement-of-account:
    url: "https://mcp.zovo.one/mcp/statement-of-account"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "theluckystrike-statement-of-account": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/statement-of-account"
    }
  }
}
# add to Vellum
assistant mcp add theluckystrike-statement-of-account -t streamable-http -u 'https://mcp.zovo.one/mcp/statement-of-account'
// mcp.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 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.

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

  • 13 Sept 26 +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.

  • 11 Sept 26 +1
    • 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 security
    • New prompt “upgrade_to_pro” functional
    • New resource “pricing” functional
  • 10 Sept 26 +1
    • Tool “license_activate” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: good → excellent functional
    • “license_activate” reworded the description of “key” cosmetic
  • 9 Sept 26 +42
    • 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
    • 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 Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 5 Sept 26 36

    First indexed and scored.

Diagnostics

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/statement-of-account

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/statement-of-account Verified 200
http (plaintext) http://mcp.zovo.one/mcp/statement-of-account HTTPS enforced 301 https://mcp.zovo.one/mcp/statement-of-account
MCP tools · 8 exposed · ~1,138 tokens

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 →

Tool Tokens
dunning_text ~214

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.

NameTypeReqDescription
as_ofstring–Age the invoices as at this date, YYYY-MM-DD. Defaults to today
clientstringyesClient id from the invoice server, an exact client name, or a name containing this text
currencystring–Only needed when the client has documents in more than one currency. Currencies are never added together
greetingstring–Opening line, default "Hello" and the client name
levelintegeryes1 friendly reminder, 2 firm reminder, 3 final demand. Level 3 is Pro
sign_offstring–Closing line, default your business name from the shared profile

No output schema declared.

No examples provided.

license_activate ~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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

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.

statement_aging ~144

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.

NameTypeReqDescription
as_ofstring–Age the invoices as at this date, YYYY-MM-DD. Defaults to today
clientstring–One client id or name. Omit to age every client in the books
currencystring–Only this currency. Omit for every currency, each aged separately
limitinteger–Maximum invoice rows returned, default and ceiling 2000

No output schema declared.

No examples provided.

statement_build ~144

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.

NameTypeReqDescription
clientstringyesClient id from the invoice server, an exact client name, or a name containing this text
currencystring–Only needed when the client has documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD. Everything dated before it becomes the opening balance
tostringyesLast day of the period, YYYY-MM-DD, inclusive

No output schema declared.

No examples provided.

statement_pdf ~202

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.

NameTypeReqDescription
as_ofstring–Date printed on the statement, YYYY-MM-DD. Defaults to today
clientstringyesClient id from the invoice server, an exact client name, or a name containing this text
currencystring–Only needed when the client has documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD
out_pathstring–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
tostringyesLast day of the period, YYYY-MM-DD, inclusive

No output schema declared.

No examples provided.

statement_text ~209

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.

NameTypeReqDescription
as_ofstring–Date printed on the statement, YYYY-MM-DD. Defaults to today
clientstringyesClient id from the invoice server, an exact client name, or a name containing this text
currencystring–Only needed when the client has documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD
greetingstring–Opening line, default "Hello" and the client name
sign_offstring–Closing line, default your business name from the shared profile
tostringyesLast day of the period, YYYY-MM-DD, inclusive

No output schema declared.

No examples provided.

statements_report ~94

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.

NameTypeReqDescription
as_ofstring–Age the invoices as at this date, YYYY-MM-DD. Defaults to today
limitinteger–How many clients to list, worst first. Default 20

No output schema declared.

No examples provided.

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.