Codex Gsfa
NPM · @PIPEWORX/MCP-CODEX-GSFA · 2 COMPONENTS
Codex GSFA — the FAO/WHO General Standard for Food Additives (CXS 192-1995).
Available components
Last scanned (9 hours ago)
Scores higher than 81% of npm servers
Category Health and Science
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-codex-gsfa). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 31 Oct 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-codex-gsfa@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-codex-gsfa |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-codex-gsfa/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612156481 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7fd3af1130232c31e97ae9058131868fbbddc9dbe077beb978ce57b4d41753874005ee3d815bd37db26c99dca327af920ea13ecd0c5efd1b6d1d541c0 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gsfa_additive_provisions ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| additive | string | yes | 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. |
No output schema declared.
No examples provided.
gsfa_check_use ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| additive | string | yes | INS number, name, or synonym — e.g. "461", "methyl cellulose". |
| food_category | string | yes | GSFA food category number ("13.2") or its name ("complementary foods for infants") — both work. Subcategories inherit parent provisions. |
No output schema declared.
No examples provided.
gsfa_coverage ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gsfa_food_category_additives ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| food_category | string | yes | 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). |
No output schema declared.
No examples provided.
gsfa_notes ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
gsfa_search_additive ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results (default 20). |
| query | string | yes | INS number, additive name, or synonym. |
No output schema declared.
No examples provided.
gsfa_search_food_categories ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results (default 50). |
| query | string | yes | Category number prefix or words from the category name. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-codex-gsfa
claude mcp add pipeworx-io-codex-gsfa -- npx -y @pipeworx/mcp-codex-gsfa
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.