Remote MCP · Endpoint

io.arcai/arcai MCP server

No. io.arcai/arcai answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://arcai.io/mcp

The last check completed an MCP handshake.

Registry name
io.arcai/arcai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
686 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Crypto intelligence: rug/scam scans for any token, verified whale flows, AI signals + track record
Website
https://arcai.io/developers
Listing
From the official MCP registry (active).
Recent checks of io.arcai/arcai
CheckedResultHandshake
5 hours agoHandshake completed686 ms
10 hours agoHandshake completed703 ms
2 days agoHandshake completed692 ms
4 days agoHandshake completed911 ms
7 days agoHandshake completed686 ms
9 days agoHandshake completed707 ms
11 days agoHandshake completed711 ms
13 days agoHandshake completed715 ms
15 days agoHandshake completed721 ms
18 days agoHandshake completed723 ms
20 days agoHandshake completed720 ms
21 days agoHandshake completed713 ms
23 days agoHandshake completed727 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 io.arcai/arcai and makes no claim about it beyond what these checks measured.