Remote MCP · Endpoint

Arroway MCP server

No. Arroway answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://www.arroway.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.oaleviola/arroway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Arroway orchestrates people and AI agents around the decisions in force.
Listing
From the official MCP registry (active).
Recent checks of Arroway
CheckedResultHandshake
34 minutes agoHandshake completed67 ms
8 days agoHandshake completed121 ms
9 days agoHandshake completed115 ms
11 days agoHandshake completed93 ms
12 days agoHandshake completed76 ms
12 days agoHandshake completed97 ms
14 days agoHandshake completed356 ms
14 days agoHandshake completed59 ms
16 days agoHandshake completed217 ms
19 days agoHandshake completed99 ms
21 days agoHandshake completed110 ms
24 days agoHandshake completed84 ms
26 days agoHandshake completed111 ms
28 days agoHandshake completed102 ms

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

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