Remote MCP · Endpoint

McpStamp Credit Notes MCP server

No. McpStamp Credit Notes answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/credit-memo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
20 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Credit all or part of an invoice with the VAT reversed, raise purchase orders, print A4 PDFs.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Credit Notes
CheckedResultHandshake
14 minutes agoHandshake completed20 ms
9 days agoHandshake completed28 ms
9 days agoHandshake completed70 ms
11 days agoHandshake completed95 ms
12 days agoHandshake completed74 ms
13 days agoHandshake completed44 ms
14 days agoHandshake completed58 ms
15 days agoHandshake completed28 ms
16 days agoHandshake completed29 ms
19 days agoHandshake completed87 ms
22 days agoHandshake completed64 ms
24 days agoHandshake completed37 ms
26 days agoHandshake completed72 ms
28 days agoHandshake completed57 ms

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

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 McpStamp Credit Notes and makes no claim about it beyond what these checks measured.