Skip to main content
Glama

Server Details

Food additive regulations of Japan, the EU and the US, side by side, with sources (free tier).

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct action: label analysis, substance search, and substance detail, with the _diff variants clearly flagged as the paid/cross-axis counterparts. The boundary between analyze_label/get_substance and their _diff siblings is well explained, though having two tools that only return an HTTP endpoint rather than data can still mislead an agent.

Naming Consistency5/5

Names follow a clean verb_noun pattern (analyze_label, get_substance, search_substances) with a consistent _diff suffix marking the paid variants. No mixing of conventions.

Tool Count3/5

Five tools is a reasonable count on paper, but two of them (analyze_label_diff, get_substance_diff) are non-functional stubs that only redirect to HTTP, leaving just three usable tools. For a multi-axis regulatory data domain that feels thin.

Completeness3/5

Core read paths are covered (search, get one substance, analyze a label including interactions), but there is no way to list or browse substances, explore categories/groups directly, or query interactions outside of label analysis. Cross-axis comparison is only reachable via paid HTTP, a notable gap.

Available Tools

5 tools
analyze_labelFind the additives named on a labelA
Read-only
Inspect

Find the additives named on a label (same as HTTP POST /v1/labels/analyze). Splits the additive section into tokens and returns, per token, the substances it resolves to (SubstanceSummary: facts on their own axis), plus known interactions between the detected substances. Cutting the additive section out of the label is the caller's job; sending the whole ingredient section is allowed. Matching is exact against the alias vocabulary in scope: a token with matches: [] is unresolved, which (open world) does not distinguish "not an additive" from "an additive not known here". axis and lang must be one of the accepted pairs: JP+ja, US+en, EU+nl, EU+fr, EU+de, EU+es, EU+pl, EU+el, EU+bg. Not a safety judgement: every record is a draft and needs verification.

Inputs: axis (required), lang (required), text (required).

analyze_label_diffFind the additives named on a label, with the cross-axis derivation (paid, HTTP only)A
Read-only
Inspect

(Paid; not available through MCP.) Same input as analyze_label, but each detected substance carries the cross-axis derivation. This tool does not return that data: it returns the HTTP endpoint (POST /v1/labels/analyze/diff with the same JSON body, 0.01 USDC per request via x402 on Base) to call instead.

Inputs: axis (required), lang (required), text (required).

get_substanceOne substance, with everything its own roster saysA
Read-only
Inspect

One substance with everything its own roster says (same as HTTP GET /v1/substances/{id}): identifiers, category, aliases, translations, the source-ledger row, groups, and — depending on the axis — Japanese use standards, EU/Codex conditions of use, mandatory labelling statements, the roster's definition text or the CFR citation. Facts from the substance's own axis only; nothing here crosses an axis (that is get_substance_diff, paid, HTTP only). Axis-specific keys are present only where the roster has that concept, and an empty list means something (use_standards: [] = no use standard; use_conditions: [] = no permitted food category). Not a safety judgement: every record is a draft and needs verification.

Inputs: id (required).

get_substance_diffOne substance, with the cross-axis derivation (paid, HTTP only)A
Read-only
Inspect

(Paid; not available through MCP.) For every axis other than the substance's own, what that axis says (with a per-cell source) kept separate from what was derived from it; when nothing can be concluded, a refusal says why and what would settle it. This tool does not return that data: it returns the HTTP endpoint (GET /v1/substances/{id}/diff, 0.01 USDC per request via x402 on Base) to call instead.

Inputs: id (required).

search_substancesLook up substances by nameA
Read-only
Inspect

Look up substances by name on one regulatory axis (same as HTTP GET /v1/substances?name=…). The name is normalised (NFKC, whitespace removed, lower-cased) and matched exactly against the names and aliases the axis itself uses in that language (E numbers and official names for EU, 品目名 and label terms for JP, CFR names for US) — no partial or fuzzy matching. The official name is an alias of itself. Returns the matching substances (SubstanceSummary: facts from their own roster only) and, per row, what text matched. axis and lang must be one of the accepted pairs: JP+ja, US+en, EU+nl, EU+fr, EU+de, EU+es, EU+pl, EU+el, EU+bg. Not a safety judgement: every record is a draft and needs verification.

Inputs: axis (required), lang (required), name (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • 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.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for Japanese food nutrition data, enabling bilingual JP/EN lookups across konbini, restaurant chains, and grocery brands.
      6
      107 npm
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources