Remote MCP · Endpoint

Codex Contaminants MCP server

No. Codex Contaminants answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/codex-contaminants/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/codex-contaminants
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
42 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Codex Alimentarius CXS 193 — maximum levels for contaminants and toxins in
Website
https://pipeworx.io/packs/codex-contaminants
Repository
https://github.com/pipeworx-io/mcp-codex-contaminants
Listing
From the official MCP registry (active).
Recent checks of Codex Contaminants
CheckedResultHandshake
1 day agoHandshake completed52 ms
4 days agoHandshake completed53 ms
5 days agoHandshake completed47 ms
7 days agoHandshake completed91 ms
8 days agoHandshake completed54 ms
9 days agoHandshake completed48 ms
12 days agoHandshake completed180 ms
13 days agoHandshake completed38 ms
15 days agoHandshake completed58 ms
16 days agoHandshake completed50 ms
18 days agoHandshake completed43 ms
19 days agoHandshake completed41 ms
20 days agoHandshake completed44 ms
20 days agoHandshake completed41 ms
21 days agoHandshake completed37 ms
23 days agoHandshake completed49 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Codex Contaminants and makes no claim about it beyond what these checks measured.