
Codex Contaminants MCP server
online · 100% uptimeCodex Alimentarius CXS 193 — maximum levels for contaminants and toxins in food and feed: lead…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Codex Contaminants yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Codex Contaminants tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Codex Contaminants compares
Against every graded Sales and outbound MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 876 Sales and outbound servers
- Uptime
- 100%
- of our recent checks; the typical remote Sales and outbound server answers 100%
- Response time
- 192 ms
- faster than 70% of 671 Sales and outbound servers
Release history: 4 versions in the registry since 2026-09-16, latest 2026-10-31, typically one every 8 days.
Install Codex Contaminants in Claude Code, Cursor or VS Code
claude mcp add --transport http codex-contaminants https://gateway.pipeworx.io/codex-contaminants/mcp
What the publisher says
From the Codex Contaminants repository's README, as published. We do not edit it. Read it on GitHub
codex-contaminants
Codex Alimentarius CXS 193-1995 maximum levels for contaminants and toxins in food — lead, cadmium, arsenic, mercury, methylmercury, tin, aflatoxins, ochratoxin A, patulin, melamine, hydrocyanic acid — by commodity.
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
59 maximum levels, 2015 edition. Both of those numbers are limitations, and both are stated on every response rather than left in this file.
Read this before using a value
Edition. Codex publishes CXS 193 only as a document, and the current text is behind an authenticated FAO workspace. This pack carries the newest public official edition, 2015 (Amended in 2010, 2012, 2013, 2014, 2015). The standard has been amended in 2016, 2017, 2018, 2019, 2021, 2022, 2023, and at CAC47 (Nov
cinnamon (2.5 mg/kg) and dried culinary herbs (2.0 mg/kg) among them.
- and CAC48 (Nov 2025). Those amendments added maximum levels — lead in
Coverage. 59 entries from the Schedule I tables. Rows whose commodity name wraps across table lines were dropped rather than risk labelling a legal limit with a sentence fragment like "exception of berries".
Together: a miss is not a finding that no limit exists. The not-found path says so in words, because "no maximum level" reads as permission.
Every value carries the source PDF page, so any figure can be checked in one step against .
Tools
contaminant, optionally narrowed to a food.
- contaminantsmaxlevels({contaminant, commodity?}) — Codex MLs for a
applies to one food.
- contaminantsforcommodity({commodity}) — every contaminant limit that
Extraction, and what went wrong four times
extract.py is the extractor. It is column-band driven for a reason: each of these was a real, silent failure during the build, and the tests pin all of them.
page and 29 on the next, so fixed slicing attaches a real limit to a truncated commodity name.
- Character offsets do not work. The ML column sits at character 36 on one
number), 25 (the withdrawn PTWI in µg/kg body weight) and 3 (3 mmHg of blood pressure) as maximum levels. Fixed by taking the ML column's x-band from each page's table header and accepting only numbers inside it.
- Reading any number on the page swept in, under LEAD, 73 (a JECFA meeting
unit is read from the header too. Hardcoding mg/kg made aflatoxin M1 in milk read 0.5 mg/kg instead of 0.5 µg/kg: wrong by 1000×.
- Units differ per contaminant — aflatoxins are µg/kg, metals mg/kg. The
says DEOXYNIVALENOL (DON), and a 3-letter heading TIN is easy to filter out by accident — when it was, tin's canned-meat limits (50 mg/kg) were filed under methylmercury.
- Section headings must come from the document, not memory. The standard
To refresh: point extract.py at a newer PDF, re-run, and read the output before shipping it. The tables are small enough that a human check pass is feasible, and for legal limits it is not optional.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"codex-contaminants": {
"url": "https://gateway.pipeworx.io/codex-contaminants/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/codex-contaminants/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, 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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Codex Contaminants: common questions
- Is Codex Contaminants MCP server safe?
- Mostly: it is graded B (77/100). Read the Codex Contaminants safety report
- How do I install Codex Contaminants?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Codex Contaminants need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Codex Contaminants maintained?
- The last commit was 40 days ago (2026-09-24). The latest release is v0.2.1.
- Is Codex Contaminants up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Codex Contaminants?
- Servers from other publishers that do the same job: Vibe Prospecting MCP server, OpenLeads MCP server and Salesforce MCP server.
- How does Codex Contaminants compare with other Sales and outbound MCP servers?
- safety score 77/100 (higher than 50% of 876 Sales and outbound servers); uptime 100% (of our recent checks; the typical remote Sales and outbound server answers 100%); response time 192 ms (faster than 70% of 671 Sales and outbound servers). Full comparison.
Alternatives to Codex Contaminants
Same job from other publishers: the closest match first, then the best rated.
- Vibe ProspectingB2B company and contact data for lead lists, enrichment, research, and outreach. OAuth sign-in.not reviewedEstablishedA
- OpenLeadsFind leads with honest email evidence, then work them: CRM, sequences, tasks, deals. No API keys.not reviewedGrowingA
- SalesforceSalesforce CRM MCP server: accounts, contacts, opportunities, leads, tasks, and custom objectsnot reviewedGrowingA
LeadbayAI lead discovery, qualification, and outreach prep on your Leadbay account.not reviewedGrowingA- Rd StationMCP server for RD Station — contacts, events, funnels, deals, segmentations, lead scoring, webhooksnot reviewedGrowingB