Remote MCP · Endpoint

io.github.theluckystrike/trial-balance MCP server

No. io.github.theluckystrike/trial-balance answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/trial-balance

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/trial-balance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Prove your books balance: every debit and credit for a month, to the minor unit.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/trial-balance
CheckedResultHandshake
1 hour agoHandshake completed150 ms
3 days agoHandshake completed50 ms
12 days agoHandshake completed37 ms
13 days agoHandshake completed29 ms
15 days agoHandshake completed42 ms
15 days agoHandshake completed72 ms
17 days agoHandshake completed24 ms
18 days agoHandshake completed55 ms
18 days agoHandshake completed58 ms
20 days agoHandshake completed54 ms
23 days agoHandshake completed94 ms
25 days agoHandshake completed51 ms
28 days agoHandshake completed78 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.theluckystrike/trial-balance and makes no claim about it beyond what these checks measured.