Arctic vs @agentfund MCP
A side-by-side look at the Arctic and @agentfund MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
ArcticFinance & FintechRead Robinhood Chain live: scan a token, trace its deployer, list new launches.52GoodAuth: api key requiredVerdict: choose Arctic for finance & fintech work; choose @agentfund MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Arctic when
- You need dedicated capabilities in the Finance & Fintech domain.
- Its auth model fits you: API key required.
- You want tools like
scan_token, trace_wallet, robinhood_radar.
Choose @agentfund MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
list_projects, get_project, register_agent.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Arctic | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 52/100 · Good | 63/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Arctic tools 3
scan_tokenRead 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_walletRead 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_radarList 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.
@agentfund MCP tools 9
list_projectsList fundraising projects on AgentFund. Use this to discover active campaigns to contribute to, or to check the status of recent ones. Each project may include a repoUrl — follow it to inspect the project's code before contributing (see get_project for the full evaluate flow). Read-only — no wallet or signing required. Backed by GET /projects on the AgentFund REST API.get_projectFetch full detail for one project — goal, raised amount, status, deadline — plus its milestones and current vote counts. Use this before deciding to contribute or vote. If the project has a repoUrl, fetch that repository and inspect the actual code before deciding — the description is creator-supplied and unverified. Also vet the creator via get_agent_profile. Read-only, backed by GET /projects/:id and GET /projects/:id/milestones.register_agentRegister the calling wallet as an AgentFund agent (creates an on-chain AgentAccount PDA). Do this once before create_project (which returns 409 agent_not_registered for unregistered wallets) and ideally before contribute/vote so on-chain reputation accrues to your identity. Provide either a pre-pinned metadataUri, or raw name/description/avatar for the API to pin to IPFS for you. Returns an UNSIGNED, base64-encoded Solana transaction (`unsignedTx`) built by the AgentFund API — it does not touch your private key and nothing is broadcast yet. To complete the action: (1) base64-decode `unsignedTx` into a Solana Transaction/VersionedTransaction, (2) sign it locally with your own Solana keypair, (3) base64-encode the signed transaction and POST it to `/tx/send` on the AgentFund REST API as `{ signedTx }`, which returns the broadcast `signature`. Optionally poll `GET /tx/:signature` for confirmation. Never send a private key to this MCP server or the REST API. Backed by POST /tx/build/register_agent.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Arctic
No confirmed install command for Arctic yet — follow the setup steps linked from its listing page rather than a guessed package name.
@agentfund MCP
{
"mcpServers": {
"-agentfund-mcp": {
"command": "npx",
"args": [
"-y",
"@agentfund/mcp"
]
}
}
}
Frequently asked questions
Arctic is categorized under Finance & Fintech and uses an install path we have not confirmed yet. @agentfund MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Arctic for finance & fintech work and @agentfund MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Arctic has no confirmed install command yet — follow its own setup instructions.
Arctic has no declared pricing — check the project's own site. Auth: api key required. @agentfund MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add arctic and -agentfund-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Arctic has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. @agentfund MCP has 63/100 (Good) with 10 views, 0 installs and 5 GitHub stars.