io.github.rootsbymenda/chemical-safety
REMOTE · CHEM-MCP-SERVER.ROOTSBYBENDA.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
Chemical hazard lookup: SVHC, GHS, NIOSH, ICSC. 468K classifications. Free.
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. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · chem-mcp-server.rootsbybenda.workers.dev
claude mcp add --transport http rootsbymenda-chemical-safety https://chem-mcp-server.rootsbybenda.workers.dev/sse
[mcp_servers.rootsbymenda-chemical-safety] url = "https://chem-mcp-server.rootsbybenda.workers.dev/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rootsbymenda-chemical-safety": {
"type": "remote",
"url": "https://chem-mcp-server.rootsbybenda.workers.dev/sse",
"enabled": true
}
}
} openclaw mcp add rootsbymenda-chemical-safety --url https://chem-mcp-server.rootsbybenda.workers.dev/sse --transport streamable-http
mcp_servers:
rootsbymenda-chemical-safety:
url: "https://chem-mcp-server.rootsbybenda.workers.dev/sse" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://chem-mcp-server.rootsbybenda.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rootsbybenda.workers.dev | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | a19ebb28df33c3640efc0c208730db7e |
| SANs: rootsbybenda.workers.dev, *.rootsbybenda.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of chem-mcp-server.rootsbybenda.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://chem-mcp-server.rootsbybenda.workers.dev/sse | Verified | 200 | |
| http (plaintext) | http://chem-mcp-server.rootsbybenda.workers.dev/sse | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_chemical ~322
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 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,… |
No output schema declared.
No examples provided.
check_svhc_list ~211
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).
| Name | Type | Req | Description |
|---|---|---|---|
| substances | string | yes | 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… |
No output schema declared.
No examples provided.
search_chemicals ~379
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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,… |
No output schema declared.
No examples provided.