Remote MCP · Endpoint

McpStamp Invoices MCP server

No. McpStamp Invoices answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://mcp.zovo.one/mcp/invoice

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/invoice-pdf-billing-generator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
144 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Numbered invoices with VAT as A4 PDFs, a client list, payments and a list of overdue invoices.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Invoices
CheckedResultHandshake
16 minutes agoHandshake completed144 ms
8 days agoHandshake completed767 ms
9 days agoHandshake completed70 ms
11 days agoHandshake completed543 ms
12 days agoHandshake completed887 ms
13 days agoHandshake completed1.27 s
14 days agoHandshake completed297 ms
14 days agoHandshake completed73 ms
16 days agoHandshake completed169 ms
19 days agoHandshake completed62 ms
21 days agoHandshake completed70 ms
24 days agoHandshake completed40 ms
26 days agoHandshake completed36 ms
28 days agoHandshake completed44 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 Invoices and makes no claim about it beyond what these checks measured.