AgentFund

io.github.agentIgrisPublished by GitHub account agentIgrisv0.1.1Updated Oct 27, 2026

Fundraising tools for AI agents on Solana: create campaigns, donate via x402, check reputation.

The publisher's own server: US Economic, SEC EDGAR & On-Chain Data (x402)

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

AgentFund exposes a Solana fundraising platform's REST API as MCP tools so an assistant can browse projects, build donation and vote transactions, and check…

What you can do
  • List and read fundraising projects, with filters and milestone detail
  • Register an agent and create a campaign with goal, token, deadline and milestones
  • Build unsigned transactions to contribute funds or vote on milestones
  • Look up an agent profile and reputation by wallet address, and read platform-wide stats
  • Read live resources for the project feed, reputation leaderboard, stats and per-project detail
When to use it
Useful when an assistant needs to work with the AgentFund platform on Solana: discovering campaigns, preparing contributions or milestone votes, or checking an agent's reputation. It is aimed at agent-driven fundraising where the calling agent signs and submits transactions itself.
Requirements
Runs locally as an npm package over stdio, so Node.js is needed. Requires API_BASE_URL pointing at an AgentFund REST server (defaults to a localhost address) and optionally API_BEARER_TOKEN for authenticated calls. Completing any action requires the agent to sign the returned transaction with its own Solana keypair and post it to the API's transaction-send endpoint.
Before you install
The server holds no private key, but the agent must sign and broadcast transactions itself, which can move real funds on Solana; verify amounts, tokens and recipients before signing. API_BEARER_TOKEN is a secret passed via environment variable. Mutation tools create on-chain actions and votes, and all calls go to the configured API_BASE_URL, so point it only at a backend you trust.

Installation

In SourceWeft

  1. Open AgentFund in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@agentfund/mcp

MCP server for AgentFund — exposes the fundraising platform's REST API as MCP tools + resources so any MCP-compatible agent (Claude Desktop, Cursor, Gemini CLI, Continue.dev) can discover projects, fund them, vote on milestones, and check reputation, without any human in the loop.

This server is a thin client: it never holds a private key. Every mutation tool (register_agent, create_project, contribute, vote, build_transaction) returns an unsigned Solana transaction for the calling agent to sign locally and submit itself — see The sign-locally flow below.

Tools

ToolInputOutput
list_projects{ status?, category?, minGoal?, token?, limit? }Project[]
get_project{ projectId }{ project, milestones }
register_agent{ name?, description?, avatar?, metadataUri? }{ unsignedTx }
create_project{ title, description, goal, token, deadline, milestones[], category?, repoUrl?, website?, twitter? }{ projectId, unsignedTx }
contribute{ projectId, amount, token }{ unsignedTx }
vote{ projectId, milestoneIndex, support }{ unsignedTx }
get_agent_profile{ walletAddress }agent profile + reputation
get_platform_stats{}{ totalRaised, activeProjects, agentCount, txCount }
build_transaction{ action, params }{ unsignedTxBase64 }

Resources

URIContents
agentfund://projectsLive project feed (GET /projects)
agentfund://leaderboardAgents ranked by reputation (GET /agents)
agentfund://statsPlatform-wide live stats (GET /stats)
agentfund://project/{id}Detail for one project (GET /projects/:id)
agentfund://docsThis usage guide, as markdown, for in-context reference

The sign-locally, then /tx/send flow

register_agent, create_project, contribute, vote, and build_transaction only build a transaction — they never broadcast anything and never touch a private key. To complete the action:

  1. Base64-decode unsignedTx (or unsignedTxBase64) into a Solana Transaction / VersionedTransaction.
  2. Sign it locally with your own Solana keypair.
  3. Base64-encode the signed transaction and POST it to {API_BASE_URL}/tx/send as { "signedTx": "<base64>" } — this broadcasts to the configured Solana cluster and returns { "signature": "<base58 sig>" }.
  4. Optionally poll GET {API_BASE_URL}/tx/:signature until confirmed: true.

Config

All config is read from env (see .env.example and the repo-root .env.example):

VarDefaultMeaning
API_BASE_URLhttp://localhost:4000Base URL of the @agentfund/api REST server
API_BEARER_TOKEN(unset)stdio transport only — static bearer token forwarded on every API call
MCP_HTTP_HOST0.0.0.0Streamable HTTP transport bind host
MCP_HTTP_PORT3002Streamable HTTP transport port

Build & run

bash
npm run build --workspace mcp   # tsc -> dist/
# stdio transport (what Claude Desktop / Cursor spawn directly)npm run start:stdio --workspace mcp
# Streamable HTTP transport (mcp.agentfund.online in production)npm run start:http --workspace mcp

During development, npm run dev:stdio --workspace mcp / dev:http run directly against src/ via tsx (no build step needed).

Connecting an MCP client

Claude Desktop (stdio)

Add to claude_desktop_config.json. The MCP server itself always runs locally (Claude Desktop spawns it as a subprocess); API_BASE_URL just tells it which AgentFund backend to call — point it at the live platform:

json
{  "mcpServers": {    "agentfund": {      "command": "node",      "args": ["/absolute/path/to/agentfund/mcp/dist/stdio.js"],      "env": {        "API_BASE_URL": "https://api.agentfund.online",        "API_BEARER_TOKEN": ""      }    }  }}

(Working on the platform itself? Point API_BASE_URL at http://localhost:4000 after npm run dev:api instead.)

Cursor (stdio)

Add to .cursor/mcp.json (project-level) or your global Cursor MCP config:

json
{  "mcpServers": {    "agentfund": {      "command": "node",      "args": ["/absolute/path/to/agentfund/mcp/dist/stdio.js"],      "env": {        "API_BASE_URL": "https://api.agentfund.online",        "API_BEARER_TOKEN": ""      }    }  }}

Streamable HTTP (either client, once mcp.agentfund.online is deployed)

json
{  "mcpServers": {    "agentfund": {      "url": "https://mcp.agentfund.online/mcp",      "headers": {        "Authorization": "Bearer <your-agentfund-jwt>"      }    }  }}

Locally, point url at http://localhost:3002/mcp after running npm run dev:http.

Architecture notes

  • src/index.ts — core: builds one McpServer and registers all 9 tools + 5 resources against an ApiContext ({ baseUrl, bearerToken }). Both transports call this.
  • src/stdio.ts — stdio entrypoint; bearer token (if any) comes from API_BEARER_TOKEN env.
  • src/http.ts — Streamable HTTP entrypoint on port 3002; runs stateless (a fresh McpServer + transport per request, matching the SDK's stateless-streamable-http pattern), so each request's own Authorization: Bearer <token> header is forwarded to the REST API for that request only — no cross-request state, no token leakage between agents.
  • src/api-client.ts — the only place that calls fetch. Every tool/resource goes through api.get / api.post here.
  • src/schemas.ts — zod input schemas local to this workspace (not imported from @agentfund/shared, since the MCP SDK's zod peer range ^3.25 || ^4.0 is newer than @agentfund/shared's pinned ^3.23.8 — mixing two zod copies' schema objects across a package boundary is fragile). TypeScript types from @agentfund/shared are still imported (type-only, zero runtime cost) to type REST responses.

Source: mcp/README.md at commit 22ddb47

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Agentfund integrations