Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Search Benevity's verified nonprofit database from an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Benevity MCP server connects Benevity's verified nonprofit database to Claude, ChatGPT and any MCP-compatible agent. Two read-only tools search charitable organisations by cause, keyword or location and return mission detail plus a verified website link. No account, no sign-in, and no tool that can move money.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
documentation URL points at support.claude.com, which redirects to academy.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.authVerified is therefore false: an authless claim we could not exercise is a vendor claim, not an observation..well-known/oauth-protected-resource, the path-suffixed variant, and .well-known/oauth-authorization-server all 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.tools/list, prompts/list or resources/list response was obtainable. Parameter shapes and read-only labels on this page come from Benevity's prose, and the two advertised prompts are unread.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.
causeshelp.benevity.org/robots.txt permits /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-22support.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-22https://mcp.benevity.org/general/v1/nonprofit: one anonymous initialize POST returned HTTP 403 with a 134-byte generic body and no www-authenticate header; prefix bisection across /general/ versus control paths; RFC 9728 metadata paths and a nonsense control all 404 (2026-08-22) · retrieved 2026-08-22www.benevity.com/robots.txt, which explicitly allows ClaudeBot and anthropic-ai full access to public content (retrieved 2026-08-22) · retrieved 2026-08-22Connect Benevity once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.