Uk Charity Commission MCP server

@pipeworx/uk-charity-commission

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.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

• ukcharitysearch(query, limit?, registeredonly?, _apiKey) — find charities by name.
• ukcharitydetails(charitynumber, subsidiarynumber?, apiKey) — the full register entry.
• ukcharityfinancials(charitynumber, subsidiarynumber?, apiKey) — filed income/expenditure history.
• ukcharitytrustees(charitynumber, subsidiarynumber?, apiKey) — the trustee board.

Auth

BYO key, with PLATFORMCHARITYCOMMISSIONKEY 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 , 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

Things worth knowing:

so in a WWW-Authenticate: AzureApiManagementKey header — so a key problem is unambiguous and is not confusable with an entitlement lag.

• Azure API Management 401s, never 403s, on a missing or wrong key, and says

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).

• A wrong path 404s BEFORE the key is checked, which is how the operation

charity number and a subsidiary number. The main charity is 0; omitting the second segment 404s.

• Every charity-scoped operation takes TWO path segments: the registered

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.

• register-of-charities.charitycommission.gov.uk/api/search — the public

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "uk-charity-commission": {
      "url": "https://gateway.pipeworx.io/uk-charity-commission/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/uk-charity-commission/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.