Skip to main content
Glama

Codex Contaminants

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Codex Alimentarius CXS 193 — maximum levels for contaminants and toxins in

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.2% over 23 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-codex-contaminants
GitHub Stars
0
Server Listing
codex-contaminants

TDQS

A3.7/5.0

Scored across 38 tools

Disambiguation3/5

Several tool families blur together: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are effectively three variants of the same universal router—beta is identical with an experimental routing prompt, and grounded adds an extraction pass—so an agent could easily misselect between them. Similarly, ai_visibility_check and scan_competitor_ai_presence are single-vs-batch versions of the same probe, and polymarket_arbitrage, polymarket_edges, and polymarket_edge_tracker all hunt for prediction-market opportunities with tight boundaries. Most other tools (memory trio, subscription lifecycle, resolution pair) are clearly distinct.

Naming Consistency4/5

The set is uniformly snake_case and follows recognizable families: ask_pipeworx* variants, polymarket_* prefixed tools, contaminants_* pair, resolution_audit/diff, subscribe/unsubscribe/list_subscriptions, and the remember/recall/forget trio. There is minor stylistic drift—some tools are verb_noun (resolve_entity, validate_claim, scan_dependency) while others are bare noun phrases (entity_profile, company_facts, bet_research, polymarket_arbitrage)—but the deviations are small and patterns remain predictable.

Tool Count2/5

38 tools is well into the heavy range, and the sprawl reflects a genuine scope problem: the server is named 'Codex Contaminants' but only 2 of its 38 tools concern that domain, with the rest forming a general-purpose Pipeworx data router, a prediction-market analytics suite, AI-visibility checks, an npm dependency scanner, llms.txt generation, and memory/subscription plumbing. The count would be defensible if tools were tightly scoped to one domain, but here it reads as a kitchen sink that no agent could easily navigate as a coherent set.

Completeness2/5

For the domain implied by the server name, coverage is thin: the two Codex contaminant tools are inverse query directions (by commodity vs by contaminant) but there is no tool to enumerate all regulated commodities, list all contaminants, explain the standard, or fetch the relevant CXS 193 context beyond maximum levels. For the actual sprawling surface, most lifecycle arcs are covered (subscriptions, memory, resolution checks) but the prediction-market tools lack a direct 'get single market quote' primitive and several description cross-references (get_company_financials, kalshi_market, polymarket_market) point at tools not present in this set.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Changeddeep_research8 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / input
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / prompt
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / q
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / query
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases."
      • addedInput schema / properties / text
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • Changedforget4 fields changed
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
    • Changedrecall4 fields changed
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
    • Changedremember9 fields changed
      • addedInput schema / properties / content
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / data
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / text
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / v
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • changedInput schema / properties / value / description
        Previous value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."
  2. 3 tool updates
    • Changedask_pipeworx3 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
    • Changedask_pipeworx_beta3 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
    • Changedask_pipeworx_grounded3 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
  3. 38 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observedcontaminants_for_commodity
    • First observedcontaminants_max_levels
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • mcp-codex-mrl

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides access to Codex Alimentarius maximum residue limits, enabling searches for pesticide and veterinary drug limits by substance or food commodity, including adoption status and JECFA cross-references.
    245 npm
    MIT

  • heathy-mcp

    Chandata
    A
    license
    Not graded
    quality
    B
    maintenance
    Heathy.org exists because nature never printed a nutrition label. Every processed snack on the shelf comes with a panel of numbers — the fruit and veg next to it, the food actually worth eating, comes with nothing. We give you the real, vetted picture, not one source's blind spot
    MIT

  • codex-gsfa

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables querying the Codex General Standard for Food Additives to check whether an additive is permitted in a food category, at what maximum level or GMP, and under which conditions.
    271 npm
    MIT

  • food-safety-mcp

    rootsbymenda
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables checking food additive safety, nutrition profiles, pesticide residues, and ingredient lists with regulatory flags and dietary compatibility. All data is sourced from authoritative bodies like JECFA, EFSA, and FDA.
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources