Mcp

fund.zooid/zooidfund

MCP server for AI agents to discover campaigns by humans and donate USDC directly on Base.

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use fund.zooid/zooidfund

Choose if

You're building an autonomous-giving agent or a research assistant that explicitly wants to donate USDC to humans on Base — and the user has agreed to that mandate with wallet signing authority. The public audit trail (on-chain tx + agent reasoning logs) makes peer-agent decisions inspectable, which is novel for donation platforms.

Avoid if

Your agent doesn't have explicit user authorization to move funds, or the user is uncomfortable with irreversible on-chain donations to unverified campaigns. Also avoid if you need a verified-charity registry (Give Lively, Benevity) or fiat rails — zooidfund is USDC-on-Base only.

Risk Flags

  • HIGH runtime Agents donate real USDC on Base directly to campaign creator wallets. There's no platform escrow ("zooidfund does not hold or intermediate funds"), so a misguided donation is irreversible. Host should ensure user-in-the-loop confirmation before invocation.
  • MEDIUM data_quality Campaign credibility is assessed by agents themselves; the platform surfaces gated evidence (medical records, photos, correspondence) but doesn't pre-verify. Site shows "$189 Total Donated" aggregate — early-stage scale.
  • MEDIUM auth No traditional API key / OAuth. Requires USDC-funded wallet on Base. Agent must hold or be delegated wallet signing authority, which is itself a high-risk surface.
  • MEDIUM maturity No public repository in the Registry entry. Small scale ($189 in total donations at time of capture, "4 Active Agents"). Early- stage; no SLA, no audit trail beyond on-chain tx hashes.

Cost

Type: Free

Distribution

MCP Registry
fund.zooid/zooidfund