mcp-uk-gazette

UK Gazette MCP — The Gazette (www.thegazette.co.uk), the UK's official

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

Tools

| Tool | Description | |------|-------------| | gazette_search_notices | Search The Gazette — the UK's official public record of statutory notices (London, Edinburgh and Belfast editions, archive back to 1665). Full-text search plus filters for notice category, publication date range, edition, and location. Covers company events (liquidations, administrations, winding-up petitions, name changes), personal insolvency, deceased estates, road/planning orders, honours, state and royal notices. Use for "official UK notices about X", "gazette notices for company Y", "road closure orders near Z". Example: gazette_search_notices({ query: "Tesco", category: "corporate insolvency" }) | | gazette_insolvency_notices | Search official UK insolvency notices in The Gazette — the statutory public record where liquidations, administrations, winding-up petitions and orders, bankruptcy orders, creditors' meetings, and notices to creditors MUST be published. The go-to source for "is UK company X in liquidation/administration", monitoring company distress, or tracking personal bankruptcies. Search by company name or Companies House number (both are indexed). scope narrows to "corporate" or "personal" insolvency. Example: gazette_insolvency_notices({ company: "Wilko", scope: "corporate" }) | | gazette_deceased_estates | Search UK deceased-estates notices in The Gazette (Trustee Act 1925 s.27 notices) — executors advertise a death so creditors and claimants can come forward before the estate is distributed. Used for probate research, tracing an estate, checking whether a death notice was placed, and finding the claim deadline. Filter by name, date of death, claim expiry date, or location. Example: gazette_deceased_estates({ name: "John Smith", died_after: "2026-01-01" }) | | gazette_get_notice | Get the structured record for one Gazette notice by its ID (from any gazette search tool, or a thegazette.co.uk/notice/ URL). Returns the notice type, publication date, gazette edition and issue, companies named (with Companies House numbers), people, addresses with coordinates, related legislation, and key dates. Example: gazette_get_notice({ notice_id: "4123456" }) | | gazette_notice_categories | Browse The Gazette's notice-category taxonomy — the category codes accepted by gazette_search_notices. Optionally filter by a search word. Categories span companies (insolvency, name changes, mergers), people (bankruptcy, deceased estates, honours), environment & infrastructure (planning, roads, property), state/royal/church notices, and money (pensions, coinage). Example: gazette_notice_categories({ search: "insolvency" }) |

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/uk-gazette/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, 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.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1684+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/gazette_search_notices \
  -H 'Content-Type: application/json' \
  -d '{"query":"Tesco","category":"corporate insolvency"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/gazette_search_notices. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "uk-gazette": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-uk-gazette"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-uk-gazette

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Uk Gazette data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides
• pipeworx.io

License

MIT