# arctic [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/aizennsossuke212/arctic-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/arctic

## Description
Read Robinhood Chain live: scan a token, trace its deployer, list new launches.

## Tools
Capabilities this server exposes over MCP:

- **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 whenever the user mentions a token contract 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 user asks who is behind a token, or about a deployer.
- **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_token to read one in depth.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What arctic does

The arctic MCP server connects MCP clients to live Robinhood Chain data. It focuses on token discovery and investigation rather than transaction execution. Developers can inspect a token contract, examine the wallet that launched it, or browse recent and heavily traded tokens.

For developers evaluating tools in the 💰 Finance & Fintech category, the server provides market and launch information at call time. Returned data can include price, market cap, liquidity, volume, buying and selling activity, launch progress, creator tax, deployer ownership, and burned supply. The data describes observed behavior and is not financial advice.

## How it works

Arctic is hosted at `https://www.arctic.qpon/api/mcp`, so there is no local package or process to install. MCP clients send tool calls over HTTP with a bearer key. A GET request to the endpoint can describe the server without authentication, which allows basic endpoint checking before configuration.

The arctic MCP server reads data from the Pons v2 factory events and token pairs when a call is made. `robinhood_radar` provides discovery modes: `new` returns recent Pons v2 launches, while `trending` returns tokens with the most 24-hour trading activity. After finding a token, an agent can pass its contract address to `scan_token` for a fuller view.

## Setup and configuration

To use the arctic MCP server, create a free key by signing in with a wallet at the Arctic console. The key can be rotated or revoked, and Arctic stores only its hash. Add the hosted endpoint and bearer header to an MCP client.

Claude Code uses an HTTP transport command similar to:

```bash
claude mcp add --transport http arctic https://www.arctic.qpon/api/mcp \\
  --header "Authorization: Bearer arc_live_…"
```

Claude Desktop, Cursor, and VS Code can use an HTTP server entry with the endpoint URL and an `Authorization` header. The published registry identifier is `qpon.arctic/arctic`.

## Tools and capabilities

- `scan_token`: Reads a Robinhood Chain token by contract address, including supply, owner powers, Pons v2 launch and graduation status, creator tax, price, market cap, liquidity, 24-hour volume, buys, sells, deployer share, and burned share. Each key includes its unit.
- `trace_wallet`: Investigates the wallet associated with a token, including recent Pons v2 launches, graduated tokens, tokens still on curves, and activity on its own curves.
- `robinhood_radar`: Lists recent launches or the most traded tokens over 24 hours, with launch age, curve progress, market cap, volume, liquidity, buys, sells, and change where applicable.

## Limitations and notes

The arctic MCP server has a shared daily request allowance. A wallet-signed key receives 200 requests per day, while holders of `$ARCTIC` receive 1,000 and guardians receive 4,000. When the shared pool is nearly exhausted, remaining capacity is reserved for `$ARCTIC` holders until midnight UTC.

The service is read-only in the documented capabilities: its tools report chain and market observations rather than placing trades or changing contracts. Results reflect factory events and pair data available at call time, so they should be treated as activity measurements rather than statements of intent. No payment card is required.

_Full upstream README: https://allmcps.com/mcp/arctic/readme_