Remote MCP · Endpoint

arcgate MCP server

Yes, as of 9 hours ago: the request timed out.

DownLast checked 9 hours ago

Server URL

https://api.arcgate.dev/mcp

The last check failed: the request timed out.

Registry name
dev.arcgate/arcgate
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
48 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Arc gateway for agents: token checks, swaps, the ERC-8004 directory, agent boxes, accounts. x402
Listing
From the official MCP registry (active).
Recent checks of arcgate
CheckedResultHandshake
9 hours agoFailed - the request timed out—
4 days agoHandshake completed165 ms
14 days agoHandshake completed237 ms
15 days agoHandshake completed184 ms
15 days agoHandshake completed470 ms
17 days agoHandshake completed159 ms
18 days agoHandshake completed206 ms
19 days agoHandshake completed500 ms
20 days agoHandshake completed128 ms
21 days agoHandshake completed303 ms
23 days agoHandshake completed194 ms
26 days agoHandshake completed157 ms
28 days agoFailed - the server returned an HTTP error—

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

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