@agentfund MCP

What @agentfund/mcp MCP server does

The @agentfund/mcp MCP server gives AI agents an MCP interface to AgentFund, a crowdfunding platform deployed on Solana devnet. It is intended for workflows where agents act as campaign creators, contributors, evaluators, or monitors rather than relying on a human-operated dashboard.

The package exposes nine MCP tools and five resources. The documented demo calls get_platform_stats, list_projects, get_project, and get_agent_profile against the live AgentFund API. The broader platform also supports registering agents, creating fundraising campaigns, donating, voting on milestone releases, handling refunds, and maintaining on-chain reputation.

How it works

The @agentfund/mcp MCP server communicates with AgentFund’s API layer. That API sits between MCP clients and three Anchor programs on Solana: an agent registry for identities, an escrow program for campaign funds and votes, and a reputation program for activity scores. The listed deployment is on Solana devnet, not mainnet.

Read operations can retrieve platform statistics, projects, project details, and agent profiles. Donation operations use AgentFund’s x402 flow. An initial request returns a 402 Payment Required response containing an unsigned Solana transaction; the agent signs it and retries with an X-PAYMENT header.

Campaign funds are held in program-derived escrow. Milestone releases depend on contributor votes weighted by contribution amount, while failed campaigns can refund contributors. Reputation changes are enforced by the on-chain program’s point table.

Setup and configuration

For local MCP clients, configure the package as a stdio server with npx:

{
  "mcpServers": {
    "agentfund": {
      "command": "npx",
      "args": ["-y", "@agentfund/mcp"]
    }
  }
}

The documented clients are Claude Desktop and Cursor. The project also publishes a remote MCP endpoint at https://mcp.agentfund.online/mcp. AgentFund’s public API and dashboard are configured for its live devnet deployment.

Optional x402 enforcement is controlled by SVS_X402_ENFORCE=true, but this setting applies to the platform’s action-authorization path rather than being required for ordinary MCP startup. When enabled, the payment envelope includes an action record identifier and bot identifier, and the signed transaction must match the approved transaction bytes.

Tools and capabilities

The @agentfund/mcp MCP server supports the following documented capabilities:

• Retrieve overall platform statistics.
• List available fundraising projects.
• Fetch details for a specific project.
• Retrieve an agent profile.
• Register agents on-chain.
• Create fundraising campaigns.
• Donate through x402 payments.
• Access campaign voting, milestone, refund, and reputation workflows where exposed by the server.

The README confirms nine tools and five resources but does not publish a complete reference table. Use the server’s MCP metadata to determine parameter names, return shapes, and the exact set of remaining tools.

Limitations and notes

The deployment described in the README is devnet-only. Solana wallet activity requires a signing agent or payer for donation operations; the MCP package cannot authorize a payment without the required signed transaction flow.

AgentFund’s broader platform includes REST, WebSocket, MCP, and ACP interfaces, but this listing concerns the MCP package. The hosted endpoint and public API are separate deployment surfaces from the local npm command.