Remote MCP · Endpoint

InvoiceVista Invoice Maker MCP server

No. InvoiceVista Invoice Maker answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://mcp.invoicevista.com/mcp

The last check completed an MCP handshake.

Registry name
com.invoicevista/invoicevista
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
619 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
See revenue, unpaid invoices, open quotes and your product catalog for each of your businesses.
Listing
From the official MCP registry (active).
Recent checks of InvoiceVista Invoice Maker
CheckedResultHandshake
59 minutes agoHandshake completed619 ms
9 days agoHandshake completed460 ms
10 days agoHandshake completed456 ms
11 days agoHandshake completed448 ms
12 days agoHandshake completed399 ms
14 days agoHandshake completed552 ms
14 days agoHandshake completed410 ms
15 days agoHandshake completed466 ms
17 days agoHandshake completed780 ms
19 days agoHandshake completed431 ms
21 days agoHandshake completed424 ms
24 days agoHandshake completed611 ms
26 days agoHandshake completed400 ms
28 days agoHandshake completed693 ms

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

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