Skip to content
Back to search

mcp-uk-ea-enforcement

uk-ea-enforcement -- the Environment Agency's published enforcement actions in England: prosecutions (court cases), cautions, enforcement undertakings, fixed and variable monetary penalties, warning letters and notices issued against companies and other bodies for waste, water-quality, pollution…

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

HTML

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

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/uk-ea-enforcement/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 · 152 lines
  1. # @pipeworx/uk-ea-enforcement
  2. Has the Environment Agency taken enforcement action against this company:
  3. a prosecution, a caution, an enforcement undertaking, a penalty or a notice?
  4. 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.
  5. ## Tools
  6. - `uk_ea_enforcement_list(name?, start?, count?)` — enforcement actions in England,
  7. by organisation name or words from it, newest first; with no name, in the
  8. publisher's own order. Each row carries the action id, date, organisation, its
  9. postcode, action type, agency function (waste, water quality and so on) and the
  10. legislation. Returns `result` (`rows`, `no_action_found`, `beyond_last_page`,
  11. `only_individuals_on_this_page`), `rows_read`, `individuals_dropped`, `next_start`
  12. and `data_as_of`.
  13. - `uk_ea_enforcement_read(id)` — one action in full: the organisation and company
  14. number, the incident site area, each offence with its legislation, environmental
  15. impact on air, land and water, and the penalty (fine and costs in pounds), and
  16. the total of fines.
  17. ## Auth
  18. Keyless.
  19. ## Data sources
  20. - Environment Agency, enforcement actions, published under the Environment Agency
  21. Conditional Licence. Read from the publisher on request, one page of the
  22. publisher's own paging per call. `data_as_of` is the day of the read.
  23. ## Behaviour worth knowing
  24. - Organisations only. The data holds sole traders and private individuals as
  25. offenders. A row is served only when the name carries a legal form (Limited, Ltd,
  26. LLP, PLC, ...) or names a public or collective body (Council, Authority, Trust,
  27. Association, ...) and is not a "trading as" name. Every other row is dropped and
  28. counted in `individuals_dropped`. The test is strict: a company with an unusual
  29. name can be dropped, which is why the count is returned.
  30. - Street addresses of offenders are not returned; only the locality and postcode.
  31. - `no_action_found` means the publisher data was read and holds no action for this
  32. name; it is not a clearance of a company. A rate-limit answer or a failed read
  33. throws instead of reading as no action.
  34. ## Quick Start
  35. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  36. ```json
  37. {
  38. "mcpServers": {
  39. "uk-ea-enforcement": {
  40. "url": "https://gateway.pipeworx.io/uk-ea-enforcement/mcp"
  41. }
  42. }
  43. }
  44. ```
  45. ### What this endpoint actually serves
  46. `tools/list` at `https://gateway.pipeworx.io/uk-ea-enforcement/mcp` returns the tools in the table
  47. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  48. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  49. gateway-wide set. So the tool count you see is larger than this table: a
  50. single-pack endpoint currently lists roughly 30 shared tools alongside the
  51. pack's own. The connection's `initialize` response states its exact scope, and
  52. is the authoritative answer for a given day.
  53. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  54. scoped connection answer a question this pack does not cover — via
  55. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  56. second MCP server. There is currently no way to mount a pack endpoint without
  57. them; if the extra schemas cost you more context than the routing is worth,
  58. connect to the full gateway once rather than to several pack endpoints.
  59. Or connect to the full Pipeworx gateway to get every pack's tools listed
  60. directly, instead of just this one's:
  61. ```json
  62. {
  63. "mcpServers": {
  64. "pipeworx": {
  65. "url": "https://gateway.pipeworx.io/mcp"
  66. }
  67. }
  68. }
  69. ```
  70. Both URLs reach the same gateway and the same 2024+ data sources. The
  71. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  72. reaches all of them from either one.
  73. ## No MCP client? Call it over HTTP
  74. ```bash
  75. curl -X POST https://gateway.pipeworx.io/v1/tools/uk_ea_enforcement_list \
  76. -H 'Content-Type: application/json' \
  77. -d '{"name":"Severn Trent"}'
  78. ```
  79. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/uk_ea_enforcement_list`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  80. ## Run it from npm
  81. `@pipeworx/mcp-uk-ea-enforcement` is a local stdio bridge to the Pipeworx gateway: your MCP client
  82. starts it with `npx`, and it forwards every call to the same
  83. `https://gateway.pipeworx.io/uk-ea-enforcement/mcp` endpoint shown above. It needs network access;
  84. there is no offline mode.
  85. ```json
  86. {
  87. "mcpServers": {
  88. "uk-ea-enforcement": {
  89. "command": "npx",
  90. "args": ["-y", "@pipeworx/mcp-uk-ea-enforcement"]
  91. }
  92. }
  93. }
  94. ```
  95. Without a key it calls anonymously, capped at 50 calls a day. A free account
  96. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  97. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  98. The key is sent as a Bearer token, the same way a hosted connection sends it,
  99. so calls are metered and billed exactly as they are there.
  100. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  101. also list `ask_pipeworx` and the other gateway-wide tools.
  102. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  103. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  104. your Node version's documentation.
  105. ## Using with ask_pipeworx
  106. Instead of calling tools directly, you can ask questions in plain English —
  107. this works on the pack endpoint above as well as on the full gateway:
  108. ```
  109. ask_pipeworx({ question: "your question about Uk Ea Enforcement data" })
  110. ```
  111. The gateway picks the right tool and fills the arguments automatically.
  112. ## More
  113. - [Docs and guides](https://pipeworx.io/docs)
  114. - [pipeworx.io](https://pipeworx.io)
  115. ## License
  116. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

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