@pipeworx/uk-charity-commission

Connect: https://gateway.pipeworx.io/uk-charity-commission/mcp · Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

The UK Register of Charities from the Charity Commission for England and Wales — a registered charity’s status, objects, areas of operation, reported income and expenditure year by year, and its named trustees.

Tools

• ukcharity_search(query, limit?, registered_only?, _apiKey) — find charities by name.
• ukcharity_details(charity_number, subsidiary_number?, _apiKey) — the full register entry.
• ukcharity_financials(charity_number, subsidiary_number?, _apiKey) — filed income/expenditure history.
• ukcharity_trustees(charity_number, subsidiary_number?, _apiKey) — the trustee board.

Auth

BYO key, with PLATFORM_CHARITY_COMMISSION_KEY as the platform fallback once one is provisioned. Until then the pack is byoExpected in workers/gateway/src/pack-manifest.json and every call needs a caller-supplied _apiKey; the refusal says so in those words.

Registration is free but not instant-self-serve in one step: sign up at https://api-portal.charitycommission.gov.uk/, then subscribe to the “Charity Commission Register of Charities” product to be issued an Ocp-Apim-Subscription-Key. There is no keyless or demo path — every operation answers 401 Access Denied without the header.

Data sources

• https://api.charitycommission.gov.uk/register/api/searchCharityName/{text}
• https://api.charitycommission.gov.uk/register/api/allcharitydetailsV2/{number}/{subsidiary}
• https://api.charitycommission.gov.uk/register/api/charityfinancialhistory/{number}/{subsidiary}
• https://api.charitycommission.gov.uk/register/api/charitytrusteeinformation/{number}/{subsidiary}

Things worth knowing:

• Azure API Management 401s, never 403s, on a missing or wrong key, and says so in a WWW-Authenticate: AzureApiManagementKey header — so a key problem is unambiguous and is not confusable with an entitlement lag.
• A wrong path 404s BEFORE the key is checked, which is how the operation names above were confirmed without holding a key. charitytrustees, charityclassification, charitypublishedreport, charityotheraddresses and charityeventhistory all 404 — they do not exist. The real names are charitytrusteeinformation, charityareaofoperation, charitygoverningdocument and charityotherregulators, all of which 401 (i.e. exist).
• Every charity-scoped operation takes TWO path segments: the registered charity number and a subsidiary number. The main charity is 0; omitting the second segment 404s.
• register-of-charities.charitycommission.gov.uk/api/search — the public website’s own endpoint — was returning 502 Bad Gateway from the Azure Application Gateway when this pack was built, so it is not a keyless fallback.

Tools

• ukcharity_search — Search the UK Register of Charities by name and return matching registered charities with their charity number, registration status, registered address and latest reported income. AUTHORITATIVE for ch
• ukcharity_details — Fetch the full UK Register of Charities entry for one charity number: registered and working names, status and registration/removal dates, charitable objects, activities, areas of operation, governing
• ukcharity_financials — Return a UK charity’s reported financial history year by year — total gross income, total expenditure and the financial period each figure covers, as filed in its annual returns to the Charity Commiss
• ukcharity_trustees — List the named trustees of one UK registered charity — the people legally responsible for it — with each trustee’s id, appointment date and the other charities they are a trustee of, as held by the Ch