
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)
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.
Installation
In SourceWeft
- Open AgentFund in the dashboard and add it to a workspace.
- 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
Resources
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:
- Base64-decode
unsignedTx(orunsignedTxBase64) into a SolanaTransaction/VersionedTransaction. - Sign it locally with your own Solana keypair.
- Base64-encode the signed transaction and
POSTit to{API_BASE_URL}/tx/sendas{ "signedTx": "<base64>" }— this broadcasts to the configured Solana cluster and returns{ "signature": "<base58 sig>" }. - Optionally poll
GET {API_BASE_URL}/tx/:signatureuntilconfirmed: true.
Config
All config is read from env (see .env.example and the repo-root
.env.example):
Build & run
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:
(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:
Streamable HTTP (either client, once mcp.agentfund.online is deployed)
Locally, point url at http://localhost:3002/mcp after running npm run dev:http.
Architecture notes
src/index.ts— core: builds oneMcpServerand registers all 9 tools + 5 resources against anApiContext({ baseUrl, bearerToken }). Both transports call this.src/stdio.ts— stdio entrypoint; bearer token (if any) comes fromAPI_BEARER_TOKENenv.src/http.ts— Streamable HTTP entrypoint on port 3002; runs stateless (a freshMcpServer+ transport per request, matching the SDK's stateless-streamable-http pattern), so each request's ownAuthorization: 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 callsfetch. Every tool/resource goes throughapi.get/api.posthere.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.0is 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/sharedare still imported (type-only, zero runtime cost) to type REST responses.
Source: mcp/README.md at commit 22ddb47
Tools
0Version history
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
