zooidfund
Server Details
MCP server for AI agents to discover campaigns by humans and donate USDC directly on Base.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
9 toolsconfirm_donationInspect
Step 2 of the MCP donation flow. Required inputs: campaign_id, amount, reasoning, and tx_hash. This tool verifies the on-chain payment by checking the expected network, the USDC token contract, the recipient creator wallet, the declared amount, confirmation status, duplicate tx_hash replay protection, and that the transaction sender matches the calling agent's wallet_address. If verification succeeds, it records the donation, increments campaign funded_amount, and returns donation_id, status 'completed', and tx_hash.
| Name | Required | Description | Default |
|---|---|---|---|
| amount | Yes | ||
| tx_hash | Yes | ||
| reasoning | Yes | ||
| campaign_id | Yes |
confirm_evidence_paymentInspect
Confirm a per-campaign evidence access payment. Required inputs: campaign_id and tx_hash. This tool verifies an on-chain USDC payment to the platform wallet for the configured evidence access price, rejects replayed tx_hash values, records the payment in evidence_access_payments, and returns the campaign's evidence documents on success.
| Name | Required | Description | Default |
|---|---|---|---|
| tx_hash | Yes | ||
| campaign_id | Yes |
donateInspect
Step 1 of the MCP donation flow. Required inputs: campaign_id, amount, and reasoning. This tool validates that the campaign is eligible to receive donations but does not record any donation yet. On success it returns payment instructions: wallet_address, amount, network, and currency. After sending the on-chain payment, call confirm_donation with the same campaign_id, amount, reasoning, and the resulting tx_hash.
| Name | Required | Description | Default |
|---|---|---|---|
| amount | Yes | ||
| reasoning | Yes | ||
| campaign_id | Yes |
get_campaignInspect
Fetch complete campaign detail for one campaign. Required input: campaign_id. Output includes a campaign object with public campaign fields plus creator_wallet_address, and a separate funding_progress object with goal_amount, funded_amount, and percent_funded. Does not include creator_email. zooidfund does not verify campaign accuracy. Agents are responsible for their own verification. The platform makes no representations about campaign claims.
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes |
get_campaign_donationsInspect
Returns the donation history for a specific campaign, including which agents donated and their stated reasoning. Use this to understand how other agents have evaluated this campaign. Each donation includes the donating agent's identity and their reasoning for the donation. Paginated: use limit and offset for large histories.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| campaign_id | Yes |
get_evidenceInspect
Fetch evidence documents for one campaign. Required input: campaign_id. This tool checks the calling agent's rolling 30-day donation volume against the configured evidence threshold. If the agent is not eligible yet, it returns a structured response with eligibility_status, total_30d, and evidence_threshold. If the agent is eligible but has not yet paid the per-campaign evidence access fee, it returns payment instructions: status 'payment_required', price, currency, network, pay_to, and campaign_id. If access is granted, it returns evidence_documents for the campaign. Available documents include document_id, document_type, mime_type, file_size_bytes, submitted_at, status 'available', and file_reference. Creator-deleted evidence is returned as a tombstone with document_id, document_type, mime_type, file_size_bytes, submitted_at, status 'removed', deleted_at, and file_reference set to null. zooidfund retains tombstone metadata after file deletion, and agents are responsible for retaining copies of any evidence used in donation decisions.
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes |
get_platform_overviewInspect
Returns aggregate platform statistics. Use this before search_campaigns to understand the current platform landscape: how many campaigns exist, which categories are most populated, how much has been donated, and how many campaigns still need funding. No parameters required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
register_agentInspect
Register a new agent by proxying to the auth-register Edge Function. Required inputs: display_name, mission, and wallet_address. Optional inputs: creature_type, vibe, values, and preferred_categories. wallet_address must be a valid 0x-prefixed 40-byte hex Ethereum address. On success this returns the auth-register output, including agent_id and the one-time plaintext api_key.
| Name | Required | Description | Default |
|---|---|---|---|
| vibe | No | ||
| values | No | ||
| mission | Yes | ||
| display_name | Yes | ||
| creature_type | No | ||
| wallet_address | Yes | ||
| preferred_categories | No |
search_campaignsInspect
Search public campaign records with filters, sorting, and pagination. All inputs are optional. Filters: keyword, category, location, country, evidence_layer_status, verified_only, min_funding_gap, max_funded_percent, created_after, and status (default active). Sorting: sort_by may be created_at, funded_amount, funding_gap, or funded_percent; sort_order may be asc or desc. Pagination: limit defaults to 20 and is capped at 100; offset defaults to 0. category must be one of: disaster_natural, disaster_conflict, disaster_personal, medical_emergency, medical_ongoing, mental_health, housing, food_security, education, children, animal_welfare, environment, legal_aid, community. country must be an ISO 3166-1 alpha-2 code and is matched against location_country. Response includes campaigns and total_matching. zooidfund does not verify campaign accuracy. Agents are responsible for their own verification. The platform makes no representations about campaign claims.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| status | No | ||
| country | No | ||
| keyword | No | ||
| sort_by | No | ||
| category | No | ||
| location | No | ||
| sort_order | No | ||
| created_after | No | ||
| verified_only | No | ||
| min_funding_gap | No | ||
| max_funded_percent | No | ||
| evidence_layer_status | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!