# Jmpr (npm · @pipeworx/mcp-jmpr)

JMPR — the Joint FAO/WHO Meeting on Pesticide Residues.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-jmpr/jmpr-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-jmpr/jmpr-mcp)
- npm · `@pipeworx/mcp-jmpr`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-jmpr/pipeworx-mcp-jmpr.md), [page](https://verifymcp.io/servers/pipeworx-io-jmpr/pipeworx-mcp-jmpr)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-jmpr`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jmpr).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 356 tokens (~118/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-jmpr -- npx -y @pipeworx/mcp-jmpr
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-jmpr": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jmpr"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-jmpr": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jmpr"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-jmpr -- npx -y @pipeworx/mcp-jmpr
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-jmpr": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-jmpr"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-jmpr --command npx --arg -y --arg @pipeworx/mcp-jmpr
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-jmpr:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-jmpr"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-jmpr": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-jmpr"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-jmpr -t stdio -c npx -a -y @pipeworx/mcp-jmpr
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-jmpr": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jmpr"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 68, −13)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 81, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (3)

### `jmpr_search` (~96 tokens)

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.

Input parameters:

- `query` (string, required): Pesticide name or fragment, e.g. "chlorpyrifos" or "pyrethr".

### `jmpr_chemical` (~141 tokens)

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.

Input parameters:

- `pesticide` (string, required): Pesticide name as JMPR spells it, e.g. "CHLORPYRIFOS". Case-insensitive; get it from jmpr_search.

### `jmpr_list_pesticides` (~67 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-jmpr/pipeworx-mcp-jmpr#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 68
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-jmpr
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-jmpr
- Repository: https://github.com/pipeworx-io/mcp-jmpr
- Website: https://pipeworx.io/packs/jmpr
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-jmpr/pipeworx-mcp-jmpr.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-jmpr/pipeworx-mcp-jmpr.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-jmpr/pipeworx-mcp-jmpr