Remote MCP · Endpoint

InvoiceBloom MCP server

No. InvoiceBloom answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://invoicebloom.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.theasteve/invoicebloom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Create, send and track invoices for freelancers and small businesses.
Listing
From the official MCP registry (active).
Recent checks of InvoiceBloom
CheckedResultHandshake
3 hours agoHandshake completed66 ms
9 days agoHandshake completed54 ms
10 days agoHandshake completed53 ms
11 days agoHandshake completed48 ms
12 days agoHandshake completed60 ms
14 days agoHandshake completed46 ms
14 days agoHandshake completed50 ms
15 days agoHandshake completed56 ms
17 days agoHandshake completed69 ms
19 days agoHandshake completed45 ms
21 days agoHandshake completed91 ms
24 days agoHandshake completed49 ms
26 days agoHandshake completed49 ms
28 days agoHandshake completed56 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 InvoiceBloom and makes no claim about it beyond what these checks measured.