Remote MCP · Endpoint

invowerk MCP server

No. invowerk answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.invowerk.dev/mcp/

The last check completed an MCP handshake.

Registry name
dev.invowerk/xrechnung-e-invoice-validator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
288 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
E-invoice checker for ZUGFeRD, Factur-X, XRechnung and Peppol BIS. Free web tool, API and MCP.
Listing
From the official MCP registry (active).
Recent checks of invowerk
CheckedResultHandshake
1 day agoHandshake completed288 ms
11 days agoHandshake completed326 ms
12 days agoHandshake completed302 ms
13 days agoHandshake completed333 ms
14 days agoHandshake completed344 ms
15 days agoHandshake completed316 ms
16 days agoHandshake completed321 ms
17 days agoHandshake completed310 ms
18 days agoHandshake completed326 ms
20 days agoHandshake completed439 ms
23 days agoHandshake completed326 ms
25 days agoHandshake completed326 ms
27 days agoHandshake completed322 ms

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

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