# Codex Contaminants (npm · @pipeworx/mcp-codex-contaminants)

Codex Alimentarius CXS 193 — maximum levels for contaminants and toxins in food and feed: lead…

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-codex-contaminants`
- 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-07.

- **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-codex-contaminants).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 345 tokens (~172/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Codex Contaminants MCP server?

Codex Contaminants runs locally as an npm package, launched with npx -y @pipeworx/mcp-codex-contaminants. 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-codex-contaminants -- npx -y @pipeworx/mcp-codex-contaminants
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-07 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-05 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

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

First indexed and scored.

## MCP tools (2)

### `contaminants_max_levels` (~193 tokens)

Codex Alimentarius maximum levels (MLs) for a contaminant in food — lead, cadmium, arsenic, mercury, methylmercury, tin, aflatoxins, ochratoxin A, patulin, melamine, hydrocyanic acid. Returns each commodity with its maximum level, the unit it is expressed in, and the page of CXS 193 it came from. Use for "what is the Codex limit for lead in fish" or "which foods have cadmium maximum levels".

Input parameters:

- `commodity` (string): Optional. Narrow to a commodity or food group, e.g. "rice", "fish", "milk", "vegetables".
- `contaminant` (string, required): Contaminant name, e.g. "lead", "cadmium", "aflatoxins", "methylmercury", "tin". Matched case-insensitively.

### `contaminants_for_commodity` (~93 tokens)

Every Codex maximum level that applies to one food — "which contaminant limits apply to rice", "what are the Codex limits for milk". Returns each contaminant with its maximum level and unit for that commodity, from CXS 193.

Input parameters:

- `commodity` (string, required): Food or commodity name, e.g. "rice", "fish", "milk", "cereal grains", "natural mineral waters".

## Diagnostics

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

## Score history

- 2026-11-07: 85
- 2026-11-06: 84
- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 66
- 2026-10-30: 81
- 2026-10-29: 80

## Common questions

### What is the Codex Contaminants MCP server?

Codex Contaminants is an MCP server listed in the public MCP registry as io.github.pipeworx-io/codex-contaminants. Codex Alimentarius CXS 193, maximum levels for contaminants and toxins in food and feed: lead… This page covers its npm package (@pipeworx/mcp-codex-contaminants).

### Is the Codex Contaminants MCP server safe to use?

Codex Contaminants scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 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 Codex Contaminants MCP server expose?

Codex Contaminants exposes 2 tools: contaminants_max_levels, contaminants_for_commodity. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.

### Is the Codex Contaminants MCP server still maintained?

Codex Contaminants is still listed as active in the MCP registry. We last reached this channel on 7 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 Codex Contaminants MCP server under?

Codex Contaminants declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Codex Contaminants MCP server?

VerifyMCP ran 16 checks on Codex Contaminants, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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