Cosmetics MCP server
BetaIngredient rules, formula checks and label tools as tools for AI agents.
The same tools as the REST API over the Model Context Protocol, with quotes and the dataset version on every result.
At a glance
- Status
- Beta
- Endpoint
- POST /mcp
- Cost
- same units as REST
- MCP tools
- 10 tools
- Data
- Cosmetics dataset 1.0.0, built 2026-10-14.
Connect a client
POST JSON-RPC 2.0 to /mcp with your key in X-API-Key; each tool has the input schema of its REST endpoint and the same units.
{
"mcpServers": {
"cosmeticrules": {
"type": "http",
"url": "https://api.cosmeticrules.com/mcp",
"headers": { "X-API-Key": "YOUR_KEY" }
}
}
}Tools
| Tool | What it does |
|---|---|
| cosmetics_ingredient_lookup | Ingredient lookup by INCI, CAS or text |
| cosmetics_ingredient_get | Get a substance by id |
| cosmetics_rules_by_market | Rules by market |
| cosmetics_compare_markets | Compare an ingredient's rules across markets |
| cosmetics_categories | Product categories |
| cosmetics_formula_check | Check a formula against market rules |
| cosmetics_formula_check_batch | Check many formulas |
| cosmetics_allergen_label | Allergen label calculation |
| cosmetics_label_check | Validate an INCI ingredient list |
| cosmetics_changes | Rule change feed |
What is included
- Same input schemas and metering as the REST endpoints
How it differs
- Quotes from the law an agent can cite.
- NOT_MODELLED instead of a silent pass.
- The dataset version on every result.
Plans
One key and one plan cover every Cosmetic Rules product, this one included. Free: 2,500 units a month. Paid plans are coming soon. Caching inside your product is allowed, and so is use by AI agents. Plans and units.
Status: Beta (new: the interface may still change, with notice in the docs). All products.