Chemical Safety MCP Server

io.github.rootsbymenda/chemical-safety

not responding

Chemical Safety is listed as active in the registry but did not answer our last check. It exposes 3 tools. Last commit 23 May 2026.

Chemical hazard lookup: SVHC, GHS, NIOSH, ICSC. 468K classifications. Free.

Uptime history 39 hours of history · worst hour 0%

39 hours agonow

9.3%

Uptime 24h

17 of 182 checks

Tools

read from the server

906 ms

Response time

average over 24h

Stars

last commit 23 May 2026

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add chemical-safety --transport http https://chem-mcp-server.rootsbybenda.workers.dev/mcp

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

{
  "mcpServers": {
    "chemical-safety": {
      "url": "https://chem-mcp-server.rootsbybenda.workers.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.chemical-safety]
url = "https://chem-mcp-server.rootsbybenda.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "chemical-safety": {
      "url": "https://chem-mcp-server.rootsbybenda.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "chemical-safety": {
      "url": "https://chem-mcp-server.rootsbybenda.workers.dev/mcp"
    }
  }
}

Available tools 3

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

chemical

check_chemical

Retrieve chemical safety and hazard data for a substance used in industrial, cosmetic, or food applications, by name or CAS number. Input: chemical name, technical substance name, synonym, or CAS number (e.g. 'bisphenol A', 'formaldehyde', '80-05-7'). Returns: substance identifiers (CAS, EC number, PubChem CID, InChIKey, SMILES, molecular formula/weight via crosswalk), ECHA SVHC Candidate List status with reason and inclusion date, NIOSH occupational exposure data (REL, PEL, IDLH, exposure routes, symptoms, target organs, health hazards), GHS classification (signal word, hazard statements, pictograms), ICSC safety card data (short/long-term effects, exposure routes), and cross-references to cosmetic ingredient and food additive databases. Sources: ECHA SVHC Candidate List (253 substances), NIOSH Pocket Guide (677 chemicals), GHS classifications (468,165 records), ICSC safety cards, substance identifier crosswalk (73,252 substances). For chemical hazard assessment and regulatory compliance. Do not use for batch SVHC screening (use check_svhc_list), cosmetic formula checks, food additive safety, or drug interactions.

chemicals

search_chemicals

Search chemical safety datasets by hazard keyword, exposure route, organ effect, GHS phrase, or regulatory concept for chemical hazard discovery. Input: hazard keyword (e.g. 'carcinogen', 'respiratory', 'liver', 'skin sensitizer', 'endocrine') with optional dataset filter (svhc, niosh, ghs, icsc, or all). Returns: ranked matches from SVHC (with reason and date), NIOSH (with REL/PEL/IDLH and symptoms), GHS (with hazard statements and pictograms), and ICSC (with exposure effects) — each with dataset label, CAS number, and detail URL. Database: 468,165 GHS records, 677 NIOSH chemicals, 253 SVHC substances, ICSC safety cards. For chemical hazard research and regulatory intelligence. Do not use for exact substance lookup (use check_chemical) or batch SVHC screening (use check_svhc_list).

svhc

check_svhc_list

Screen multiple substances against the EU ECHA SVHC Candidate List for REACH regulatory compliance. Input: comma-separated or newline-separated chemical names or CAS numbers (up to 50 substances). Returns per-substance: match status (SVHC or not), resolved CAS number, SVHC substance name, EC number, reason for inclusion (CMR, PBT, vPvB, endocrine disruption, equivalent concern), and date included on Candidate List. Source: ECHA SVHC Candidate List (253 Substances of Very High Concern under EU REACH Regulation). For supply chain SVHC screening and REACH Article 33 compliance. Do not use for full hazard profiles (use check_chemical) or broad hazard discovery (use search_chemicals).

Endpoints

URL	Transport	State	Latency	Checked
https://chem-mcp-server.rootsbybenda.workers.dev/mcp	streamable-http	answering	31 ms	8 min ago
https://chem-mcp-server.rootsbybenda.workers.dev/sse	sse	answering	59 ms	9 min ago

Chemical Safety — questions

Answers built from our own checks of this server.

What can Chemical Safety do?

It exposes 3 tools, read directly from the server on our last check. Among them: check_chemical, check_svhc_list, search_chemicals. 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 Chemical Safety working right now?

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

The registry lists Chemical Safety 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 Chemical Safety?

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 Chemical Safety need an API key?

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

How fast is Chemical Safety?

It answers our handshake in 906 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Chemical Safety open source?

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