Remote MCP · Endpoint

dev.invoicehub/invoicehub MCP server

No. dev.invoicehub/invoicehub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.invoicehub.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.invoicehub/invoicehub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
369 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.
Listing
From the official MCP registry (active).
Recent checks of dev.invoicehub/invoicehub
CheckedResultHandshake
1 hour agoHandshake completed369 ms
1 day agoHandshake completed459 ms
2 days agoHandshake completed505 ms
3 days agoHandshake completed379 ms
4 days agoHandshake completed698 ms
5 days agoHandshake completed347 ms
6 days agoHandshake completed395 ms
9 days agoHandshake completed538 ms
12 days agoHandshake completed385 ms
14 days agoHandshake completed766 ms
16 days agoHandshake completed376 ms
18 days agoHandshake completed396 ms
20 days agoHandshake completed365 ms
22 days agoHandshake completed356 ms
24 days agoHandshake completed460 ms
26 days agoHandshake completed332 ms
27 days agoHandshake completed481 ms
28 days agoHandshake completed593 ms

The last 18 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 dev.invoicehub/invoicehub and makes no claim about it beyond what these checks measured.