# io.github.rootsbymenda/chemical-safety (remote · chem-mcp-server.rootsbybenda.workers.dev)

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

- Trust score: 60/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `chem-mcp-server.rootsbybenda.workers.dev`: 66/100, [markdown](https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server.md), [page](https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server)
- remote · `chem-mcp-server.rootsbybenda.workers.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server-2.md), [page](https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server-2)

## Channel facts

- Endpoint: `https://chem-mcp-server.rootsbybenda.workers.dev/sse`
- Transports: `sse`
- Auth: `none`
- Version: `1.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 912 tokens (~304/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rootsbymenda-chemical-safety": {
      "type": "remote",
      "url": "https://chem-mcp-server.rootsbybenda.workers.dev/sse",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rootsbymenda-chemical-safety --url https://chem-mcp-server.rootsbybenda.workers.dev/sse --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rootsbymenda-chemical-safety:
    url: "https://chem-mcp-server.rootsbybenda.workers.dev/sse"
```

### Other

```json
{
  "mcpServers": {
    "rootsbymenda-chemical-safety": {
      "type": "http",
      "url": "https://chem-mcp-server.rootsbybenda.workers.dev/sse"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (3)

### `check_chemical` (~322 tokens)

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.

Input parameters:

- `query` (string, required): Chemical common name, technical substance name, synonym, or CAS number (Chemical Abstracts Service registry number, e.g. '80-05-7'). Use CAS when available for exact matching across ECHA SVHC, NIOSH,…

### `check_svhc_list` (~211 tokens)

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).

Input parameters:

- `substances` (string, required): Comma-separated or newline-separated list of chemical names or CAS numbers to screen against the EU ECHA SVHC Candidate List. Include CAS numbers when available because SVHC names may have salts, iso…

### `search_chemicals` (~379 tokens)

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).

Input parameters:

- `database` (string): Optional dataset filter. Use 'svhc' for ECHA Candidate List records, 'niosh' for occupational exposure profiles, 'ghs' for hazard classifications, 'icsc' for safety cards, or 'all' for cross-dataset…
- `limit` (number): Maximum number of chemical records to return (1-25, default 10). Use lower limits for precise regulatory phrases and higher limits for broad hazard discovery.
- `query` (string, required): Hazard, endpoint, organ system, exposure route, regulatory phrase, or chemical keyword (e.g. 'carcinogen', 'respiratory', 'liver', 'skin sensitizer', 'endocrine'). Use this for discovery across SVHC,…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server-2#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 58
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://chem-mcp-server.rootsbybenda.workers.dev/sse
- Repository: https://github.com/rootsbymenda/chem-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server-2/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server-2/changelog.json
- HTML version of this page: https://verifymcp.io/servers/rootsbymenda-chemical-safety/chem-mcp-server-2