Remote MCP · Endpoint

Arbo MCP server

No. Arbo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://getarbo.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.getarbo/arbo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
292 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Site structure for client redesigns. Page tree with URL, keyword, status and redirect plan export.
Listing
From the official MCP registry (active).
Recent checks of Arbo
CheckedResultHandshake
1 hour agoHandshake completed292 ms
1 day agoHandshake completed292 ms
4 days agoHandshake completed309 ms
6 days agoHandshake completed273 ms
7 days agoHandshake completed294 ms
9 days agoHandshake completed292 ms
10 days agoHandshake completed296 ms
11 days agoHandshake completed273 ms
14 days agoHandshake completed297 ms
15 days agoHandshake completed269 ms
17 days agoHandshake completed273 ms
19 days agoHandshake completed303 ms
20 days agoHandshake completed265 ms
21 days agoHandshake completed270 ms
22 days agoHandshake completed293 ms

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

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