Cosmetic Regulatory MCP Server

by rootsbymenda Your server? Claim it

not responding

Cosmetic Regulatory is listed as active in the registry but did not answer our last check. It exposes 4 tools. Last commit 23 May 2026.

Cosmetic safety: NOAEL, MoS, SCCS, 12 jurisdictions. 30K ingredients. Free.

Uptime history 51 days of history · worst day 0%

51 days agonow

0.0%

Uptime 24h

0 of 182 checks

Tools

read from the server

104 ms

Response time

average over 24h

Stars

last commit 23 May 2026

Cosmetic Regulatory does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add cosmetic-regulatory --transport http https://roots-mcp-server.rootsbybenda.workers.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "cosmetic-regulatory": {
      "url": "https://roots-mcp-server.rootsbybenda.workers.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.cosmetic-regulatory]
url = "https://roots-mcp-server.rootsbybenda.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "cosmetic-regulatory": {
      "url": "https://roots-mcp-server.rootsbybenda.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "cosmetic-regulatory": {
      "url": "https://roots-mcp-server.rootsbybenda.workers.dev/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

calculate

calculate_mos

Calculate Margin of Safety for a cosmetic ingredient at a specific concentration following SCCS Notes of Guidance methodology. Input: ingredient name/INCI/CAS, concentration percentage, product type (e.g. 'body lotion', 'shampoo', 'lipstick'), optional body weight and dermal absorption override. Returns: NOAEL value with study source (species, route, duration), SCCS exposure parameters (daily exposure, retention factor), Systemic Exposure Dose (SED) calculation, Margin of Safety value, pass/fail assessment against MoS>100 threshold, and recommended maximum concentration if MoS fails. Sources: SCCS Notes of Guidance (11th Revision, SCCS/1628/21), NOAEL studies from ECHA/ToxValDB, SCCS exposure parameter tables. Database: 174,973 NOAEL studies searched for best available value. Use for cosmetic ingredient exposure assessment and safety calculations. Do not use for regulatory lookup alone (use check_ingredient), formula screening (use check_formula), or food/pharmaceutical exposure calculations.

formula

check_formula

Scan a cosmetic product INCI ingredient list for regulatory compliance and safety flags across multiple jurisdictions. Input: comma-separated INCI declaration as printed on a cosmetic product label (up to 50 ingredients). Returns per-ingredient: matched INCI name, CAS number, safety rating, EU and US regulatory status, concern level, regulatory flags, NOAEL values, and jurisdiction-specific restrictions including max concentration limits, product-type restrictions, and regulation references. Returns overall: LOW/MODERATE/HIGH formula risk assessment, flagged ingredient count with reasons, and jurisdiction-level compliance summary. Sources: EU Regulation 1223/2009, US FDA, Korea MFDS, Japan MHLW, ASEAN, Saudi SFDA, Canada Hotlist, Australia SUSMP, China IECIC. Database: 30,553 cosmetic ingredients across 55+ jurisdictions. Use for cosmetic formula safety screening and CPSR-style triage. Do not use for single ingredient lookup (use check_ingredient) or custom MoS calculations (use calculate_mos).

ingredient

check_ingredient

Retrieve cosmetic ingredient safety data for regulatory compliance and safety assessment. Input: common name, INCI name, or CAS number (e.g. 'retinol', 'RETINOL', '68-26-8'). Returns: NOAEL study values with species/route/duration, pre-calculated Margin of Safety from SCCS opinions, GHS hazard classifications, EU/US/Korea/Japan/ASEAN/Saudi/Canada/Australia regulatory status across 12 jurisdictions, SCCS opinion summaries, CIR safety conclusions, dermal absorption profiles, sensitization data with patch-test frequencies, endocrine disruption flags, SVHC status, IFRA fragrance restrictions, China IECIC listing, and EU allergen classifications. Sources include ECHA IUCLID dossiers, SCCS opinions, CIR safety assessments, FDA, ToxValDB, and EPA CompTox. Database: 30,553 cosmetic ingredients, 174,973 NOAEL studies, 8,898 sensitization assays, 5,267 CIR safety conclusions, and 1,583 SCCS opinions. Use for cosmetic ingredient safety assessment. Do not use for full formula scans (use check_formula), MoS calculations with custom concentration (use calculate_mos), food additive questions, or pharmaceutical actives.

ingredients

search_ingredients

Search cosmetic ingredient records by partial name, function, category, or safety concept for ingredient discovery and selection. Input: keyword matching partial INCI name, function, or category (e.g. 'sunscreen', 'preservative', 'retinoid', 'fragrance allergen', 'humectant'). Returns: matching cosmetic ingredient names, INCI names, CAS numbers, functions/categories, safety ratings, EU regulatory status, concern levels, and NOAEL availability. Database: 30,553 cosmetic ingredients with safety profiles. Use for cosmetic ingredient discovery before checking a specific ingredient. Do not use when the user has an exact INCI/CAS and needs full safety data (use check_ingredient).

Endpoints

URL	Transport	State	Latency	Checked
https://roots-mcp-server.rootsbybenda.workers.dev/mcp	streamable-http	answering	104 ms	7 min ago
https://roots-mcp-server.rootsbybenda.workers.dev/sse	sse	answering	67 ms	7 min ago

Alternatives to Cosmetic Regulatory

same job, measured the same way

Spoonacular

by pipeworx-io

Spoonacular food API: recipes, nutrition, ingredients, meal plans. Free 150/day.

54 tools answering

Uptimebolt MCP Server

by clm-cloud-solutions

AI-powered infrastructure monitoring — health, incidents, predictions, RCA, deploy safety

39 installs/wk local only

AI Compliance Monitor

by vdineshk

Regulatory intelligence for AI agents across jurisdictions

4 tools answering

SENTINEL Compliance Intelligence

by injprotocol

AML/CFT compliance oracle: wallet screening, sanctions, PEPs, jurisdiction risk.

22 tools answering

Ifg Tax

by aitorgarcia21

International tax research — 213 jurisdictions, 500K+ legal documents.

20 installs/wk local only

LexLint: compliance lint for AI, scraping, and privacy law

by lexlint

Compliance lint for AI, scraping, and privacy law. Cited findings in 200 or more jurisdictions.

7 tools answering

open-compute (computer-use)

by lukisch

Model-agnostic computer-use MCP: screenshot, safety-gated actions, Windows UIA targeting.

69 installs/wk local only

Noaa Tides

by pipeworx-io

NOAA Tides & Currents — observations, predictions, datums, station metadata

38 tools answering

Cosmetic Regulatory — questions

Answers built from our own checks of this server.

What can Cosmetic Regulatory do?

It exposes 4 tools, read directly from the server on our last check. Among them: calculate_mos, check_formula, check_ingredient, search_ingredients. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Cosmetic Regulatory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 182 checks got a reply (0.0%), average response time 104 ms. The bar chart above shows every period we have measured.

The registry lists Cosmetic Regulatory as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Cosmetic Regulatory?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Cosmetic Regulatory need an API key?

No. Cosmetic Regulatory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

Is Cosmetic Regulatory open source?

Yes — it is published under the MIT licence, written in Python, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.