Remote MCP · Endpoint

finisma – ZUGFeRD e-invoices MCP server

No. finisma – ZUGFeRD e-invoices answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://finisma.de/api/mcp

The last check completed an MCP handshake.

Registry name
de.finisma/finisma
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
310 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Create ZUGFeRD e-invoices from JSON or PDF, verify Factur-X, check VAT IDs and Peppol.
Listing
From the official MCP registry (active).
Recent checks of finisma – ZUGFeRD e-invoices
CheckedResultHandshake
53 minutes agoHandshake completed310 ms
2 days agoHandshake completed313 ms
5 days agoHandshake completed397 ms
7 days agoHandshake completed310 ms
9 days agoHandshake completed311 ms
11 days agoHandshake completed308 ms
13 days agoHandshake completed306 ms
15 days agoHandshake completed306 ms
17 days agoHandshake completed302 ms
19 days agoHandshake completed305 ms
20 days agoHandshake completed321 ms
21 days agoHandshake completed309 ms
23 days agoHandshake completed303 ms
25 days agoHandshake completed322 ms

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

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 finisma – ZUGFeRD e-invoices and makes no claim about it beyond what these checks measured.