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 Group Expenses

REMOTE · GROUP-EXPENSES.ZOVO.ONE

Shared trip and house expenses

+3 this week 73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% 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 Security63
Transport & Reachability100
Schema Quality & AI Usability76
  • 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 871 tokens (~174/item across 5 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 67

    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://group-expenses.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 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.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 group-expenses.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://group-expenses.zovo.one/mcp Verified 200
http (plaintext) http://group-expenses.zovo.one/mcp HTTPS enforced 301 https://group-expenses.zovo.one/mcp
MCP tools · 4 exposed · ~792 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
add_ledger_expenses ~143

Use this when the organizer tells you about expenses or payments to add to an existing shared ledger. Takes the private organizer link and up to 40 expenses or payments; returns the new balances. Names must match the members. Does not edit or delete expenses (use update_expense_ledger to delete).

NameTypeReqDescription
expensesarray–Expenses to add.
manage_linkstringyesThe private organizer link returned when the ledger was created, e.g. https://group-expenses.zovo.one/m/AbC.../XyZ...
paymentsarray–Payments made between members, e.g. Ben paid Ana back 42.25.
NameTypeReqDescription
changesarray––
closedbooleanyes–
currencystringyes–
endedbooleanyes–
expense_countnumberyes–
expires_atstringyes–
manage_urlstringyes–
minor_digitsnumberyes–
number_formatstring––
payment_countnumberyes–
peoplearrayyes–
people_countobject––
public_urlstringyes–
recentarrayyes–
recent_countobject––
rulestringyes–
settle_uparrayyes–
settle_up_zeroes_allbooleanyes–
titlestringyes–
totalstringyes–

No examples provided.

create_expense_ledger ~318

Use this when a group wants to track shared costs for a trip, a shared house or an event and split them fairly: it publishes a shared web page where everyone adds what they paid, and returns a public link to share and a private organizer link. Optional starting expenses and payments can be included. Amounts use whole minor units of one currency (no conversion). Members are first names, 2 to 30. Does not move money, convert currencies or send reminders. Do not use for a one-off bill split that nobody else needs to see.

NameTypeReqDescription
currencystringyesISO 4217 currency code, e.g. EUR, USD, GBP, JPY, KWD.
expensesarray–Optional expenses to add right away.
membersarrayyesFirst names of the people sharing costs (2-30), e.g. ["Ana", "Ben", "Chi"].
notestring–Optional note shown on the page, e.g. Add every shared cost here.
number_formatstring–How people type amounts on the page, e.g. 1,234.56. Default depends on the currency (EUR uses 1.234,56).
paymentsarray–Optional payments already made between members.
time_zonestring–Optional IANA time zone for dates on the page, e.g. Europe/Lisbon. Default UTC.
titlestring–Name of the ledger, e.g. Lisbon trip 2026.
NameTypeReqDescription
changesarray––
closedbooleanyes–
currencystringyes–
endedbooleanyes–
expense_countnumberyes–
expires_atstringyes–
manage_urlstringyes–
minor_digitsnumberyes–
number_formatstring––
payment_countnumberyes–
peoplearrayyes–
people_countobject––
public_urlstringyes–
recentarrayyes–
recent_countobject––
rulestringyes–
settle_uparrayyes–
settle_up_zeroes_allbooleanyes–
titlestringyes–
totalstringyes–

No examples provided.

show_expense_ledger_results ~120

Use this when the organizer asks for the balances, who owes whom, or the settle-up payments of a shared expense ledger made with create_expense_ledger. Takes the private organizer link and returns each person's paid, share and balance, the settle-up list and recent expenses. Does not change the ledger. Do not use without the organizer link.

NameTypeReqDescription
manage_linkstringyesThe private organizer link returned when the ledger was created, e.g. https://group-expenses.zovo.one/m/AbC.../XyZ...
NameTypeReqDescription
changesarray––
closedbooleanyes–
currencystringyes–
endedbooleanyes–
expense_countnumberyes–
expires_atstringyes–
manage_urlstringyes–
minor_digitsnumberyes–
number_formatstring––
payment_countnumberyes–
peoplearrayyes–
people_countobject––
public_urlstringyes–
recentarrayyes–
recent_countobject––
rulestringyes–
settle_uparrayyes–
settle_up_zeroes_allbooleanyes–
titlestringyes–
totalstringyes–

No examples provided.

update_expense_ledger ~211

Use this when the organizer wants to add members, delete expenses by their number (#3), rename the ledger, change the note, or close or reopen the page. Takes the private organizer link. Deleting removes the expense from all balances. Does not remove members who are already in expenses.

NameTypeReqDescription
add_membersarray–New members to add, e.g. ["Eli"].
delete_expensesarray–Numbers of expenses or payments to delete, as shown on the page, e.g. [3].
manage_linkstringyesThe private organizer link returned when the ledger was created, e.g. https://group-expenses.zovo.one/m/AbC.../XyZ...
notestring–New note shown on the page; empty text removes it.
statusstring–closed stops new expenses (balances stay visible); open allows them again.
titlestring–New title, e.g. Lisbon trip (final).
NameTypeReqDescription
changesarray––
closedbooleanyes–
currencystringyes–
endedbooleanyes–
expense_countnumberyes–
expires_atstringyes–
manage_urlstringyes–
minor_digitsnumberyes–
number_formatstring––
payment_countnumberyes–
peoplearrayyes–
people_countobject––
public_urlstringyes–
recentarrayyes–
recent_countobject––
rulestringyes–
settle_uparrayyes–
settle_up_zeroes_allbooleanyes–
titlestringyes–
totalstringyes–

No examples provided.

Install

How do I install the Zovo Group Expenses MCP server?

Zovo Group Expenses is a hosted endpoint at https://group-expenses.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 · group-expenses.zovo.one

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

What is the Zovo Group Expenses MCP server?

Zovo Group Expenses is an MCP server listed in the public MCP registry as io.github.theluckystrike/group-expenses. Shared trip and house expenses. This page covers its hosted endpoint (https://group-expenses.zovo.one/mcp).

Is the Zovo Group Expenses MCP server safe to use?

Zovo Group Expenses scores 73 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 Group Expenses MCP server expose?

Zovo Group Expenses exposes 4 tools: create_expense_ledger, show_expense_ledger_results, add_ledger_expenses, update_expense_ledger. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.

Does the Zovo Group Expenses MCP server require authentication?

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

Is the Zovo Group Expenses MCP server still maintained?

Zovo Group Expenses 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 Group Expenses MCP server?

VerifyMCP ran 14 checks on Zovo Group Expenses, 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.