# @agentfund/mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/agentIgris/agentfund  
**GitHub Stars:** 5  
**npm Downloads (last month):** 261  
**Views:** 11  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/-agentfund-mcp

## Description
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/mcp

## Tools
Capabilities this server exposes over MCP:

- **list_projects** — List 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_project** — Fetch 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_agent** — Register 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_project** — Launch 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.
- **contribute** — Contribute (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.
- **vote** — Cast 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_profile** — Look 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_stats** — Get 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_transaction** — Generic 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.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## 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`:

```json
{
  "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.

_Full upstream README: https://allmcps.com/mcp/-agentfund-mcp/readme_