@agentfund MCP vs E Arveldaja MCP

A side-by-side look at the @agentfund MCP and E Arveldaja MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

@agentfund MCP logo@agentfund MCPFinance & Fintech · Local subprocess (stdio)Fundraising infrastructure for AI agents on Solana — campaigns, x402 donations, and on-chain reputation. MCP tools for registering agents, creating campaigns, and donating via the x402 pay-to-call flow, backed by Anchor programs (agentregistry, escrow, reputation). npx -y @agentfund/mcp63GoodAuth: otherE Arveldaja MCP logoE Arveldaja MCPFinance & Fintech · Local subprocess (stdio)MCP server for the Estonian e-arveldaja (RIK e-Financials) accounting API.67GreatAuth: not declared

Verdict: choose @agentfund MCP for finance & fintech work as a local process; choose E Arveldaja 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?

@agentfund MCP logoChoose @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.
Explore @agentfund MCP

E Arveldaja MCP logoChoose E Arveldaja MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_setup_instructions, get_server_status, import_apikey_credentials.
Explore E Arveldaja MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec@agentfund MCP logo@agentfund MCPE Arveldaja MCP logoE Arveldaja MCP
CategoryFinance & FintechFinance & Fintech
Quality signal63/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthotherNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars539
Directory activity 11 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools9130

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.
  • contributeContribute (donate) SOL or USDC to an existing AgentFund project — transfers from the calling agent's wallet into the project's escrow PDA once signed and sent. Use this after finding a project via list_projects/get_project that an agent wants to fund. 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/contribute.
  • voteCast a vote (support or oppose) on whether a specific project milestone should release its escrowed funds to the creator. Use this after reviewing a project's milestone proof via get_project. One vote per agent wallet per milestone. 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/vote.
  • get_agent_profileLook up an AgentFund agent's profile by Solana wallet address: reputation score, projects created, total contributed, and history. Use this to vet a project creator or a fellow contributor before contributing or voting. Read-only, backed by GET /agents/:pubkey.
  • get_platform_statsGet live AgentFund platform-wide stats: total raised, active project count, registered agent count, and total transaction count. Use this for a quick pulse check on the platform, e.g. before deciding whether to launch a new campaign. Read-only, no input required, backed by GET /stats.
  • build_transactionGeneric escape hatch for building an unsigned Solana transaction for any AgentFund action (e.g. 'create_project', 'contribute', 'vote', 'release_milestone', 'refund') when you need direct control over the exact action name and params, rather than using the dedicated create_project/contribute/vote tools. 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/:action.

E Arveldaja MCP tools 130

  • get_setup_instructionsShow how to configure e-arveldaja API credentials when the server is running without connections.
  • get_server_statusReport the running e-arveldaja MCP server version, the active tool profile, and any active point-of-use release notices. Read-only; needs no credentials.
  • import_apikey_credentialsPreview and persist apikey*.txt credentials into local/global .env. Preview-first: the default call verifies and projects the target and returns a plan_handle; call again with execute=true and that handle to persist. overwrite=false appends different credentials as another connection.
  • list_stored_credentialsInspect credentials stored in local/global .env files.
  • remove_stored_credentialsPreview and remove one stored credential block from a local/global .env file. Preview-first: the default call projects the removal and returns a plan_handle; call again with execute=true and that handle to delete.
  • list_connectionsList configured e-arveldaja connections and the active index.
  • switch_connectionSwitch active e-arveldaja connection. Clears caches; interrupted in-flight tools are blocked from further API requests.
  • clear_cacheClear cached e-arveldaja API and reference data. Use after changing data directly in the e-arveldaja web UI, or before reports that must reflect the latest upstream state.
  • get_session_logRetrieve mutating-operation audit log Markdown for the current connection, another audit-log label, or connection:<raw name>.
  • list_audit_logsList available human-readable audit log files.
  • clear_session_logClear the audit log for the current connection. DESTRUCTIVE — cannot be undone.
  • list_clientsList clients. Paginated. Brief view by default; use view='full' or get_client for detail.
  • +118 more on the listing page

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "-agentfund-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentfund/mcp"
      ]
    }
  }
}

E Arveldaja MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "e-arveldaja-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "e-arveldaja-mcp"
      ]
    }
  }
}

Frequently asked questions

@agentfund MCP is categorized under Finance & Fintech and uses a local stdio subprocess. E Arveldaja MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick @agentfund MCP for finance & fintech work and E Arveldaja 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.

@agentfund MCP is listed as free. Auth: other. E Arveldaja MCP has no declared pricing — check the project's own site. 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 e-arveldaja-mcp 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 11 views, 0 installs and 5 GitHub stars. E Arveldaja MCP has 67/100 (Great) with 2 views, 0 installs and 39 GitHub stars.