API and MCP server

Compoatlas data can be queried directly, read-only and without an account: through a JSON API or an MCP server that AI assistants (Claude, ChatGPT and others) can use as a connector. Answers are those of the pages, with dated official sources.

JSON API

• GET /api/v1/ingredients/{slug}: status of an ingredient. Example: /api/v1/ingredients/phenoxyethanol
• GET /api/v1/products/{barcode}: recorded, dated composition of a cosmetic product, with the certainty of each link
• GET /api/v1/alerts?barcode=… (or substance=, brand=): EU Safety Gate alerts on cosmetic products. Example: /api/v1/alerts?substance=hydroquinone
• POST /api/v1/report with {"products": [{"gtin": …, "ingredients": …}]}: compliance report for up to 200 products (prohibited ingredient, Safety Gate alert, missing list); nothing is stored
• GET /api/v1/search?q=… and POST /api/v1/analyze with {"text": "Aqua, Glycerin, …"}
• OpenAPI description: /api/v1/openapi.json

MCP server

Endpoint: https://compoatlas.com/mcp (Streamable HTTP, no authentication), compatible with protocol version 2026-07-28 and with 2025 versions that still use the initialize handshake. Five read-only tools: search, get_ingredient, get_product, search_alerts, analyze_ingredient_list. Text answers are currently in French; structured data is language-neutral.