# Codex Gsfa (npm · @pipeworx/mcp-codex-gsfa)

Codex GSFA — the FAO/WHO General Standard for Food Additives (CXS 192-1995).

- 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`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-codex-gsfa/codex-gsfa-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-codex-gsfa/codex-gsfa-mcp)
- npm · `@pipeworx/mcp-codex-gsfa`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-codex-gsfa/pipeworx-mcp-codex-gsfa.md), [page](https://verifymcp.io/servers/pipeworx-io-codex-gsfa/pipeworx-mcp-codex-gsfa)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-codex-gsfa`
- 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-codex-gsfa).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 952 tokens (~136/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Gsfa MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 84, +1)

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

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

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

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

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-31 (score 56, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (7)

### `gsfa_check_use` (~184 tokens)

Answer whether a specific food additive is permitted in a specific food category under the Codex General Standard for Food Additives, and at what maximum level. Returns the maximum use level (a numeric limit such as 10,000 mg/kg, or GMP meaning good manufacturing practice), which GSFA table the permission comes from, the note references that condition it, and whether the permission was stated for that exact food category or inherited from a parent category. Use for questions about whether an additive is allowed in a food, legal use levels, and food additive compliance.

Input parameters:

- `additive` (string, required): INS number, name, or synonym — e.g. "461", "methyl cellulose".
- `food_category` (string, required): GSFA food category number ("13.2") or its name ("complementary foods for infants") — both work. Subcategories inherit parent provisions.

### `gsfa_search_additive` (~115 tokens)

Find food additives in the Codex GSFA by INS number, name, or synonym. Returns each match with its INS number, name, synonyms, technological functional classes (thickener, preservative, colour, and so on), and how many food-category provisions it holds. Use to resolve an additive name or E-number to its GSFA entry before looking up permitted uses.

Input parameters:

- `limit` (number): Maximum results (default 20).
- `query` (string, required): INS number, additive name, or synonym.

### `gsfa_additive_provisions` (~154 tokens)

List every food category in which a given food additive is permitted under the Codex GSFA, with the maximum use level for each. Separates Table 1 and 2 provisions (which carry a specific maximum level) from Table 3 provisions (permitted under good manufacturing practice with no numeric limit). Use to see the full permitted scope of one additive across all foods.

Input parameters:

- `additive` (string, required): INS number, name, or synonym — e.g. "415", "xanthan gum".
- `limit` (number): Maximum provisions returned (default 200).
- `table` (string): Filter to one table: "table1_2" or "table3". Omit for both.

### `gsfa_food_category_additives` (~128 tokens)

List every food additive permitted in a given Codex GSFA food category, with each maximum use level. Includes provisions inherited from parent categories, since a GSFA provision applies to a category and all of its subcategories. Use to see what additives may legally be used in a particular food.

Input parameters:

- `food_category` (string, required): GSFA food category number ("01.4.4") or its name ("cream analogues").
- `include_inherited` (boolean): Include provisions stated on parent categories (default true).
- `limit` (number): Maximum results (default 200).

### `gsfa_search_food_categories` (~96 tokens)

Search the Codex GSFA food category system by number or name — for example "cheese", "beverages", or "01.4". Returns matching category numbers and names. Use to find the right GSFA food category number before checking which additives are permitted in it.

Input parameters:

- `limit` (number): Maximum results (default 50).
- `query` (string, required): Category number prefix or words from the category name.

### `gsfa_notes` (~148 tokens)

Look up the qualifying notes that condition Codex GSFA food additive provisions. GSFA provisions are frequently limited by numbered notes such as "for use in ready-to-drink products only", "as sulphur dioxide", or "on the fat basis", and a maximum use level is not fully specified without them. Give note numbers to resolve, or a search term to find notes by their wording.

Input parameters:

- `limit` (number): Maximum results when searching (default 25).
- `note_ids` (array): Note numbers to resolve, e.g. [160, 273].
- `query` (string): Find notes whose text contains this wording, e.g. "sulphur dioxide".

### `gsfa_coverage` (~68 tokens)

Report what this Codex GSFA dataset contains and how current it is: the Codex Alimentarius Commission sessions represented, counts of additives, food categories and provisions, and which additive records could not be retrieved. Use to check the freshness and completeness of GSFA answers before relying on them.

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 56
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Codex Gsfa MCP server?

Codex Gsfa is an MCP server listed in the public MCP registry as io.github.pipeworx-io/codex-gsfa. Codex GSFA, the FAO/WHO General Standard for Food Additives (CXS 192-1995). This page covers its npm package (@pipeworx/mcp-codex-gsfa).

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

Codex Gsfa 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 Codex Gsfa MCP server expose?

Codex Gsfa exposes 7 tools: gsfa_check_use, gsfa_search_additive, gsfa_additive_provisions, gsfa_food_category_additives, gsfa_search_food_categories, and 2 more. Their descriptions and schemas cost roughly 893 tokens of context every time the server is loaded.

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

Codex Gsfa 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 Codex Gsfa MCP server under?

Codex Gsfa 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 Gsfa MCP server?

VerifyMCP ran 16 checks on Codex Gsfa, 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-gsfa
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-codex-gsfa
- Repository: https://github.com/pipeworx-io/mcp-codex-gsfa
- Website: https://pipeworx.io/packs/codex-gsfa
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-codex-gsfa/pipeworx-mcp-codex-gsfa.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-codex-gsfa/pipeworx-mcp-codex-gsfa/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-codex-gsfa/pipeworx-mcp-codex-gsfa.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-codex-gsfa/pipeworx-mcp-codex-gsfa