Jmpr
NPM · @PIPEWORX/MCP-JMPR · 2 COMPONENTS
JMPR — the Joint FAO/WHO Meeting on Pesticide Residues.
Available components
Last scanned (2 hours ago)
Scores higher than 81% 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-jmpr). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 356 tokens (~118/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
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-jmpr@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-jmpr |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-jmpr/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649488385 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e695eba5f9dbf0f03badb3c115697c11879236161c665c59132a328dc4872b53ac3f941ae868588b0b7720e3cb0ff51e52ffc5d16ba645d1190f34ccc |
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 →
jmpr_chemical ~141
Get the full JMPR safety evaluation for one pesticide: its Acceptable Daily Intake (ADI) and Acute Reference Dose (ARfD) in mg/kg body weight, the year each was set, the meeting's conclusions, its CAS number, chemical class and pesticide use type, plus links to the JMPR reports and monographs. Use to answer how much of a pesticide is considered safe to consume daily, or why a value was withdrawn or never set.
| Name | Type | Req | Description |
|---|---|---|---|
| pesticide | string | yes | Pesticide name as JMPR spells it, e.g. "CHLORPYRIFOS". Case-insensitive; get it from jmpr_search. |
No output schema declared.
No examples provided.
jmpr_list_pesticides ~67
List every pesticide the FAO/WHO Joint Meeting on Pesticide Residues has evaluated. Use to survey coverage or to check whether a substance has ever been assessed at all — absence means JMPR has not evaluated it, which is different from it having no safe level.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jmpr_search ~96
Find pesticides evaluated by the FAO/WHO Joint Meeting on Pesticide Residues (JMPR) by name or partial name. Returns matching pesticide names, which are the identifier used to fetch a full safety evaluation. Use when you have a pesticide name and want its toxicological assessment.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Pesticide name or fragment, e.g. "chlorpyrifos" or "pyrethr". |
No output schema declared.
No examples provided.
How do I install the Jmpr MCP server?
Jmpr runs locally as an npm package, launched with npx -y @pipeworx/mcp-jmpr. 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-jmpr
claude mcp add pipeworx-io-jmpr -- npx -y @pipeworx/mcp-jmpr
What is the Jmpr MCP server?
Jmpr is an MCP server listed in the public MCP registry as io.github.pipeworx-io/jmpr. JMPR, the Joint FAO/WHO Meeting on Pesticide Residues. This page covers its npm package (@pipeworx/mcp-jmpr).
Is the Jmpr MCP server safe to use?
Jmpr scores 84 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 Jmpr MCP server expose?
Jmpr exposes 3 tools: jmpr_search, jmpr_chemical, jmpr_list_pesticides. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Is the Jmpr MCP server still maintained?
Jmpr 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 Jmpr MCP server under?
Jmpr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.