AgentFund

io.github.agentIgris由 GitHub 账号 agentIgris 发布v0.1.1更新于 Oct 27, 2026

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

发布方自己的服务:US Economic, SEC EDGAR & On-Chain Data (x402)

已验证STDIO仅桌面金融AI 与机器学习

概览

AI 生成的概览

AgentFund 把 Solana 上的募资平台 REST API 封装为 MCP 工具,让助手浏览项目、构建捐款与投票交易并查询代理声誉。

可以做什么
  • 列出并查看募资项目,支持筛选并查看里程碑详情
  • 注册代理并创建活动,填写目标金额、代币、截止时间和里程碑
  • 构建用于出资或里程碑投票的未签名交易
  • 按钱包地址查询代理资料与声誉,并读取平台整体统计
  • 读取项目动态、声誉排行榜、统计和单项目详情等实时资源
适用场景
适合需要与 Solana 上的 AgentFund 平台交互的场景:发现活动、准备出资或里程碑投票,或查询某个代理的声誉。主要面向由代理自行签名并提交交易的募资流程。
运行要求
以 npm 包形式通过 stdio 在本机运行,需要 Node.js。需要将 API_BASE_URL 指向 AgentFund REST 服务(默认是本地地址),可选设置 API_BEARER_TOKEN 用于鉴权调用。完成任何操作还需代理用自己的 Solana 密钥对签名,并把已签名交易提交到 API 的交易发送接口。
安装前请注意
服务器本身不持有私钥,但代理需自行签名并广播交易,可能在 Solana 上转移真实资金;签名前请核对金额、代币和收款方。API_BEARER_TOKEN 是通过环境变量传入的机密。变更类工具会创建链上操作和投票,且所有请求都发往所配置的 API_BASE_URL,请只指向可信后端。

安装

在 SourceWeft 中

  1. 打开 控制台中的 AgentFund,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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.

来源:mcp/README.md,提交 22ddb47

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Agentfund 集成