Remote MCP · Endpoint

ArcID MCP server

Yes, as of 6 hours ago: the hostname does not resolve.

DownLast checked 6 hours ago

Server URL

https://mcp.arcusid.com/mcp

The last check failed: the hostname does not resolve.

Registry name
io.github.arcusid/arcid-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 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
6 hours agoFailed - the hostname does not resolve—
9 days agoHandshake completed221 ms
10 days agoHandshake completed160 ms
11 days agoHandshake completed157 ms
12 days agoHandshake completed132 ms
14 days agoHandshake completed242 ms
15 days agoHandshake completed140 ms
15 days agoHandshake completed204 ms
17 days agoHandshake completed193 ms
19 days agoHandshake completed129 ms
22 days agoHandshake completed157 ms
24 days agoHandshake completed175 ms
26 days agoHandshake completed238 ms
28 days agoHandshake completed156 ms

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

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.