Benevity
by Benevity
Search Benevity's verified nonprofit database from an AI agent. Two read-only tools, no sign-in, and no path to a donation — Benevity states the connector returns links and cannot move money. Both enumerations agree.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Benevity via MCP
https://mcp.benevity.org/general/v1/nonprofitWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Benevity Tools & Capabilities (2)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The vendor documentation Anthropic nominates is Anthropic's own. The directory's
documentationURL points atsupport.claude.com, which redirects toacademy.claude.com— a page written by Anthropic about its own connector. Treating it as the vendor's enumeration would have made the Reverse-Honeycomb self-referential, comparing Anthropic's directory against Anthropic's tutorial. Benevity's genuine documentation is elsewhere, in its own help centre, and is linked below. It is the richer of the two. - We verified nothing about the auth posture ourselves. Both parties state no authentication is needed and Anthropic's directory records the server as authless, but every request we made returned 403 before reaching the server.
authVerifiedis therefore false: an authless claim we could not exercise is a vendor claim, not an observation. - No RFC 9728 descriptor exists.
.well-known/oauth-protected-resource, the path-suffixed variant, and.well-known/oauth-authorization-serverall returned 404 — as did a nonsense control path, so the host is not a catch-all and those 404s are real. There is no scope list because there is no OAuth. - We could not read tool schemas, annotations or prompts. No
tools/list,prompts/listorresources/listresponse was obtainable. Parameter shapes and read-only labels on this page come from Benevity's prose, and the two advertised prompts are unread. - Ten results per search, no pagination. Benevity documents a hard cap of 10 and a query length of 3 to 180 characters, and directs users to refine terms instead of paging. A broad question cannot be exhaustively answered through this connector.
- Cause identifiers are session-scoped. Benevity's troubleshooting states organisation identifiers only work within the current search session, so a detail lookup in a new conversation requires searching again first. Identifiers cannot be stored and reused later.
- Results are cached, not live. Benevity states the connector uses cached data that refreshes regularly, while Anthropic's tutorial says Claude accesses the database in real time. The two descriptions conflict, and neither publishes a refresh interval.
- No tax or financial data. Benevity states the connector returns mission information, programme descriptions and website links, and directs users to the nonprofit's site or to external resources for tax or financial detail. Do not use it to check charitable status.
- Coverage is uneven and incomplete. Benevity states coverage is strongest for United States organisations and major international nonprofits, and that an organisation missing from results may simply not be part of the validated network yet. Absence is not evidence of illegitimacy.
- Rate limits exist but no rate is published. Benevity says only that standard rate limits apply to prevent abuse.
- The database size is stated four different ways across four sources, spanning two million to 2.5 million. Cite the range, not a figure.
Frequently asked questions
No. Benevity's documentation states the connector returns verified links to nonprofit websites where a person completes the donation, keeping giving within official channels. Both tools are documented as read-only and idempotent, neither takes an amount or a payment method, and no tool name carries a donate, grant or disburse verb. The agent researches; a human pays.
Two, and both enumerations agree on that. Anthropic's directory lists Benevity Nonprofit Search and Benevity Get Nonprofit Details; Benevity's own help centre documents benevity_nonprofit_search and benevity_nonprofit_details. The names differ in casing and prefix but map one-to-one, with nothing extra on either side. Both are read-only searches over public nonprofit data.
No. Benevity states you do not need a Benevity account and that no authentication is required, and Anthropic's directory records the server as authless. We could not confirm this over the wire: the endpoint returned 403 from a generic edge with no authentication challenge header, which is a network block rather than an auth posture.
None that Benevity documents. Benevity states the connector collects no personal data, that search terms are not stored or associated with individual users, and that no personally identifiable information is shared with the MCP server. Everything returned is public nonprofit information — missions, programmes, geography and a website link.
Up to ten per query, with no pagination. Benevity documents a maximum of 10 results, a query length of 3 to 180 characters, and advises refining search terms rather than paging when results miss. That cap is a real ceiling on coverage: a database Benevity sizes in the millions is reachable only ten rows at a time.
The two sources disagree. Anthropic's tutorial says all paid plans — Pro, Max, Team and Enterprise — and gives Team and Enterprise admin steps. Benevity's own pages say the connector is currently available for Claude Pro and to contact Anthropic about Team or Enterprise. Anthropic's page is newer, so treat the wider claim as current.
Between two and 2.5 million, depending on which source you read. Benevity's press release says more than two million validated nonprofits, Anthropic's directory says 2.3 million, Benevity's integration page says 2.4 million, and Anthropic's tutorial says 2.5 million or more. No source is dated in a way that resolves the spread.
Because an edge proxy blocks it, not because the server demands credentials. The response is a 134-byte generic Forbidden page served through Google's front end, with no authentication challenge header. Every path under the same prefix returns a byte-identical body, including paths that do not exist, so the 403 carries no information about the server behind it.
Sources
- Benevity help centre, "Benevity nonprofit MCP server" (retrieved 2026-08-22). Benevity's own tool enumeration, parameter limits, error codes and troubleshooting. The page serves a Cloudflare interstitial to command-line clients;
causeshelp.benevity.org/robots.txtpermits/hc/en-us/articles/, so the block is bot-filtering rather than policy, and the text was read through Zendesk's public Help Center API on the same host. · retrieved 2026-08-22 - Benevity help centre, "Anthropic x Benevity" (retrieved 2026-08-22). Source for the donation answer, result cap, caching and plan availability. · retrieved 2026-08-22
- Anthropic tutorial, "Using the Benevity connector in Claude" (retrieved 2026-08-22). The URL Anthropic's directory publishes as the connector's documentation,
support.claude.com/en/articles/12923227-using-the-benevity-connector-in-claude, redirects here. Anthropic's page about its own connector, not Benevity's. · retrieved 2026-08-22 - Benevity press release, "Benevity Integrates Its Trusted Global Nonprofit Network With Anthropic's Claude" (retrieved 2026-08-22) · retrieved 2026-08-22
- Live endpoint probe of
https://mcp.benevity.org/general/v1/nonprofit: one anonymous initialize POST returned HTTP 403 with a 134-byte generic body and nowww-authenticateheader; prefix bisection across/general/versus control paths; RFC 9728 metadata paths and a nonsense control all 404 (2026-08-22) · retrieved 2026-08-22 www.benevity.com/robots.txt, which explicitly allows ClaudeBot andanthropic-aifull access to public content (retrieved 2026-08-22) · retrieved 2026-08-22- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Benevity support — <mailto:support@benevity.com> · Benevity documents <mailto:support@benevity.org> for connector issues · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Data & Research
- Developer
- Benevity
- Tools
- 2
- Domain
- mcp.benevity.org
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.