Eu Pesticides
NPM · @PIPEWORX/MCP-EU-PESTICIDES · 2 COMPONENTS
eu-pesticides -- EU approval status of pesticide active substances.
Available components
Last scanned (8 hours ago)
Scores higher than 69% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-eu-pesticides). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 597 tokens (~298/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-eu-pesticides@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-eu-pesticides |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-eu-pesticides/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635931842 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1ac31cfcd6c60f7359f6d7959d5fa350413d639dc6a7698761a56b299bd0c6698006a2ac76302402d3319a0e550dc44936cc4739226ad951fc4ab7a2b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
eu_pesticide_substance ~241
EU approval record for one pesticide (plant-protection) active substance from the European Commission EU Pesticides Database: approval status (Approved / Not approved / Pending), an explicit approval_state that flags an Approved entry whose expiry date has already passed, first-approval date, expiry date, the governing Commission regulations and directives (links to EUR-Lex; this is how to see whether and under which implementing regulation an approval was renewed or extended), rapporteur member state, candidate-for-substitution and low-risk flags, ADI / ARfD / AOEL reference values, CLP classification, national authorisations and MRL residue definitions. Look up by name (exact, then partial), CAS number or substance id. Returns data_as_of with every answer. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| cas | string | – | CAS number, e.g. "50563-36-5". |
| id | number | – | EU Pesticides Database substance id. |
| name | string | – | Active substance name, e.g. "dimethachlor", "glyphosate", "chlorpyrifos". Exact match preferred; otherwise partial matches are listed. |
No output schema declared.
No examples provided.
eu_pesticides_list ~299
List EU pesticide active substances by approval status and dates -- e.g. approvals expiring before a date (expiring_before), all substances still Approved, Not approved, or Pending, candidates for substitution, low-risk substances, or one category (fungicide, herbicide, insecticide...). Each row carries status, approval_state (flags Approved entries whose expiry date has passed), first-approval date and expiry date. Sorted by expiry date for date filters, otherwise by name. Source: European Commission EU Pesticides Database; data_as_of in every answer. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_for_substitution | boolean | – | Only substances flagged as candidates for substitution. |
| category | string | – | Substance category text, e.g. "fungicide", "herbicide", "insecticide", "plant growth regulator". |
| expiring_after | string | – | ISO date YYYY-MM-DD: only substances whose expiry date is on or after it. |
| expiring_before | string | – | ISO date YYYY-MM-DD: only Approved substances whose expiry date is on or before it (includes ones already lapsed). |
| limit | number | – | Rows to return (default 25, max 200). |
| low_risk | boolean | – | Only low-risk active substances. |
| offset | number | – | Rows to skip, for paging. |
| query | string | – | Substring of the substance name. |
| status | string | – | Approval status filter. |
No output schema declared.
No examples provided.
How do I install the Eu Pesticides MCP server?
Eu Pesticides runs locally as an npm package, launched with npx -y @pipeworx/mcp-eu-pesticides. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-eu-pesticides
claude mcp add pipeworx-io-eu-pesticides -- npx -y @pipeworx/mcp-eu-pesticides
What is the Eu Pesticides MCP server?
Eu Pesticides is an MCP server listed in the public MCP registry as io.github.pipeworx-io/eu-pesticides. eu-pesticides -- EU approval status of pesticide active substances. This page covers its npm package (@pipeworx/mcp-eu-pesticides).
Is the Eu Pesticides MCP server safe to use?
Eu Pesticides scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Eu Pesticides MCP server expose?
Eu Pesticides exposes 2 tools: eu_pesticide_substance, eu_pesticides_list. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.
Is the Eu Pesticides MCP server still maintained?
Eu Pesticides is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Eu Pesticides MCP server under?
Eu Pesticides declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.