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 整合