Remote MCP · Endpoint

InvoiceForge MCP server

No. InvoiceForge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://invoiceforge.agenttoolworks.com/mcp

The last check completed an MCP handshake.

Registry name
com.agenttoolworks/invoiceforge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
583 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Generate, validate and read EN 16931 and Peppol BIS 3.0 e-invoices, in UBL and CII.
Listing
From the official MCP registry (active).
Recent checks of InvoiceForge
CheckedResultHandshake
1 hour agoHandshake completed583 ms
2 days agoHandshake completed484 ms
4 days agoHandshake completed528 ms
6 days agoHandshake completed455 ms
8 days agoHandshake completed570 ms
10 days agoHandshake completed599 ms
12 days agoHandshake completed515 ms
14 days agoHandshake completed478 ms
16 days agoHandshake completed624 ms
17 days agoHandshake completed553 ms
18 days agoHandshake completed519 ms
20 days agoHandshake completed480 ms
22 days agoHandshake completed569 ms
24 days agoCredentials required—

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