Remote MCP · Endpoint

io.github.theluckystrike/credit-memo MCP server

No. io.github.theluckystrike/credit-memo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/credit-memo

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/credit-memo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Issue a credit memo against an invoice or standalone, with per-line tax and totals.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/credit-memo
CheckedResultHandshake
1 hour agoHandshake completed150 ms
3 days agoHandshake completed21 ms
12 days agoHandshake completed27 ms
13 days agoHandshake completed18 ms
15 days agoHandshake completed38 ms
15 days agoHandshake completed54 ms
17 days agoHandshake completed38 ms
18 days agoHandshake completed64 ms
18 days agoHandshake completed57 ms
20 days agoHandshake completed33 ms
23 days agoHandshake completed95 ms
25 days agoHandshake completed30 ms
28 days agoHandshake completed64 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/credit-memo and makes no claim about it beyond what these checks measured.