Is io.github.nansen-ai/nansen-mcp up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://mcp.nansen.ai/ra/mcp/
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://mcp.nansen.ai/ra/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://mcp.nansen.ai with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 50 tools: address_counterparties, address_counterparties_batch, address_dex_trades, address_first_funder, address_historical_balances, address_labels, address_perp_positions, address_portfolio, address_related_addresses, address_transactions, entity_name_search, general_search, growth_chain_rank, hyperliquid_leaderboard, nansen_score_top_tokens, prediction_market_address_pnl, prediction_market_address_summary, prediction_market_address_trades, prediction_market_lookup, prediction_market_ohlcv, prediction_market_orderbook, prediction_market_pnl_leaderboard, prediction_market_position_detail, prediction_market_screener, prediction_market_top_holders, prediction_market_trades, smart_traders_and_funds_dcas, smart_traders_and_funds_dex_trades, smart_traders_and_funds_historical_token_balances, smart_traders_and_funds_netflow, smart_traders_and_funds_perp_trades, smart_traders_and_funds_pnl_leaderboard, smart_traders_and_funds_token_balances, token_current_top_holders, token_dex_trades, token_discovery_screener, token_flows, token_info, token_jup_dca, token_ohlcv, token_pnl_leaderboard, token_quant_scores, token_recent_flows_summary, token_sectors, token_technical_indicators, token_transfers, token_who_bought_sold, transaction_lookup, wallet_pnl_for_token, wallet_pnl_summary.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameio.github.nansen-ai/nansen-mcp
Endpointhttps://mcp.nansen.ai/ra/mcp/
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy