# Additive Atlas (remote · api.additiveatlas.monon.space)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `api.additiveatlas.monon.space`: 80/100 (this document), [markdown](https://verifymcp.io/servers/space-monon-additive-atlas/api.md), [page](https://verifymcp.io/servers/space-monon-additive-atlas/api)

## Channel facts

- Endpoint: `https://api.additiveatlas.monon.space/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-24.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1315 tokens (~263/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Additive Atlas MCP server?

Additive Atlas is a hosted endpoint at https://api.additiveatlas.monon.space/mcp, so there is nothing to install locally. 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 --transport http space-monon-additive-atlas 'https://api.additiveatlas.monon.space/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "space-monon-additive-atlas": {
      "url": "https://api.additiveatlas.monon.space/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "space-monon-additive-atlas": {
      "type": "http",
      "url": "https://api.additiveatlas.monon.space/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.space-monon-additive-atlas]
url = "https://api.additiveatlas.monon.space/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "space-monon-additive-atlas": {
      "type": "remote",
      "url": "https://api.additiveatlas.monon.space/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add space-monon-additive-atlas --url 'https://api.additiveatlas.monon.space/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  space-monon-additive-atlas:
    url: "https://api.additiveatlas.monon.space/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "space-monon-additive-atlas": {
      "Transport": "http",
      "Url": "https://api.additiveatlas.monon.space/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add space-monon-additive-atlas -t streamable-http -u 'https://api.additiveatlas.monon.space/mcp'
```

### Other

```json
{
  "mcpServers": {
    "space-monon-additive-atlas": {
      "type": "http",
      "url": "https://api.additiveatlas.monon.space/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-23 (score 80, +1)

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

### 2026-10-21 (score 79, +1)

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

### 2026-10-19 (score 78, +1)

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

### 2026-10-17 (score 77, +1)

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

### 2026-10-14 (score 76, +1)

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

### 2026-10-12 (score 75, +1)

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

### 2026-10-10 (score 74, +2)

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

### 2026-10-07 (score 72, +1)

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

## MCP tools (5)

### `search_substances` (~269 tokens)

Look up substances by name

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.

Input parameters:

- `axis` (string, required): Regulatory axis the label or name belongs to: JP, EU or US.
- `lang` (string, required): Language of the name or label text (ISO 639-1), e.g. ja, en, de, fr.
- `name` (string, required): The name to look up, as printed on a label or roster.

### `get_substance` (~204 tokens)

One substance, with everything its own roster says

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.

Input parameters:

- `id` (string, required): Substance id as returned by search_substances or analyze_label, e.g. eu:e951, jp:designated-aspartame, us:cfr-172-804.

### `analyze_label` (~310 tokens)

Find the additives named on a label

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.

Input parameters:

- `axis` (string, required): Regulatory axis the label or name belongs to: JP, EU or US.
- `lang` (string, required): Language of the name or label text (ISO 639-1), e.g. ja, en, de, fr.
- `text` (required): The additive (or whole ingredient) section of one label: one raw string (split at 、 , ， / for Japanese and , ; . : for Latin script, at bracket depth zero; whitespace is not a separator), or an array…

### `get_substance_diff` (~148 tokens)

One substance, with the cross-axis derivation (paid, HTTP only)

(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.

Input parameters:

- `id` (string, required): Substance id as returned by search_substances or analyze_label, e.g. eu:e951, jp:designated-aspartame, us:cfr-172-804.

### `analyze_label_diff` (~199 tokens)

Find the additives named on a label, with the cross-axis derivation (paid, HTTP only)

(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.

Input parameters:

- `axis` (string, required): Regulatory axis the label or name belongs to: JP, EU or US.
- `lang` (string, required): Language of the name or label text (ISO 639-1), e.g. ja, en, de, fr.
- `text` (required): The additive (or whole ingredient) section of one label: one raw string (split at 、 , ， / for Japanese and , ; . : for Latin script, at bracket depth zero; whitespace is not a separator), or an array…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/space-monon-additive-atlas/api#diagnostics

## Score history

- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 74
- 2026-10-07: 72
- 2026-10-04: 71
- 2026-10-03: 70
- 2026-10-02: 70
- 2026-10-01: 69
- 2026-09-30: 69

## Common questions

### What is the Additive Atlas MCP server?

Additive Atlas is an MCP server listed in the public MCP registry as space.monon/additive-atlas. Food additive regulations of Japan, the EU and the US, side by side, with sources (free tier). This page covers its hosted endpoint (https://api.additiveatlas.monon.space/mcp).

### Is the Additive Atlas MCP server safe to use?

Additive Atlas scores 80 out of 100 on VerifyMCP. 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 Additive Atlas MCP server expose?

Additive Atlas exposes 5 tools: search_substances, get_substance, analyze_label, get_substance_diff, analyze_label_diff. Their descriptions and schemas cost roughly 1,130 tokens of context every time the server is loaded.

### Does the Additive Atlas MCP server require authentication?

No. We connected to Additive Atlas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Additive Atlas MCP server still maintained?

Additive Atlas is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.additiveatlas.monon.space/mcp
- Website: https://additiveatlas.monon.space/
- Changelog RSS feed: https://verifymcp.io/servers/space-monon-additive-atlas/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/space-monon-additive-atlas/api.json
- HTML version of this page: https://verifymcp.io/servers/space-monon-additive-atlas/api