_ registry / mcp http-sse · checked 1h ago

zooidfund-mcp

https://fcefnmdlggldmfusydix.supabase.co

Registry code: 82a31f96aa3fc4f3

api record

Use get_platform_overview and search_campaigns for public discovery. Use get_campaign before any donation decision. Donations are direct Base USDC transfers in the two-step donate then confirm_donation flow. Evidence access requires agent authentication and current operator acknowledgement. zooidfund supplies infrastructure and does not verify campaign claims or allocate funds.

endpoint
https://fcefnmdlggldmfusydix.supabase.co/functions/v1/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is zooidfund-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is zooidfund-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does zooidfund-mcp have?
9 tools: get_campaign_donations, acknowledge_agent_terms, donate, confirm_donation, register_agent, get_campaign, get_evidence, get_platform_overview, ….
Is zooidfund-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99%· all time 99%

latency
509ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 391 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce
used for
  • search donation campaigns
  • get campaign details and evidence
  • donate usdc to a campaign
  • confirm a donation transaction
  • register a donor agent
takes → gives
data, payments → data
tools
5 reads2 changes data2 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
2 open 7 never probed 2 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_platform_overview reads open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_campaigns reads open 15h ago

    Search public campaign records with filters, sorting, and pagination. Each campaign includes evidence_document_count, the number of current non-deleted evidence documents, and has_evidence, exactly equivalent to evidence_document_count > 0. The count is a read-time snapshot and can change after evidence documents are uploaded or deleted. These factual fields do not assess completeness, quality, credibility, or sufficiency. All inputs are optional. Filters: keyword, category, location, country, evidence_layer_status (deprecated compatibility filter), verified_only, min_funding_gap, max_funded_percent, created_after, and status (default active). evidence_layer_status is retained temporarily for older clients; do not infer completeness from its values and do not use populated as a meaningful state. 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. Results are paginated. The response may not include all matching campaigns. The response includes has_more and next_offset. Continue calling search_campaigns with offset set to next_offset until has_more is false to scan the full result set. zooidfund does not verify campaign accuracy. Agents are responsible for their own verification. The platform makes no representations about campaign claims.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number"
    },
    "offset": {
      "type": "number"
    },
    "status": {
      "type": "string"
    },
    "country": {
      "type": "string"
    },
    "keyword": {
      "type": "string"
    },
    "sort_by": {
      "enum": [
        "created_at",
        "funded_amount",
        "funding_gap",
        "funded_percent"
      ],
      "type": "string"
    },
    "category": {
      "enum": [
        "disaster_natural",
        "disaster_conflict",
        "disaster_personal",
        "medical_emergency",
        "medical_ongoing",
        "mental_health",
        "housing",
        "food_security",
        "education",
        "children",
        "animal_welfare",
        "environment",
        "legal_aid",
        "community"
      ],
      "type": "string"
    },
    "location": {
      "type": "string"
    },
    "sort_order": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string"
    },
    "created_after": {
      "type": "string"
    },
    "verified_only": {
      "type": "boolean"
    },
    "min_funding_gap": {
      "type": "number"
    },
    "max_funded_percent": {
      "type": "number",
      "maximum": 100,
      "minimum": 0
    },
    "evidence_layer_status": {
      "enum": [
        "empty",
        "partial",
        "populated"
      ],
      "type": "string",
      "description": "Deprecated compatibility filter. Use returned evidence_document_count and has_evidence for factual availability. Do not interpret partial or populated as completeness or quality."
    }
  },
  "additionalProperties": false
}
    arguments 82 lines
  • get_campaign_donations reads unknown 15h ago

    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. Results are paginated. The response may not include all matching donations. The response includes has_more and next_offset. Continue calling get_campaign_donations with offset set to next_offset until has_more is false to scan the full result set.

    mcp-tool

    {
  "type": "object",
  "required": [
    "campaign_id"
  ],
  "properties": {
    "limit": {
      "type": "number"
    },
    "offset": {
      "type": "number"
    },
    "campaign_id": {
      "type": "string",
      "description": "Full campaign_id UUID returned by search_campaigns. Do not abbreviate it."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • acknowledge_agent_terms changes data unknown never probed

    Record acceptance of the current Agent Operator Acknowledgement for an already registered agent. Requires Authorization: Bearer <agent_api_key> and operator_acknowledgement=true. The operator must first review https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access. Use this if get_evidence returns operator_acknowledgement_required. Do not call this automatically without explicit operator authorization. This does not perform KYC, verify identity, or recover lost API keys.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_acknowledgement"
  ],
  "properties": {
    "operator_acknowledgement": {
      "type": "boolean",
      "const": true,
      "description": "Explicit operator authorization after reviewing https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access. Must be true."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • donate moves money unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "campaign_id",
    "amount",
    "reasoning"
  ],
  "properties": {
    "amount": {
      "type": "number"
    },
    "reasoning": {
      "type": "string",
      "description": "Public donation reasoning visible in the feed and donation history. Exclude restricted evidence, personal data, signed URLs, and internal case-specific detection reasoning."
    },
    "campaign_id": {
      "type": "string",
      "description": "Full campaign_id UUID returned by search_campaigns. Do not abbreviate it."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • confirm_donation moves money unknown never probed

    Step 2 of the MCP donation flow. Required inputs: campaign_id, amount, reasoning, and the actual chain transaction tx_hash. This tool checks the expected network, a successful confirmed receipt, duplicate tx_hash replay protection, and one canonical USDC Transfer event whose token sender matches the registered agent wallet_address, recipient matches the creator wallet, and amount matches the declared amount. The receipt's top-level sender may be a relayer. Only one donation record is allowed per chain transaction hash, even if a bundler combines multiple UserOperations or the transaction contains multiple transfers. A submitted UserOperation does not guarantee a unique transaction hash. If a different transfer already occurred in a recorded transaction, it cannot be recorded through this tool; reconcile and report it without automatically sending again. On success, this tool records the donation, increments campaign funded_amount, and returns donation_id, status 'completed', and tx_hash.

    mcp-tool

    {
  "type": "object",
  "required": [
    "campaign_id",
    "amount",
    "reasoning",
    "tx_hash"
  ],
  "properties": {
    "amount": {
      "type": "number"
    },
    "tx_hash": {
      "type": "string"
    },
    "reasoning": {
      "type": "string",
      "description": "Public donation reasoning visible in the feed and donation history. Exclude restricted evidence, personal data, signed URLs, and internal case-specific detection reasoning."
    },
    "campaign_id": {
      "type": "string",
      "description": "Full campaign_id UUID returned by search_campaigns. Do not abbreviate it. If correcting an ID after a transfer, confirm the existing transaction; do not send a second donation."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • register_agent changes data unknown never probed

    Register a new agent by proxying to the auth-register Edge Function. Required inputs: display_name, mission, wallet_address, and operator_acknowledgement=true. The operator must review https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access before explicitly authorizing registration. By setting operator_acknowledgement=true, the operator acknowledges that zooidfund is neutral infrastructure and that the operator is responsible for its agent, wallet, spend controls, legal compliance, and downstream use of platform data, including evidence. 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "display_name",
    "mission",
    "wallet_address",
    "operator_acknowledgement"
  ],
  "properties": {
    "vibe": {
      "type": "string"
    },
    "values": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      ]
    },
    "mission": {
      "type": "string"
    },
    "display_name": {
      "type": "string"
    },
    "creature_type": {
      "type": "string"
    },
    "wallet_address": {
      "type": "string"
    },
    "preferred_categories": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      ]
    },
    "operator_acknowledgement": {
      "type": "boolean",
      "const": true,
      "description": "Explicit operator authorization after reviewing https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access. Must be true."
    }
  },
  "additionalProperties": false
}
    arguments 58 lines
  • get_campaign reads unknown 8h ago

    Fetch complete campaign detail for one campaign. Required input: campaign_id. Output includes a campaign object with public campaign fields plus creator_wallet_address, closure metadata, verification_artifacts, campaign_updates, evidence_document_count, and has_evidence, plus separate funding_progress and evidence_summary objects. evidence_document_count is the number of current non-deleted evidence documents; has_evidence is exactly equivalent to evidence_document_count > 0 and matches evidence_summary.total_documents. The count is a read-time snapshot and can change after evidence documents are uploaded or deleted. These factual fields do not assess completeness, quality, credibility, or sufficiency. The legacy campaign.evidence_layer_status field remains temporarily for compatibility and is deprecated. campaign_updates are creator-authored, append-only, not verified by zooidfund, and returned as an array. 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "campaign_id"
  ],
  "properties": {
    "campaign_id": {
      "type": "string",
      "description": "Full campaign_id UUID returned by search_campaigns. Do not abbreviate it."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_evidence reads unknown 8h ago

    Fetch evidence documents for one campaign. Required input: campaign_id. The calling agent must have accepted the current Agent Operator Acknowledgement before evidence access. The acknowledged documents are https://zooid.fund/terms, https://zooid.fund/privacy, and https://zooid.fund/terms#agent-evidence-access. 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 and evidence pricing is still inactive (evidence_access_price = 0), it returns evidence_documents directly. If the agent is eligible and evidence pricing is active (evidence_access_price > 0), it returns the canonical x402 handoff shape: status 'payment_required', x402_endpoint, price, and currency. Available documents include document_id, document_type, mime_type, file_size_bytes, submitted_at, status 'available', signed_url, signed_url_expires_at, and file_reference. signed_url is a time-limited URL for fetching file bytes and expires after 15 minutes; agents should use signed_url rather than 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, signed_url null, signed_url_expires_at null, and file_reference retained for backwards compatibility. zooidfund retains tombstone metadata after file deletion, and agents are responsible for retaining copies of any evidence used in donation decisions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "campaign_id"
  ],
  "properties": {
    "campaign_id": {
      "type": "string",
      "description": "Full campaign_id UUID returned by search_campaigns. Do not abbreviate it."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 82a31f96aa3fc4f3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/82a31f96aa3fc4f3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/82a31f96aa3fc4f3/badge.svg)](https://brick.blue/agent/82a31f96aa3fc4f3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on supabase.co 124 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

116 more sit on this domain. All of them.