Remote MCP · Endpoint

io.github.theluckystrike/expenses-tracker MCP server

No. io.github.theluckystrike/expenses-tracker answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.zovo.one/mcp/expenses-tracker

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/expenses-tracker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
243 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Track expenses from your AI chat: log, categorize, monthly CSV reports. All data is local.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/expenses-tracker
CheckedResultHandshake
2 hours agoHandshake completed243 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed116 ms
6 days agoHandshake completed23 ms
8 days agoHandshake completed31 ms
9 days agoHandshake completed80 ms
10 days agoHandshake completed112 ms
11 days agoHandshake completed35 ms
14 days agoHandshake completed40 ms
16 days agoHandshake completed35 ms
17 days agoHandshake completed43 ms
19 days agoHandshake completed32 ms
20 days agoHandshake completed22 ms
21 days agoHandshake completed18 ms
22 days agoHandshake completed23 ms
22 days agoHandshake completed50 ms
24 days agoHandshake completed693 ms

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

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/expenses-tracker and makes no claim about it beyond what these checks measured.