Skip to content
Back to search

mcp-uk-cma-cases

uk-cma-cases -- the UK Competition and Markets Authority's case pages: merger inquiries, market studies and investigations, competition-law (Competition Act 1998) cases, consumer-enforcement cases, digital-markets cases, regulatory appeals and subsidy-advice referrals.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pipeworx-io--mcp-uk-cma-cases/badge.svg)](/listings/pipeworx-io--mcp-uk-cma-cases)

HTML

<a href="/listings/pipeworx-io--mcp-uk-cma-cases"><img src="/api/listings/pipeworx-io--mcp-uk-cma-cases/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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

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

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/uk-cma-cases/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 2024+ data sources. The only difference is which pack's tools are listed **directly**; `ask_pipeworx` reaches all of them from either one.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 158 lines
  1. # @pipeworx/uk-cma-cases
  2. Has the UK Competition and Markets Authority opened a case about this company or
  3. market: a merger inquiry, a market study, a Competition Act investigation, a
  4. consumer-protection enforcement case?
  5. Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2024+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
  6. ## Tools
  7. - `uk_cma_cases_list(query?, case_type?, case_state?, market_sector?, opened_from?, opened_to?, start?, count?)`
  8. — the CMA's case listing, newest first when no text is given. Each row carries
  9. the title, case type, open or closed state, market sectors, opened and closed
  10. dates, outcome code, the CMA's own summary and the case page link. The first five
  11. rows also carry `latest_update` (date and text of the newest dated entry on the
  12. case page, e.g. a Phase 1 decision). Returns
  13. `result` (`rows`, `beyond_last_page`, `no_case_matched`), `total_matches`,
  14. `individual_cases_excluded` and `data_as_of`.
  15. - `uk_cma_case_read(slug)` — one case page as plain text: statutory timetable,
  16. decisions, final-report notices, undertakings, `latest_update` and a dated
  17. `timeline` (newest first), the list of published case
  18. documents with titles and links, and the page's change history, newest first.
  19. ## Auth
  20. Keyless.
  21. ## Data sources
  22. - Competition and Markets Authority, case register. Read from the
  23. publisher on request. `data_as_of` is the day of the read; each row carries the
  24. page's own `last_updated`.
  25. ## Behaviour worth knowing
  26. - Firms and markets only. The CMA also lists criminal-cartel cases and
  27. competition-disqualification cases, which concern individuals. Those case types
  28. are excluded in the query and the number left out for the same filters is
  29. returned as `individual_cases_excluded`; asking for one of them is refused.
  30. - E-mail addresses and phone numbers in case text are removed and counted in
  31. `redactions`.
  32. - The outcome code is often empty while a decision is already published in the case
  33. text. An empty code is rendered "not recorded in case metadata", never as
  34. "undecided"; `latest_update` and `timeline` hold the decision.
  35. - `no_case_matched` means the CMA listing was read and holds no case for these
  36. filters; it is not a clearance of a company. A failed read throws instead.
  37. - Case type values: mergers, markets, ca98-and-civil-cartels, consumer-enforcement,
  38. digital-markets-unit, regulatory-references-and-appeals,
  39. review-of-orders-and-undertakings, sau-referral, information-and-advice-to-government.
  40. ## Quick Start
  41. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  42. ```json
  43. {
  44. "mcpServers": {
  45. "uk-cma-cases": {
  46. "url": "https://gateway.pipeworx.io/uk-cma-cases/mcp"
  47. }
  48. }
  49. }
  50. ```
  51. ### What this endpoint actually serves
  52. `tools/list` at `https://gateway.pipeworx.io/uk-cma-cases/mcp` returns the tools in the table
  53. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  54. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  55. gateway-wide set. So the tool count you see is larger than this table: a
  56. single-pack endpoint currently lists roughly 30 shared tools alongside the
  57. pack's own. The connection's `initialize` response states its exact scope, and
  58. is the authoritative answer for a given day.
  59. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  60. scoped connection answer a question this pack does not cover — via
  61. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  62. second MCP server. There is currently no way to mount a pack endpoint without
  63. them; if the extra schemas cost you more context than the routing is worth,
  64. connect to the full gateway once rather than to several pack endpoints.
  65. Or connect to the full Pipeworx gateway to get every pack's tools listed
  66. directly, instead of just this one's:
  67. ```json
  68. {
  69. "mcpServers": {
  70. "pipeworx": {
  71. "url": "https://gateway.pipeworx.io/mcp"
  72. }
  73. }
  74. }
  75. ```
  76. Both URLs reach the same gateway and the same 2024+ data sources. The
  77. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  78. reaches all of them from either one.
  79. ## No MCP client? Call it over HTTP
  80. ```bash
  81. curl -X POST https://gateway.pipeworx.io/v1/tools/uk_cma_cases_list \
  82. -H 'Content-Type: application/json' \
  83. -d '{"query":"Vodafone"}'
  84. ```
  85. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/uk_cma_cases_list`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  86. ## Run it from npm
  87. `@pipeworx/mcp-uk-cma-cases` is a local stdio bridge to the Pipeworx gateway: your MCP client
  88. starts it with `npx`, and it forwards every call to the same
  89. `https://gateway.pipeworx.io/uk-cma-cases/mcp` endpoint shown above. It needs network access;
  90. there is no offline mode.
  91. ```json
  92. {
  93. "mcpServers": {
  94. "uk-cma-cases": {
  95. "command": "npx",
  96. "args": ["-y", "@pipeworx/mcp-uk-cma-cases"]
  97. }
  98. }
  99. }
  100. ```
  101. Without a key it calls anonymously, capped at 50 calls a day. A free account
  102. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  103. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  104. The key is sent as a Bearer token, the same way a hosted connection sends it,
  105. so calls are metered and billed exactly as they are there.
  106. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  107. also list `ask_pipeworx` and the other gateway-wide tools.
  108. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  109. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  110. your Node version's documentation.
  111. ## Using with ask_pipeworx
  112. Instead of calling tools directly, you can ask questions in plain English —
  113. this works on the pack endpoint above as well as on the full gateway:
  114. ```
  115. ask_pipeworx({ question: "your question about Uk Cma Cases data" })
  116. ```
  117. The gateway picks the right tool and fills the arguments automatically.
  118. ## More
  119. - [Docs and guides](https://pipeworx.io/docs)
  120. - [pipeworx.io](https://pipeworx.io)
  121. ## License
  122. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.