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
Markdown
[](/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
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
- # @pipeworx/uk-ea-enforcement
- Has the Environment Agency taken enforcement action against this company:
- a prosecution, a caution, an enforcement undertaking, a penalty or a notice?
- 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.
- ## Tools
- - `uk_ea_enforcement_list(name?, start?, count?)` — enforcement actions in England,
- by organisation name or words from it, newest first; with no name, in the
- publisher's own order. Each row carries the action id, date, organisation, its
- postcode, action type, agency function (waste, water quality and so on) and the
- legislation. Returns `result` (`rows`, `no_action_found`, `beyond_last_page`,
- `only_individuals_on_this_page`), `rows_read`, `individuals_dropped`, `next_start`
- and `data_as_of`.
- - `uk_ea_enforcement_read(id)` — one action in full: the organisation and company
- number, the incident site area, each offence with its legislation, environmental
- impact on air, land and water, and the penalty (fine and costs in pounds), and
- the total of fines.
- ## Auth
- Keyless.
- ## Data sources
- - Environment Agency, enforcement actions, published under the Environment Agency
- Conditional Licence. Read from the publisher on request, one page of the
- publisher's own paging per call. `data_as_of` is the day of the read.
- ## Behaviour worth knowing
- - Organisations only. The data holds sole traders and private individuals as
- offenders. A row is served only when the name carries a legal form (Limited, Ltd,
- LLP, PLC, ...) or names a public or collective body (Council, Authority, Trust,
- Association, ...) and is not a "trading as" name. Every other row is dropped and
- counted in `individuals_dropped`. The test is strict: a company with an unusual
- name can be dropped, which is why the count is returned.
- - Street addresses of offenders are not returned; only the locality and postcode.
- - `no_action_found` means the publisher data was read and holds no action for this
- name; it is not a clearance of a company. A rate-limit answer or a failed read
- throws instead of reading as no action.
- ## Quick Start
- Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
- ```json
- {
- "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:
- ```json
- {
- "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.
- ## No MCP client? Call it over HTTP
- ```bash
- curl -X POST https://gateway.pipeworx.io/v1/tools/uk_ea_enforcement_list \
- -H 'Content-Type: application/json' \
- -d '{"name":"Severn Trent"}'
- ```
- 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":"..."}`.
- ## Run it from npm
- `@pipeworx/mcp-uk-ea-enforcement` is a local stdio bridge to the Pipeworx gateway: your MCP client
- starts it with `npx`, and it forwards every call to the same
- `https://gateway.pipeworx.io/uk-ea-enforcement/mcp` endpoint shown above. It needs network access;
- there is no offline mode.
- ```json
- {
- "mcpServers": {
- "uk-ea-enforcement": {
- "command": "npx",
- "args": ["-y", "@pipeworx/mcp-uk-ea-enforcement"]
- }
- }
- }
- ```
- Without a key it calls anonymously, capped at 50 calls a day. A free account
- raises that to 200 a day: get a key at https://pipeworx.io/signup and add
- `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
- The key is sent as a Bearer token, the same way a hosted connection sends it,
- so calls are metered and billed exactly as they are there.
- It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
- also list `ask_pipeworx` and the other gateway-wide tools.
- Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
- default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
- your Node version's documentation.
- ## 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 Ea Enforcement data" })
- ```
- The gateway picks the right tool and fills the arguments automatically.
- ## More
- - [Docs and guides](https://pipeworx.io/docs)
- - [pipeworx.io](https://pipeworx.io)
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.