Remote MCP · Endpoint

ArcID MCP server

No. ArcID answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.arcusid.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.arcusid/arcid-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
175 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Look up AI agents on Arc: ERC-8004 identity, feedback, validations and USDC-backed trust scores.
Listing
From the official MCP registry (active).
Recent checks of ArcID
CheckedResultHandshake
2 hours agoHandshake completed175 ms
2 days agoHandshake completed238 ms
4 days agoHandshake completed156 ms
6 days agoHandshake completed381 ms
8 days agoHandshake completed155 ms
10 days agoHandshake completed374 ms
12 days agoHandshake completed179 ms
13 days agoHandshake completed194 ms
14 days agoHandshake completed433 ms
16 days agoHandshake completed122 ms
18 days agoHandshake completed150 ms
20 days agoHandshake completed125 ms
21 days agoHandshake completed140 ms
23 days agoHandshake completed207 ms
24 days agoHandshake completed43 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 ArcID and makes no claim about it beyond what these checks measured.