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.

Zovo Spending Report

REMOTE · SPENDING-REPORT.ZOVO.ONE

Turn your bank statement into a budget and see where your money goes.

+3 this week 79 Trust /100

Last scanned (17 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability72
  • 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 1005 tokens (~335/item across 3 items; 2 tools + 1 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 Management43
  • Stability observed for 13 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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 Nov 26 +1

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

  • 18 Nov 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.

  • 16 Nov 26 +1

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

  • 14 Nov 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.

  • 12 Nov 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.

  • 10 Nov 26 +1

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

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 73

    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 21 Nov 2026 · Probed https://spending-report.zovo.one/mcp

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 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 f1971975b30f87fc0e8936cda4cd5f1e
SANs: zovo.one, spending-report.zovo.one, *.spending-report.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 spending-report.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://spending-report.zovo.one/mcp Verified 200
http (plaintext) http://spending-report.zovo.one/mcp HTTPS enforced 301 https://spending-report.zovo.one/mcp
MCP tools · 2 exposed · ~906 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
categorize_spending ~448

Use this when the user pastes or lists bank or credit card transactions (date, description, amount) and asks where their money goes, to categorize spending, make a budget from them, or find subscriptions and recurring charges. Accepts a list of rows or pasted text/CSV. Returns the same report as generate_spending_report: spending by category, income vs spending, monthly totals, top merchants, recurring charges with cost per year, uncategorized merchants, Excel and PDF downloads. To correct categories, call again with the same rows and category_overrides. Use generate_spending_report when a statement file is attached. Does not connect to banks and does not give financial advice.

NameTypeReqDescription
account_typestring–Optional: bank (checking or savings) or credit_card. Default: detected from the file; pasted rows count as bank. Example: credit_card.
category_overrides––Optional: your category for merchants the rules got wrong or left Uncategorized, keyed by the merchant name shown in the result. Example: {"Blue Bottle":"Dining","Riverbend Design":"Income","Venmo":"…
date_orderstring–Optional: order of numeric dates such as 03/04/2026: MDY (US, default) or DMY (day first). Example: DMY.
statement_yearnumber|string–Optional: the year for dates printed without one, e.g. 2026.
transactions–yesThe transactions: a list like [{"date":"2026-09-02","description":"NETFLIX.COM","amount":-15.49}], or the rows pasted as text or CSV, e.g. "09/02/2026, NETFLIX.COM, -15.49". Money out negative, money…
NameTypeReqDescription
categoriesarrayyes–
downloadsobjectyes–
headlinestringyes–
monthsarrayyes–
overrides_appliedarrayyes–
recurringarrayyes–
rulesarrayyes–
sourceobjectyes–
top_merchantsarrayyes–
totalsobjectyes–
uncategorizedarrayyes–
warningsarrayyes–

No examples provided.

generate_spending_report ~458

Use this when the user attaches a bank or credit card statement (text PDF, CSV or Excel export) and asks to turn it into a budget, see where their money goes, find subscriptions or recurring charges, or total spending by category or month. Returns spending by category, income vs spending and net, monthly totals, top merchants, recurring charges with next expected date and cost per year, a list of uncategorized merchants, an Excel workbook and a one-page PDF summary. Transfers between own accounts and credit card payments are not counted as spending. To correct categories, call again with the same file and category_overrides. Does not connect to banks, does not read scanned images (needs OCR first), and does not give financial advice.

NameTypeReqDescription
account_typestring–Optional: bank (checking or savings) or credit_card. Default: detected from the file; pasted rows count as bank. Example: credit_card.
category_overrides––Optional: your category for merchants the rules got wrong or left Uncategorized, keyed by the merchant name shown in the result. Example: {"Blue Bottle":"Dining","Riverbend Design":"Income","Venmo":"…
date_orderstring–Optional: order of numeric dates such as 03/04/2026: MDY (US, default) or DMY (day first). Example: DMY.
fileobjectyesThe bank or credit card statement: a text PDF from the bank's website, or the CSV or Excel (.xlsx) transaction export, e.g. september-statement.pdf.
flip_signsboolean|string–Optional, CSV/Excel only: true when the export lists purchases as positive numbers and payments as negative (some card exports). Default false.
statement_yearnumber|string–Optional: the year for dates printed without one, e.g. 2026.
NameTypeReqDescription
categoriesarrayyes–
downloadsobjectyes–
headlinestringyes–
monthsarrayyes–
overrides_appliedarrayyes–
recurringarrayyes–
rulesarrayyes–
sourceobjectyes–
top_merchantsarrayyes–
totalsobjectyes–
uncategorizedarrayyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Zovo Spending Report MCP server?

Zovo Spending Report is a hosted endpoint at https://spending-report.zovo.one/mcp, 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 · spending-report.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-spending-report 'https://spending-report.zovo.one/mcp'
Common questions

What is the Zovo Spending Report MCP server?

Zovo Spending Report is an MCP server listed in the public MCP registry as io.github.theluckystrike/spending-report. Turn your bank statement into a budget and see where your money goes. This page covers its hosted endpoint (https://spending-report.zovo.one/mcp).

Is the Zovo Spending Report MCP server safe to use?

Zovo Spending Report scores 79 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 Zovo Spending Report MCP server expose?

Zovo Spending Report exposes 2 tools: generate_spending_report, categorize_spending. Their descriptions and schemas cost roughly 906 tokens of context every time the server is loaded.

Does the Zovo Spending Report MCP server require authentication?

No. We connected to Zovo Spending Report without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Zovo Spending Report MCP server still maintained?

Zovo Spending Report is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Zovo Spending Report MCP server?

VerifyMCP ran 14 checks on Zovo Spending Report, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.