Skip to content
Back to search

mcp-uk-gc-actions

uk-gc-actions -- the UK Gambling Commission's published regulatory actions against licensed gambling businesses: financial penalties, payments in lieu of a penalty (settlements), licence revocations and suspensions, licence conditions, public statements and warnings, with the Commission's own…

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-gc-actions/badge.svg)](/listings/pipeworx-io--mcp-uk-gc-actions)

HTML

<a href="/listings/pipeworx-io--mcp-uk-gc-actions"><img src="/api/listings/pipeworx-io--mcp-uk-gc-actions/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-gc-actions": {
      "url": "https://gateway.pipeworx.io/uk-gc-actions/mcp"
    }
  }
}

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/uk-gc-actions/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 · 150 lines
  1. # @pipeworx/uk-gc-actions
  2. Has the UK Gambling Commission taken regulatory action against this gambling
  3. operator: a financial penalty, a settlement, a licence revocation, conditions
  4. attached to a licence, a public statement?
  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_gc_actions_list(name?, outcome?, start?, count?)` — the Commission's
  8. published regulatory actions, newest first. Each row carries the action id,
  9. operator, whether it was a sanction or a settlement, the decision date and the
  10. outcomes. `outcome` keeps rows whose outcomes include the text. Returns `result`
  11. (`rows`, `no_action_found`, `no_action_with_that_outcome`, `beyond_last_page`,
  12. `only_individuals_matched`), `individuals_dropped`, `next_start` and `data_as_of`.
  13. - `uk_gc_action_read(id)` — one action in full: operator, licence account number,
  14. decision date, outcomes and the Commission's own written findings, including the
  15. licence conditions breached and the penalty amount.
  16. ## Auth
  17. Keyless.
  18. ## Data sources
  19. - Gambling Commission, regulatory actions. Read from the publisher on request.
  20. `data_as_of` is the day of the read; each row carries the Commission's decision date.
  21. ## Behaviour worth knowing
  22. - Operators only. The list mixes licensed businesses with personal-licence holders
  23. (individuals). A row is served only when the name carries a legal form (Limited,
  24. Ltd, PLC, LLC, GmbH, ...) and is not a "trading as" name. Every other row is
  25. dropped and counted in `individuals_dropped`. The test is strict, so an operator
  26. with an unusual name can be dropped; the count is returned.
  27. - E-mail addresses and phone numbers in the text of an action are removed and
  28. counted in `redactions`. The narrative can name other parties; read it as the
  29. Commission wrote it.
  30. - `no_action_found` means the published list was read and holds no action for this
  31. name; it is not a clearance of an operator. A failed read throws.
  32. ## Quick Start
  33. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  34. ```json
  35. {
  36. "mcpServers": {
  37. "uk-gc-actions": {
  38. "url": "https://gateway.pipeworx.io/uk-gc-actions/mcp"
  39. }
  40. }
  41. }
  42. ```
  43. ### What this endpoint actually serves
  44. `tools/list` at `https://gateway.pipeworx.io/uk-gc-actions/mcp` returns the tools in the table
  45. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  46. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  47. gateway-wide set. So the tool count you see is larger than this table: a
  48. single-pack endpoint currently lists roughly 30 shared tools alongside the
  49. pack's own. The connection's `initialize` response states its exact scope, and
  50. is the authoritative answer for a given day.
  51. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  52. scoped connection answer a question this pack does not cover — via
  53. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  54. second MCP server. There is currently no way to mount a pack endpoint without
  55. them; if the extra schemas cost you more context than the routing is worth,
  56. connect to the full gateway once rather than to several pack endpoints.
  57. Or connect to the full Pipeworx gateway to get every pack's tools listed
  58. directly, instead of just this one's:
  59. ```json
  60. {
  61. "mcpServers": {
  62. "pipeworx": {
  63. "url": "https://gateway.pipeworx.io/mcp"
  64. }
  65. }
  66. }
  67. ```
  68. Both URLs reach the same gateway and the same 2024+ data sources. The
  69. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  70. reaches all of them from either one.
  71. ## No MCP client? Call it over HTTP
  72. ```bash
  73. curl -X POST https://gateway.pipeworx.io/v1/tools/uk_gc_actions_list \
  74. -H 'Content-Type: application/json' \
  75. -d '{"name":"Grosvenor"}'
  76. ```
  77. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/uk_gc_actions_list`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  78. ## Run it from npm
  79. `@pipeworx/mcp-uk-gc-actions` is a local stdio bridge to the Pipeworx gateway: your MCP client
  80. starts it with `npx`, and it forwards every call to the same
  81. `https://gateway.pipeworx.io/uk-gc-actions/mcp` endpoint shown above. It needs network access;
  82. there is no offline mode.
  83. ```json
  84. {
  85. "mcpServers": {
  86. "uk-gc-actions": {
  87. "command": "npx",
  88. "args": ["-y", "@pipeworx/mcp-uk-gc-actions"]
  89. }
  90. }
  91. }
  92. ```
  93. Without a key it calls anonymously, capped at 50 calls a day. A free account
  94. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  95. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  96. The key is sent as a Bearer token, the same way a hosted connection sends it,
  97. so calls are metered and billed exactly as they are there.
  98. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  99. also list `ask_pipeworx` and the other gateway-wide tools.
  100. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  101. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  102. your Node version's documentation.
  103. ## Using with ask_pipeworx
  104. Instead of calling tools directly, you can ask questions in plain English —
  105. this works on the pack endpoint above as well as on the full gateway:
  106. ```
  107. ask_pipeworx({ question: "your question about Uk Gc Actions data" })
  108. ```
  109. The gateway picks the right tool and fills the arguments automatically.
  110. ## More
  111. - [Docs and guides](https://pipeworx.io/docs)
  112. - [pipeworx.io](https://pipeworx.io)
  113. ## License
  114. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

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