Connect Arctic and your agent gets 3 tools, among them robinhood_radar, scan_token, trace_wallet. It answers at https://www.arctic.qpon/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 4 October 2026; the last check, on 19 November 2026, succeeded.
Read Robinhood Chain live: scan a token, trace its deployer, list new launches.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
robinhood_radar | List Robinhood Chain tokens right now: `new` gives the latest Pons v2 launches (age, curve progress, market cap), `trending` gives the most traded tokens over 24h (volume, liquidity, buys and sells, change). Use it to find tokens, then scan Inputs: list, limit |
scan_token | Read a Robinhood Chain token right now: name, supply, owner powers, Pons v2 launch and graduation, creator tax, price, market cap, liquidity, 24h volume, buys and sells, deployer share and burned share. Every key carries its unit. Use it wh Inputs: address |
trace_wallet | Read the wallet behind a Robinhood Chain token: how many tokens it launched through the Pons v2 factory in the last hours, how many graduated, how many are still on a curve, and whether it bought or sold on its own curves. Use it when the u Inputs: wallet, hours |
Every block below points at https://www.arctic.qpon/api/mcp. Pick your client and copy.
claude mcp add --transport http arctic https://www.arctic.qpon/api/mcp
{
"mcpServers": {
"arctic": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://www.arctic.qpon/api/mcp"]
}
}
}{
"mcpServers": {
"arctic": {
"url": "https://www.arctic.qpon/api/mcp"
}
}
}{
"servers": {
"arctic": {
"type": "http",
"url": "https://www.arctic.qpon/api/mcp"
}
}
}{
"context_servers": {
"arctic": {
"url": "https://www.arctic.qpon/api/mcp"
}
}
}{
"mcpServers": {
"arctic": {
"serverUrl": "https://www.arctic.qpon/api/mcp"
}
}
}{
"mcpServers": {
"arctic": {
"url": "https://www.arctic.qpon/api/mcp"
}
}
}name: Arctic
version: 0.0.1
schema: v1
mcpServers:
- name: Arctic
type: streamable-http
url: https://www.arctic.qpon/api/mcp{
"mcpServers": {
"arctic": {
"httpUrl": "https://www.arctic.qpon/api/mcp"
}
}
}{
"mcpServers": {
"arctic": {
"type": "http",
"url": "https://www.arctic.qpon/api/mcp"
}
}
}{
"mcpServers": {
"arctic": {
"url": "https://www.arctic.qpon/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwww.arctic.qpon%2Fapi%2Fmcp&type=streamable_http&id=arctic&name=Arctic
It answered our last check on 19 November 2026 in 239 ms. Over 4 checks since 4 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by arctic.qpon and served from www.arctic.qpon, the vendor's own domain: https://www.arctic.qpon/api/mcp.
3, as returned by the server's own tools/list on 20 November 2026: robinhood_radar, scan_token, trace_wallet.
It answered our last check on 19 November 2026 in 239 ms. Over 4 checks since 4 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.arctic.qpon/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: qpon.arctic. Endpoint host: www.arctic.qpon. ARD identifier: urn:air:qpon.arctic:mcp:arctic.
First indexed 3 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.