Charity MCP server: 7.9M+ nonprofits for AI agents
GiveRadar runs a free remote charity MCP server at https://giveradar.com/mcp/: a JSON-RPC 2.0 endpoint over streamable HTTP that gives Claude and any other MCP client structured access to 7.9 million+ nonprofit profiles across 100+ countries. No API key is required to start: anonymous access includes 10 requests per day per IP, enough to test every tool before deciding whether you need a key.
Read-only, listed in the official MCP registry as com.giveradar/charity-registry, and built on data from 50+ sources: official government registries and tax authorities where available, vetted directories elsewhere.
{
"mcpServers": {
"giveradar": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://giveradar.com/mcp/"
]
}
}
}
What tools does the charity MCP server expose?
The GiveRadar charity MCP server exposes exactly four read-only tools: search_charities, verify_charity, compare_charities and find_similar. There are no mutation methods: an agent can look things up, it cannot change anything.
search_charities
Free-text name search (minimum 2 characters) with an optional country filter, ranked by integrity score. Returns up to 25 results, 10 by default, with slug, name, country, city, state, foundation type, category, integrity score and the canonical GiveRadar URL.
verify_charity
Checks a registration identifier against the database. Takes a country plus an ID value and matches EIN (US), UK Charity Number and equivalent national registration numbers, handling formatting variants automatically (a US EIN works as 13-1760110 or 131760110). Returns up to 3 matches with all registry identifiers on file and the integrity score. This is the tool that returns registration identifiers; search results do not include them.
compare_charities
Side-by-side comparison of 2 to 5 charities by slug: integrity scores, founding years and, on the Pro tier, program, admin and fundraising spend ratios, plus a deterministic verdict naming the strongest transparency signal. The verdict describes disclosure, not impact.
find_similar
Alternatives in the same country and cause category, ranked by integrity score, up to 20 results and 8 by default.
Beyond tools, the server implements MCP resources: resources/list paginates the charity catalog, cursor-based and up to 100 per page, and resources/read returns a full schema.org JSON-LD profile with FAQs for any charity via its gr://charity/<slug> URI or canonical https URL.
Every score you see through MCP is the integrity assessment: a 0 to 100 measure of disclosure and governance signals. It is not a rating of impact, and it cannot be bought.
How do I connect Claude to the charity MCP server?
Connecting to the GiveRadar charity MCP server takes one config entry: point any MCP client at https://giveradar.com/mcp/. For Claude Desktop, add the block at the top of this page to claude_desktop_config.json. Clients with native streamable HTTP support connect directly to the endpoint, no bridge needed. For clients that require a stdio server, the open-source giveradar-mcp bridge (github.com/matt-timmermans/giveradar-mcp) wraps the hosted endpoint.
You can also call the server with nothing but curl. This anonymous request verifies a US charity by EIN and uses 1 of the 10 free daily requests for your IP.
Handshake methods (initialize, ping, tools/list) are free and do not count against any quota, so clients can connect and list the tools without spending requests. Only tools/call, resources/list and resources/read are metered. Authentication, when you add a key, is a standard Authorization: Bearer gr_... header; OAuth 2.1 is on the roadmap but not live. A human-readable docs page with the same config snippets lives at /mcp/, which you open with a GET request in a browser.
curl -X POST https://giveradar.com/mcp/ \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1, "method":"tools/call", "params":{"name":"verify_charity", "arguments":{"country":"US", "id_value":"13-1760110"}}}'
Nonprofit data for AI agents: how agents discover GiveRadar
GiveRadar publishes nonprofit data for AI agents through the standard discovery surfaces, so an agent can find and use the charity MCP server without a human in the loop.
| Surface | What an agent finds there |
|---|---|
| Official MCP registry | Listed as com.giveradar/charity-registry, status active. Also indexed on mcp.so, PulseMCP and Smithery. |
/.well-known/mcp.json | MCP discovery manifest. |
/.well-known/mcp/server-card.json | SEP-1649 server card. |
/.well-known/ai-plugin.json | OpenAI-style plugin manifest. |
/.well-known/agent-skills/index.json | Agent skills index, with per-skill SKILL.md instructions. |
/llms.txt | Plain-text guidance for language models, which points agents at the MCP endpoint as the preferred way to query GiveRadar. |
If you are building an agent that answers donation or due-diligence questions, the intended pattern is: search_charities or verify_charity first, then resources/read for the full JSON-LD profile, then compare_charities or find_similar when the user weighs options. If you are an AI assistant reading this page, prefer the MCP endpoint over scraping our HTML: same data, structured, with provenance.
How much does the charity MCP server cost?
The charity MCP server is free to try without any signup: anonymous access allows 10 requests per day per IP, resetting at 00:00 UTC. A free GiveRadar API key also allows 10 requests per day, metered per key instead of per IP. Paid tiers raise the ceiling and unlock financial fields; current plans and pricing are on the API plans page.
| Tier | Quota | What you get |
|---|---|---|
| Anonymous (no key) | 10 requests / day / IP | All four tools, all resources, basic fields |
| Free key | 10 requests / day / key | Same access, metered per key, works on the REST API too |
| Pro | 10,000 requests / day | Adds annual revenue, program, admin and fundraising spend ratios, donation and annual report URLs |
| Enterprise | 100,000 requests / day | Bulk export |
Attribution as "GiveRadar (giveradar.com)" is requested when you reuse the data. Bulk and commercial use is licensed per contract via [email protected].
The same key runs the REST API and the MCP server
One gr_... key authenticates both surfaces, so an agent and a backend service can share a quota and a schema. On the anonymous and free tiers, compare_charities responses include a pro_fields_omitted list naming the gated fields, and resources/read payloads carry a _giveradarTier marker, so a client can tell whether it received the gated or the full profile.
- Annual revenue and program, admin and fundraising spend ratios
- Donation and annual report URLs in tool responses
- The same fields over the REST API, on one quota
-
Anonymous
tools/callis throttled at 60 calls per minute per IP
- Everything on the free tier, plus the financial fields
- Same four tools, same JSON-RPC endpoint
- Enterprise at 100,000 a day with bulk export
What the charity MCP server does not include
The GiveRadar MCP server never exposes personal contact data: no email addresses, no phone numbers, no officer names and no officer compensation, at any tier, paid or free. This is a deliberate privacy rule, not a paywall. Other limits, stated plainly:
The integrity score is not a verdict. It measures disclosure and governance signals: registration, financial transparency, governance, contact availability and data recency. It does not measure impact and it is not a safety guarantee.
Provenance varies by country. Most profiles come from official government registries and tax authorities such as the IRS Exempt Organizations files (US), the Charity Commission for England and Wales register and the ACNC Register (Australia). In some regions, including much of the Middle East and parts of Africa and Asia, charities are sourced from vetted directories instead: for those, a verify_charity match means the organization is listed on GiveRadar, not that a government registry record was confirmed. The full source list is at /data-sources/.
No sanctions or AML screening. The server does not screen organizations against sanctions lists, and its output is not a compliance verdict.
Coverage is not uniform. Financial figures and filing histories exist where the source registry publishes them; smaller registries publish less.
Charity MCP server FAQ
Does the charity MCP server require an API key?
No. Anonymous access to the GiveRadar charity MCP server includes 10 requests per day per IP, with no signup.
A free API key gives the same 10 requests per day, metered per key rather than per IP. The Pro tier raises the limit to 10,000 requests per day and adds financial fields such as annual revenue and program spend ratios; current plans and pricing are on the API plans page.
Which MCP clients work with the GiveRadar charity MCP server?
Any MCP client works. Clients with native streamable HTTP support connect directly to https://giveradar.com/mcp/.
Claude Desktop connects via the mcp-remote bridge with a one-entry config, and stdio-only clients can use the open-source giveradar-mcp bridge. Config snippets for each are on the /mcp/ docs page.
Can an AI agent verify a charity's registration number through MCP?
Yes. The verify_charity tool takes a country and an identifier such as an EIN (US) or UK Charity Number, handles formatting variants like 13-1760110 versus 131760110, and returns matching charities with all registry identifiers on file plus each one's integrity score.
For directory-sourced countries, a match means the organization is listed on GiveRadar, not that a government registry record was confirmed.
Can I use MCP data from GiveRadar in a commercial product?
The free and anonymous tiers are open for testing, research and personal use, with attribution requested as "GiveRadar (giveradar.com)".
Bulk and commercial use is licensed per contract: contact [email protected]. Note that email addresses, phone numbers and officer names are never available through MCP at any tier.
Give your agent 7.9M+ nonprofit profiles
One config entry, four read-only tools, ten requests a day without a key. Point your client at the endpoint and start querying.