General Tools
giveready.org
Search and donate to nonprofits, with detailed information and on-chain donation history.
ENDPOINT 1
https://www.giveready.org/mcp
MCP server metadata
- Name
- giveready
- Version
- 0.3.0
GiveReady — search 41,000+ nonprofits, get profiles with impact data, initiate USDC donations via x402, and contribute back via consensus enrichment. See https://www.giveready.org/AGENTS.md for the live bounty list.
Known tools 6
search_nonprofitsSearch 41,000+ nonprofits across 29 cause areas by keyword, cause, or country.
Inferred read-onlyget_nonprofitGet detailed information about a specific nonprofit including mission, programmes, impact metrics, registration details, and donation links.
Inferred read-onlylist_causesList all 29 cause areas in the GiveReady directory with the number of nonprofits in each.
Inferred read-onlyget_donation_historyGet on-chain USDC donation history for a nonprofit — total received, count, recent transactions with hashes.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.giveready]
url = "https://www.giveready.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"giveready": {
"type": "http",
"url": "https://www.giveready.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: giveready
Remote MCP URL: https://www.giveready.org/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"giveready": {
"url": "https://www.giveready.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"giveready": {
"type": "http",
"url": "https://www.giveready.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "giveready",
"transport": "streamable-http",
"url": "https://www.giveready.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.