Remote MCP · Endpoint

Nansen MCP server

No. Nansen answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.nansen.ai/ra/mcp/

The last check completed an MCP handshake.

Registry name
io.github.nansen-ai/nansen-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
50 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Blockchain analytics API for AI agents. Smart Money signals, wallet profiling, token analytics.
Listing
From the official MCP registry (active).
Recent checks of Nansen
CheckedResultHandshake
34 minutes agoHandshake completed68 ms
2 days agoHandshake completed49 ms
4 days agoHandshake completed49 ms
5 days agoHandshake completed46 ms
7 days agoHandshake completed76 ms
8 days agoHandshake completed51 ms
9 days agoHandshake completed54 ms
12 days agoHandshake completed48 ms
13 days agoHandshake completed54 ms
15 days agoHandshake completed59 ms
17 days agoHandshake completed75 ms
18 days agoHandshake completed51 ms
19 days agoHandshake completed47 ms
20 days agoHandshake completed52 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed51 ms
23 days agoHandshake completed52 ms

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

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