About arctic
arctic is a hosted MCP server for reading live Robinhood Chain token and wallet data. It helps users inspect token metrics, trace deployers and discover recent or heavily traded launches without installing software.
Key features
- 01Read token supply, ownership and market metrics
- 02Trace a token's deploying wallet
- 03List recent token launches
- 04Find tokens trending by 24-hour trading
Use cases
- 01Review a token's liquidity and volume
- 02Check a deployer's launch and trading history
- 03Find newly launched or actively traded tokens
MCP support
Exposes three read tools to MCP clients through a hosted endpoint: token scanning, wallet tracing and launch discovery. Requests use a bearer key and count against the key's daily allowance.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://www.arctic.qpon/api/mcpclaude mcp add --transport http qpon-arctic-arctic https://www.arctic.qpon/api/mcp{"mcpServers":{"qpon-arctic-arctic":{"type":"http","url":"https://www.arctic.qpon/api/mcp"}}}Open in Cursor{"servers":{"qpon-arctic-arctic":{"type":"http","url":"https://www.arctic.qpon/api/mcp"}}}Open in VS Code{"mcpServers":{"qpon-arctic-arctic":{"type":"http","url":"https://www.arctic.qpon/api/mcp"}}}{"mcpServers":{"qpon-arctic-arctic":{"serverUrl":"https://www.arctic.qpon/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://www.arctic.qpon/api/mcpAuth requiredTools
3| Parameter | Type | Required | Description |
|---|---|---|---|
| address | string | Yes | The token contract address: 0x followed by 40 hex characters. |
Details
From the project READMEArctic · MCP server
Read Robinhood Chain live from any MCP client: scan a token onchain, trace the wallet that launched it, and list what just launched or is most traded.
The server is hosted — there is nothing to install and nothing to run on your machine.
https://www.arctic.qpon/api/mcp
Published in the official registry as qpon.arctic/arctic.
Add it
Claude Code
claude mcp add --transport http arctic https://www.arctic.qpon/api/mcp \
--header "Authorization: Bearer arc_live_…"
Claude Desktop, Cursor, VS Code
{
"mcpServers": {
"arctic": {
"type": "http",
"url": "https://www.arctic.qpon/api/mcp",
"headers": { "Authorization": "Bearer arc_live_…" }
}
}
}
A key is free: sign in with a wallet at https://www.arctic.qpon/console and create one. It can be rotated or revoked at any time, and Arctic stores only a hash of it.
Tools
| Tool | What it reads |
|---|---|
scan_token | One token: supply, owner powers, Pons v2 launch and graduation, creator tax, price, liquidity, 24h volume, deployer share, burned share. |
trace_wallet | The wallet behind a token: what it launched, how much graduated, and whether it bought or sold on its own curves. |
robinhood_radar | new for the latest launches, trending for the most traded over 24 hours. |
What it costs
Nothing. A tools/call spends one request from the daily allowance of the wallet behind
your key — 200 a day signed in, 1,000 for a holder of $ARCTIC, 4,000 for a guardian.
There is no card anywhere on Arctic: it runs on the free tiers of several model hosts,
and the chain is read directly.
Honest notes
- Numbers come from the Pons v2 factory's own events and from the pairs themselves, read at call time. They describe behaviour, not intent, and are not financial advice.
- The shared daily pool can run out. When it is nearly spent, what is left is held for wallets holding $ARCTIC; everyone else waits for midnight UTC.
- A GET on the endpoint describes the server without a key, so you can check it before wiring anything up.
Links
- Install page: https://www.arctic.qpon/mcp
- Manifest: https://www.arctic.qpon/server.json
- Docs: https://www.arctic.qpon/docs?guide=mcp
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.