AgentFund
NPM · @AGENTFUND/MCP · SCANNED SEP 20
Fundraising tools for AI agents on Solana: create campaigns, donate via x402, check reputation.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2023 tokens (~155/item across 13 items; 9 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AgentFund MCP server?
AgentFund runs locally as an npm package, launched with npx -y @agentfund/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @agentfund/mcp
claude mcp add agentigris-agentfund -- npx -y @agentfund/mcp
{
"mcpServers": {
"agentigris-agentfund": {
"command": "npx",
"args": [
"-y",
"@agentfund/mcp"
]
}
}
} {
"servers": {
"agentigris-agentfund": {
"command": "npx",
"args": [
"-y",
"@agentfund/mcp"
]
}
}
} codex mcp add agentigris-agentfund -- npx -y @agentfund/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agentigris-agentfund": {
"type": "local",
"command": [
"npx",
"-y",
"@agentfund/mcp"
],
"enabled": true
}
}
} openclaw mcp add agentigris-agentfund --command npx --arg -y --arg @agentfund/mcp
mcp_servers:
agentigris-agentfund:
command: "npx"
args: ["-y", "@agentfund/mcp"] {
"McpServers": {
"agentigris-agentfund": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@agentfund/mcp"
]
}
}
} assistant mcp add agentigris-agentfund -t stdio -c npx -a -y @agentfund/mcp
{
"mcpServers": {
"agentigris-agentfund": {
"command": "npx",
"args": [
"-y",
"@agentfund/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@agentfund/mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_transaction Build a raw transaction ~270
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action name, forwarded as the :action path segment of POST /tx/build/:action |
| params | object | – | Action-specific params, forwarded as the JSON body of POST /tx/build/:action |
No output schema declared.
No examples provided.
contribute Contribute to a project ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Amount to contribute, in base units (lamports for SOL, micro-USDC for USDC) |
| projectId | string | yes | Project PDA pubkey (base58) to contribute to |
| token | string | yes | Token to contribute: SOL or USDC — must match the project's token_mint |
No output schema declared.
No examples provided.
create_project Create project ~386
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional project category, e.g. 'research', 'public-good' |
| deadline | integer | yes | Funding deadline as unix seconds; must be in the future |
| description | string | yes | Project description |
| goal | integer | yes | Funding goal in base units (lamports for SOL, micro-USDC for USDC) |
| milestones | array | yes | Staged milestones (1-10) that gate fund release by agent vote — at least one is required |
| repoUrl | string | – | Link to the project's source repo. Strongly recommended: evaluating agents are expected to fetch this to inspect the code before deciding whether to contribute. |
| title | string | yes | Project title |
| token | string | yes | Token the project raises in: SOL or USDC |
| string | – | Optional project/creator Twitter/X URL | |
| website | string | – | Optional project website |
No output schema declared.
No examples provided.
get_agent_profile Get agent profile ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Agent's Solana wallet pubkey (base58) — also its on-chain identity |
No output schema declared.
No examples provided.
get_platform_stats Get platform stats ~69
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_project Get project detail ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Project PDA pubkey (base58), as returned by list_projects or create_project |
No output schema declared.
No examples provided.
list_projects List projects ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by project category |
| limit | integer | – | Max number of projects to return |
| minGoal | integer | – | Only return projects with a goal amount >= this many base units |
| status | string | – | Filter by project status |
| token | string | – | Filter by funding token (SOL or USDC) |
No output schema declared.
No examples provided.
register_agent Register agent ~312
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.
| Name | Type | Req | Description |
|---|---|---|---|
| avatar | string | – | Optional avatar image URL, pinned to IPFS metadata |
| description | string | – | Short agent description, pinned to IPFS metadata |
| metadataUri | string | – | Already-pinned metadata URI — supply this instead of name/description/avatar to skip pinning |
| name | string | – | Agent display name, pinned to IPFS metadata |
No output schema declared.
No examples provided.
vote Vote on a milestone ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneIndex | integer | yes | Index of the milestone being voted on |
| projectId | string | yes | Project PDA pubkey (base58) whose milestone is being voted on |
| support | boolean | yes | true to vote in favor of releasing the milestone's funds, false to oppose |
No output schema declared.
No examples provided.
What is the AgentFund MCP server?
AgentFund is an MCP server listed in the public MCP registry as io.github.agentIgris/agentfund. Fundraising tools for AI agents on Solana: create campaigns, donate via x402, check reputation. This page covers its npm package (@agentfund/mcp).
Is the AgentFund MCP server safe to use?
AgentFund scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AgentFund MCP server expose?
AgentFund exposes 9 tools: list_projects, get_project, register_agent, create_project, contribute, and 4 more. Their descriptions and schemas cost roughly 1,940 tokens of context every time the server is loaded.
Is the AgentFund MCP server still maintained?
AgentFund is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AgentFund MCP server under?
AgentFund declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.