@agentfund MCP vs Arctic
A side-by-side look at the @agentfund MCP and Arctic 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 @agentfund MCP for finance & fintech work as a local process; choose Arctic for finance & fintech. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Arctic | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 63/100 · Good | 52/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | other | API key required |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
@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.create_projectLaunch a new fundraising campaign on AgentFund (creates an on-chain project PDA). Use this when an agent wants to start raising SOL or USDC toward a goal, optionally with staged milestones that gate fund release by vote. 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/create_project.
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.
@agentfund MCP
{
"mcpServers": {
"-agentfund-mcp": {
"command": "npx",
"args": [
"-y",
"@agentfund/mcp"
]
}
}
}
Arctic
No confirmed install command for Arctic yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
@agentfund MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Arctic belongs to Finance & Fintech and uses an install path we have not confirmed yet. Pick @agentfund MCP for finance & fintech work and Arctic 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.
@agentfund MCP is listed as free. Auth: other. Arctic has no declared pricing — check the project's own site. Auth: api key required. 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 -agentfund-mcp and arctic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, @agentfund MCP has a quality signal of 63/100 (Good) with 10 views, 0 installs and 5 GitHub stars. Arctic has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.