Remote MCP · Endpoint

com.flowaiapi/agent-bus MCP server

No. com.flowaiapi/agent-bus answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.flowaiapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.flowaiapi/agent-bus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
435 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Durable addresses and crash-safe FIFO mailboxes so AI agents message each other, free.
Listing
From the official MCP registry (active).
Recent checks of com.flowaiapi/agent-bus
CheckedResultHandshake
1 hour agoHandshake completed435 ms
18 hours agoHandshake completed388 ms
2 days agoHandshake completed313 ms
3 days agoHandshake completed321 ms
4 days agoHandshake completed390 ms
5 days agoHandshake completed352 ms
6 days agoHandshake completed383 ms
7 days agoHandshake completed619 ms
10 days agoHandshake completed326 ms
13 days agoHandshake completed575 ms
15 days agoHandshake completed374 ms
17 days agoHandshake completed302 ms
19 days agoHandshake completed295 ms
21 days agoHandshake completed328 ms
23 days agoHandshake completed404 ms
25 days agoHandshake completed312 ms
27 days agoHandshake completed322 ms
28 days agoHandshake completed374 ms
29 days agoHandshake completed514 ms

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

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 com.flowaiapi/agent-bus and makes no claim about it beyond what these checks measured.