McpStamp Statement of Account
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Client statements of account, ageing of open invoices and payment chasers as text or PDF.
Available components
Last scanned (19 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 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
- Context-footprint check failed: tool/resource definitions use about 1331 tokens (~133/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 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
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.
- 2 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 16 Oct 26 0
- Server version: 0.22.0 → 0.22.6 functional
- 15 Oct 26 +70
- Stability: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Oct 26 −69
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 83 to 93. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 90
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 4 Nov 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 | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| 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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/statement-of-account"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/statement-of-account"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/statement-of-account |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/statement-of-account |
| Authorisation server | https://mcp.zovo.one |
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 |
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 →
dunning_text Write a dunning letter ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Age the invoices as at this date, YYYY-MM-DD. Defaults to today |
| client | string | yes | 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 | yes | 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 |
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.
statement_aging Age the open invoices ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
statement_build Build a statement of account ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | 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 | yes | First day of the period, YYYY-MM-DD. Everything dated before it becomes the opening balance |
| to | string | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
statement_pdf Render the statement of account as a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date printed on the statement, YYYY-MM-DD. Defaults to today |
| client | string | yes | 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 | yes | 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 | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
statement_text Plain-text statement of account ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date printed on the statement, YYYY-MM-DD. Defaults to today |
| client | string | yes | 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 | yes | 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 | yes | Last day of the period, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
statements_report What every client owes ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
How do I install the McpStamp Statement of Account MCP server?
McpStamp 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
claude mcp add --transport http theluckystrike-statement-of-account 'https://mcp.zovo.one/mcp/statement-of-account'
What is the McpStamp Statement of Account MCP server?
McpStamp Statement of Account is an MCP server listed in the public MCP registry as io.github.theluckystrike/statement-of-account. Client statements of account, ageing of open invoices and payment chasers as text or PDF. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/statement-of-account).
Is the McpStamp Statement of Account MCP server safe to use?
McpStamp Statement of Account scores 94 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 McpStamp Statement of Account MCP server expose?
McpStamp 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 McpStamp Statement of Account MCP server require authentication?
Yes. McpStamp 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 McpStamp Statement of Account MCP server still maintained?
McpStamp Statement of Account is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.