Remote MCP · Endpoint

InkVoice — XRechnung & E-Invoicing MCP server

No. InkVoice — XRechnung & E-Invoicing answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.inkvoice.net/mcp

The last check completed an MCP handshake.

Registry name
net.inkvoice/inkvoice
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
XRechnung and ZUGFeRD e-invoicing (EN 16931): create, validate, check Leitweg-IDs, German VAT.
Listing
From the official MCP registry (active).
Recent checks of InkVoice — XRechnung & E-Invoicing
CheckedResultHandshake
1 hour agoHandshake completed303 ms
1 day agoHandshake completed300 ms
2 days agoHandshake completed356 ms
3 days agoHandshake completed337 ms
4 days agoHandshake completed327 ms
5 days agoHandshake completed271 ms
6 days agoHandshake completed329 ms
8 days agoHandshake completed368 ms
11 days agoHandshake completed417 ms
13 days agoHandshake completed395 ms
16 days agoHandshake completed410 ms
18 days agoHandshake completed385 ms
20 days agoHandshake completed413 ms
22 days agoHandshake completed422 ms
24 days agoHandshake completed396 ms
26 days agoHandshake completed394 ms
27 days agoHandshake completed389 ms
29 days agoHandshake completed439 ms
30 days agoHandshake completed574 ms

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

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 InkVoice — XRechnung & E-Invoicing and makes no claim about it beyond what these checks measured.