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/trial-balance

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

Prove your books balance: every debit and credit for a month, to the minor unit.

+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 Security94
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 (good).Pass
  • Tool/resource definitions use about 1148 tokens (~104/item across 11 items; 9 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Install

How do I install the io.github.theluckystrike/trial-balance MCP server?

io.github.theluckystrike/trial-balance is a hosted endpoint at https://mcp.zovo.one/mcp/trial-balance, 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-trial-balance 'https://mcp.zovo.one/mcp/trial-balance'
// .cursor/mcp.json
{
  "mcpServers": {
    "theluckystrike-trial-balance": {
      "url": "https://mcp.zovo.one/mcp/trial-balance"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "theluckystrike-trial-balance": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/trial-balance"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.theluckystrike-trial-balance]
url = "https://mcp.zovo.one/mcp/trial-balance"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-trial-balance": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/trial-balance",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add theluckystrike-trial-balance --url 'https://mcp.zovo.one/mcp/trial-balance' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  theluckystrike-trial-balance:
    url: "https://mcp.zovo.one/mcp/trial-balance"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "theluckystrike-trial-balance": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/trial-balance"
    }
  }
}
# add to Vellum
assistant mcp add theluckystrike-trial-balance -t streamable-http -u 'https://mcp.zovo.one/mcp/trial-balance'
// mcp.json
{
  "mcpServers": {
    "theluckystrike-trial-balance": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/trial-balance"
    }
  }
}

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.

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

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 23 Sept 26 81

    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 30 Sept 2026 · Probed https://mcp.zovo.one/mcp/trial-balance

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 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", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"

Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"
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
Retrieved Yes
Resource https://mcp.zovo.one
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/trial-balance Verified 200
http (plaintext) http://mcp.zovo.one/mcp/trial-balance HTTPS enforced 301 https://mcp.zovo.one/mcp/trial-balance
MCP tools · 9 exposed · ~1,071 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
ledger_build ~112

Derive the double-entry ledger for one period in ONE currency from the invoice, credit note, deposit, expense, bank and asset stores, and register it. Nothing is written back. Free: 3 periods a month.

NameTypeReqDescription
currencystring–Needed when the period holds documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD
tostringyesLast day of the period, YYYY-MM-DD, inclusive

No output schema declared.

No examples provided.

ledger_export_csv ~143

Return the period's ledger lines as RFC 4180 CSV, one row per leg, as a download link valid for one hour. Pro, but ledger_lines returns these same fields free and unlimited; this only lays them out as CSV columns.

NameTypeReqDescription
accountstring–Only this account or category prefix
currencystring–Needed when the period holds documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD
sourcestring–Only lines derived from this server
tostringyesLast day of the period, YYYY-MM-DD, inclusive

No output schema declared.

No examples provided.

ledger_lines ~252

List the ledger lines for a period, filtered by account, source server, source_id or date; each carries its debit, credit and bank_ref, with the totals of the rows returned. Filtered totals do not balance. Free.

NameTypeReqDescription
accountstring–Only this account, e.g. cash, receivables, vat_output, or a category prefix such as "expenses"
currencystring–Needed when the period holds documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD
limitinteger–Maximum rows, default and ceiling 5000
sincestring–Only lines dated on or after this date, YYYY-MM-DD
sourcestring–Only lines derived from this server: invoice, billing-docs, deposits, expense-tracker or asset-register
source_idstring–Only lines derived from this document, e.g. INV-2026-0001
tostringyesLast day of the period, YYYY-MM-DD, inclusive
untilstring–Only lines dated on or before this date, YYYY-MM-DD

No output schema declared.

No examples provided.

ledger_report ~107

Report a built period account by account: debits, credits, movement and closing balance, plus purchase commitments held as memos and the period's exceptions. Pro; ledger_lines gives the lines free.

NameTypeReqDescription
currencystring–Needed when the period holds documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD
tostringyesLast day of the period, YYYY-MM-DD, inclusive

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.

month_close ~112

List what a month leaves unposted or unbalanced, with its trial balance and bank reconciliation, then store the close as a snapshot; a later call names any drift against it. dry_run writes nothing. Pro.

NameTypeReqDescription
currencystring–Needed when the period holds documents in more than one currency. Currencies are never added together
dry_runboolean–Report the exceptions and the trial balance without writing the close. Default false
monthstringyesThe month to close, YYYY-MM

No output schema declared.

No examples provided.

period_delete ~101

Delete one built period from the register and give its free-tier slot back. Refused when a closed month's snapshot covers the period, and that month is named. No sibling book is touched.

NameTypeReqDescription
currencystring–Needed only when the same date range was built in more than one currency
fromstringyesFirst day of the period, YYYY-MM-DD
tostringyesLast day of the period, YYYY-MM-DD, inclusive

No output schema declared.

No examples provided.

trial_balance ~113

Total the debits and the credits for a period and prove they are equal to the minor unit. When they are not, name the entries whose own legs do not add up and the source document behind each. Free and unlimited.

NameTypeReqDescription
currencystring–Needed when the period holds documents in more than one currency. Currencies are never added together
fromstringyesFirst day of the period, YYYY-MM-DD
tostringyesLast day of the period, YYYY-MM-DD, inclusive

No output schema declared.

No examples provided.

Common questions

What is the io.github.theluckystrike/trial-balance MCP server?

io.github.theluckystrike/trial-balance is an MCP server listed in the public MCP registry as io.github.theluckystrike/trial-balance. Prove your books balance: every debit and credit for a month, to the minor unit. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/trial-balance).

Is the io.github.theluckystrike/trial-balance MCP server safe to use?

io.github.theluckystrike/trial-balance 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/trial-balance MCP server expose?

io.github.theluckystrike/trial-balance exposes 9 tools: ledger_build, period_delete, trial_balance, ledger_lines, month_close, and 4 more. Their descriptions and schemas cost roughly 1,071 tokens of context every time the server is loaded.

Does the io.github.theluckystrike/trial-balance MCP server require authentication?

Yes. io.github.theluckystrike/trial-balance 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/trial-balance MCP server still maintained?

io.github.theluckystrike/trial-balance is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.