Skip to content

Additive Atlas

by monon.space · remote · no sign-in to list tools · v0.1.0 · published by space.monon

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

Read only
CompareRegistry entry

5 tools: 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http additive-atlas https://api.additiveatlas.monon.space/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Only reads 5Claude Code: allow
  • analyze_labelFind the additives named on a label (same as HTTP POST /v1/labels/analyze).No findings

    Why it is in this group

    • The name "analyze_label" says "analyze": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • analyze_label_diff(Paid; not available through MCP.) Same input as analyze_label, but each detected substance carries the cross-axis derivation.No findings

    Why it is in this group

    • The name "analyze_label_diff" says "analyze": a word for reading.
    Description, as the server wrote it
    (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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_substanceOne substance with everything its own roster says (same as HTTP GET /v1/substances/{id}): identifiers, category, aliases, translations, the source-ledger row, groups, and — dependi…No findings

    Why it is in this group

    • The name "get_substance" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_substance_diff(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 not…No findings

    Why it is in this group

    • The name "get_substance_diff" says "get": a word for reading.
    Description, as the server wrote it
    (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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_substancesLook up substances by name on one regulatory axis (same as HTTP GET /v1/substances?name=…).No findings

    Why it is in this group

    • The name "search_substances" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http additive-atlas https://api.additiveatlas.monon.space/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__additive-atlas__search_substances",
      "mcp__additive-atlas__get_substance",
      "mcp__additive-atlas__analyze_label",
      "mcp__additive-atlas__get_substance_diff",
      "mcp__additive-atlas__analyze_label_diff"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as additive-atlas. Review it before you use it.