Remote MCP · Endpoint

arcgate MCP server

No. arcgate answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.arcgate.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.arcgate/arcgate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
48 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Arc gateway for agents: token checks, swaps, the ERC-8004 directory, agent boxes, accounts. x402
Website
https://docs.arcgate.dev/
Listing
From the official MCP registry (active).
Recent checks of arcgate
CheckedResultHandshake
1 hour agoHandshake completed128 ms
1 day agoHandshake completed303 ms
3 days agoHandshake completed194 ms
5 days agoHandshake completed157 ms
8 days agoFailed - the server returned an HTTP error—
10 days agoHandshake completed250 ms
12 days agoHandshake completed151 ms
14 days agoHandshake completed167 ms
16 days agoHandshake completed149 ms
18 days agoHandshake completed405 ms
20 days agoHandshake completed172 ms
22 days agoHandshake completed141 ms
23 days agoHandshake completed180 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.