Giveready

What the giveready MCP server does

The giveready MCP server makes GiveReady’s nonprofit directory available to AI assistants through Model Context Protocol. The directory contains more than 41,000 verified nonprofits covering 29 cause areas. Available organization data can include programmes, impact metrics, beneficiary demographics, donation links, and wallet addresses when those details are present.

This server is intended for agents that need to identify youth nonprofits by search criteria and then inspect a specific organization. It supports discovery rather than acting as a general-purpose payment processor. GiveReady also exposes REST endpoints for applications that do not use MCP, including nonprofit search, organization details, cause listings, statistics, and donation-related routes.

How it works

The package runs as a local stdio MCP server. An MCP-compatible client starts it with npx and communicates with the process using the configured MCP connection. The README provides the server name giveready and the package command giveready-mcp.

The underlying GiveReady service combines a Cloudflare Workers application with a D1 SQLite database. Its public API includes search and detail routes, while /mcp provides the MCP server manifest. GiveReady also documents x402 donation endpoints using USDC on Solana, but the listed MCP tools focus on nonprofit data and enrichment.

Use the giveready MCP server when an agent must find organizations by cause or other available directory data, inspect a nonprofit record, or contribute additional nonprofit information through the enrichment tool.

Setup and configuration

Add the server to an MCP client configuration with a command and argument like this:

{
  "mcpServers": {
    "giveready": {
      "command": "npx",
      "args": ["giveready-mcp"]
    }
  }
}

No environment variables or API keys are specified in the provided setup. The repository also includes instructions for running a complete self-hosted instance: clone the project, install npm dependencies, create a Cloudflare D1 database, apply the schema and seed files, and start the development process with npm run dev. Production deployment uses the repository’s Cloudflare configuration and deployment documentation.

Tools and capabilities

The giveready MCP server lists four tools:

• search_nonprofits — searches the available nonprofit directory.
• get_nonprofit — retrieves information for a nonprofit.
• list_causes — lists the supported cause areas.
• submit_enrichment — submits additional nonprofit information.

The broader service also provides donation endpoints, donation history, an embeddable donation widget, and agent-discovery files.

Limitations and notes

The available data depends on what GiveReady has recorded for each nonprofit. Wallet addresses, donation links, programmes, impact metrics, and beneficiary information are available where provided, so an agent should not assume every organization has every field.

It does not specify the exact search syntax, tool argument schema, enrichment validation rules, or authentication requirements for the MCP tools. Consult the package or repository documentation before building workflows that depend on particular fields or responses.

GiveReady describes direct USDC donations on Solana through x402, with transaction fees paid by the donor. That payment flow is separate from the four MCP tools listed above and should not be inferred to occur automatically when an agent searches or retrieves a nonprofit.