Eu Pesticides

@pipeworx/eu-pesticides

EU approval status of pesticide (plant-protection) active substances: whether a substance is Approved, Not approved or Pending, from when to when, and under which Commission regulation, with the ADI / ARfD / AOEL reference values.

Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• eu_pesticide_substance({ name | cas | id }) — one substance's full approval record: status, an explicit approval_state (an "Approved" entry whose expiry date has passed is returned as approved_but_expiry_date_passed, never as current), first-approval date, expiry date, the governing regulations and directives with links (the answer to "was it renewed, under which implementing regulation"), rapporteur member state, candidate-for-substitution and low-risk flags, ADI / ARfD / AOEL, CLP classification, national authorisations and MRL residue definitions.
• eu_pesticides_list({ status?, expiring_before?, expiring_after?, category?, candidate_for_substitution?, low_risk?, query?, limit?, offset? }) — filter the whole list, e.g. every approval expiring before a date.

Every response carries source and data_as_of.

Auth

Keyless.

Data sources

• European Commission (DG SANTE), EU Pesticides Database, active substances.

approval_date_first is the date of first approval, not of the latest renewal; renewals and extensions appear as additional entries in governing_legislation. Where the publisher lists different expiry dates for different uses of one entry (paraffin oil, famoxadone), expiry_date is the earliest and every value is in expiry_date_variants.

The publisher serves this list in many sequential pages with unreliable server-side filters, so the pack answers from a dated snapshot that is re-read monthly by a scheduled job; data_as_of is the snapshot date. For a legally binding answer confirm against EUR-Lex.

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/eu-pesticides/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 1879+ 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/eu_pesticide_substance \
  -H 'Content-Type: application/json' \
  -d '{"name":"dimethachlor"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/eu_pesticide_substance. 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": {
    "eu-pesticides": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-eu-pesticides"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-eu-pesticides

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 Eu Pesticides data" })

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

More

• Docs and guides
• pipeworx.io

License

MIT