Search / space.monon/additive-atlas
protogridR0· no sign-inFood additive regulations of Japan, the EU and the US, side by side, with sources (free tier).
v0.1.0 · active · website · descriptor JSON · versions
{
"mcpServers": {
"additive-atlas": {
"type": "http",
"url": "https://api.additiveatlas.monon.space/mcp"
}
}
}claude mcp add --transport http additive-atlas https://api.additiveatlas.monon.space/mcp[mcp_servers.additive-atlas]
url = "https://api.additiveatlas.monon.space/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"additive-atlas": {
"type": "remote",
"url": "https://api.additiveatlas.monon.space/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"additive-atlas": {
"type": "http",
"url": "https://api.additiveatlas.monon.space/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=additive-atlas&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLmFkZGl0aXZlYXRsYXMubW9ub24uc3BhY2UvbWNwIn0%3D"
}{
"servers": {
"additive-atlas": {
"type": "http",
"url": "https://api.additiveatlas.monon.space/mcp"
}
}
}{
"mcpServers": {
"additive-atlas": {
"httpUrl": "https://api.additiveatlas.monon.space/mcp"
}
}
}extensions:
"additive-atlas":
enabled: true
name: "additive-atlas"
type: streamable_http
uri: "https://api.additiveatlas.monon.space/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations5 of 5 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_substance (destructiveHint, idempotentHint); search_substances (destructiveHint, idempotentHint); analyze_label (destructiveHint, idempotentHint); …tools.token_costabout 1,374 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes4 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageanalyze_label_diffchangeddescription(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.
(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.
get_substance_diffchangeddescription(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.
(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.
analyze_label_diffchangeddescription(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, x402 payment, in preparation) to call instead.
(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.
get_substance_diffchangeddescription(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, x402 payment, in preparation) to call instead.
(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.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-100% +updated-20d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://api.additiveatlas.monon.space/mcp streamable-http | none | yes | 100% | 736 ms | 2025-11-25 | 2026-10-20 |
analyze_labelread-only | 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. |
analyze_label_diffread-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. |
get_substanceread-only | 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. |
get_substance_diffread-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. |
search_substancesread-only | 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. |
Schemas: list_tools.
{
"name": "space.monon/additive-atlas",
"title": "Additive Atlas",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://api.additiveatlas.monon.space/mcp",
"type": "streamable-http"
}
],
"version": "0.1.0",
"websiteUrl": "https://additiveatlas.monon.space",
"description": "Food additive regulations of Japan, the EU and the US, side by side, with sources (free tier)."
}