原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Msds Chain

作者:littleblakew版本 1.5.12i★ –i在你的电脑上运行
注册名称io.github.littleblakew/msds-chain

安装

概览

作者提供的说明(英文原文)

Chemical safety intelligence — 25 tools: compatibility, hazards, PPE, compliance, SDS lookup

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: Streamable HTTP
  • 分类: 法律与政府数据
  • 你需要填写:MSDS_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "msds-chain": {
      "command": "npx",
      "args": [
        "-y",
        "msds-chain-mcp"
      ],
      "env": {
        "MSDS_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add msds-chain --env MSDS_API_KEY=your-value -- npx -y msds-chain-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "msds-chain": {
      "command": "npx",
      "args": [
        "-y",
        "msds-chain-mcp"
      ],
      "env": {
        "MSDS_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "msds-chain": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "msds-chain-mcp"
      ],
      "env": {
        "MSDS_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • MSDS_API_KEY 机密 必填 env
    API key from msdschain.lagentbot.com (free plan available)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 littleblakew 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“法律与政府数据”中的其他服务器比较i

  • 星标数多于此分类中其他 1744 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1744 个服务器的 88% 更新
  • 基础检查结果等于或优于此分类中其他 1744 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Msds Chain 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:MSDS_API_KEY

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.5.12)于5天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Romania Company Check, Japan Company Check, U.S. Public Company Check

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Romania Company Check

作者:JusticeUA

Romania company checks by CUI: status, insolvency, LEI and sanctions from official registers.

在云端运行今天更新
安装

Japan Company Check

作者:JusticeUA

Japan company checks by corporate number: status, closure cause, successor, LEI and sanctions.

在云端运行今天更新
安装

U.S. Public Company Check

作者:JusticeUA

U.S. public company checks by SEC CIK: filing status, bankruptcy 8-K flag, LEI and sanctions.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

MSDS Chain MCP Server

Chemical safety intelligence for AI-assisted experiment design.

An MCP server that gives AI agents (Claude, ChatGPT, Claude Code, Gemini CLI, Copilot Studio, and any other MCP client) 27 tools for chemical safety reasoning: compatibility checks, hazard analysis, regulatory compliance, PPE, storage, transport, and signed audit reports. Every answer names the supplier SDS it came from, with a link to the original PDF.

MSDS Chain, powered by ChainSDS: a verified, always-current chemical safety database.

Built for researchers who design experiments with AI and want safety verification inside the workflow rather than as a separate step: whether the chemicals on a deck are compatible, which mixing orders are dangerous, what PPE a specific handling step needs, how a compound is treated under EU REACH or US OSHA/TSCA, and what a GLP/GMP reviewer will ask for afterwards.

Quick Start

Hosted endpoint. Nothing to install, nothing to run locally:

claude mcp add msds-chain --transport http https://mcp.lagentbot.com/mcp

Then run /mcp in Claude Code and sign in. A browser opens, you enter your email, and you paste back the code we send you. Your account is provisioned automatically and the free plan includes a credit allowance. There is no API key to create beforehand.

On another platform? See Platform Setup below.

Tools (27)

ToolDescription
`batch_safety_check`One-call report for a chemical list: pairwise compatibility + per-chemical risk warnings
`check_regulatory_lists`Cross-reference a chemical against 23 regulatory watch lists across 8 jurisdictions + 3 international conventions
`review_synthesis_route`Screen a multi-step synthesis route for incompatibilities within each step and between carried-over residue and the next step; never declares a route safe
`assess_thermal_hazard`Thermal hazard screening: energetic-group and oxygen-balance flags, plus a Stoessel class from process values you supply
`get_sds_section`Retrieve a specific SDS section (1-16) for a chemical
`get_sds_document`Signed download URL (~5 min) for the original SDS/MSDS PDF; includes source provenance
`get_chemical_alternatives`Safer substitutes for restricted or high-risk chemicals
`validate_protocol_chemicals`Extract & validate chemical names from protocol text or code
`check_mixing_order`Safe addition sequence for reagent pairs (e.g., acid into water)
`get_waste_disposal`Waste classification, container type, and disposal procedures
`upload_msds_pdf`Upload MSDS PDF for AI-powered parsing and data extraction (requires API key)
`validate_sds`Check an SDS you uploaded for contradictions between its own sections, gaps, age and US OSHA HazCom format; every finding quotes the lines it is based on
`draft_sds_sections`Draft Sections 8 and 15 of an SDS for your own mixture from its ingredient list; every line cites its source, and missing ingredients are listed rather than guessed
`compare_sds_versions`Hazard-change diff between two SDS versions (H-code additions/removals + whether they change a verdict)
check_chemical_compatibilityPairwise compatibility for 2+ chemicals
get_chemical_risk_warningsGHS classification, H-codes, signal words, flash point
get_ppe_recommendationGloves, eye protection, respiratory, body protection
get_storage_guidanceStorage class, cabinet type, temperature, isolation rules
get_emergency_responseSpill, fire, or exposure emergency procedures
get_exposure_limitsOEL/TLV/PEL/MAC across US, EU, JP, CN, INT
get_transport_classificationUN number, hazard class, packing group, ADR/IATA/IMDG
check_regulatory_complianceMulti-region compliance status, list-backed for EU, US, CN, JP, CA, AU, SG
search_chemical_databaseLook up chemicals by name, synonym, or CAS number
ask_chemical_safetyNatural language catch-all for any safety question
create_audit_sessionFull audit with signed PDF report (requires API key)
get_audit_reportDownload link for the signed audit PDF

Usage Examples

Experiment protocol review:

User: I'm planning a Grignard reaction with magnesium turnings, diethyl ether,

and bromobenzene. Check if this setup is safe.

Agent: → calls batch_safety_check(["magnesium", "diethyl ether", "bromobenzene"]) → Returns: compatibility matrix + per-chemical risk warnings (with source SDS)

Signed audit report:

User: Create a safety audit report for our quarterly review.

Chemicals: acetone, methanol, ethanol, isopropanol, hexane.

Agent: → calls create_audit_session("Q2 2026 Solvent Cabinet Review", [...]) → calls get_audit_report("SESSION-ID") → Returns: signed PDF URL (Ed25519 signature, suitable for GLP/GMP compliance)

Platform Setup

One hosted server, two transports. Pick the row your client supports:

TransportEndpointNotes
Streamable HTTPhttps://mcp.lagentbot.com/mcpPreferred: broadest and most robust
SSEhttps://mcp.lagentbot.com/sseFor clients that only speak SSE

Authentication is either OAuth (the client opens a browser sign-in on first connect) or a static header, Authorization: Bearer sk-msds-your-key, for headless clients. Create a key at msdschain.lagentbot.com > API Keys.

Claude (web, desktop, mobile)

Settings > Connectors, search msds-chain, and enable it. Sign-in happens on first use.

Claude Code

Three routes, any one is enough:

# 1. Remote server only

claude mcp add msds-chain --transport http https://mcp.lagentbot.com/mcp

2. Plugin from the official Claude plugin marketplace (server + skill)

/plugin install msds-chain@claude-plugins-official

3. npm shim (registers the same hosted endpoint)

claude mcp add msds-chain -- npx -y msds-chain-mcp@latest

Manual config in ~/.claude.json:

{

"mcpServers": { "msds-chain": { "type": "http", "url": "https://mcp.lagentbot.com/mcp" } } }

Routes 2 and 3 of the plugin also install the /msds-safety-check skill: it spots chemicals in your conversation and offers a check, and runs a guided audit for lab protocols or EHS compliance.

ChatGPT

Listed in the OpenAI Plugin Directory. Search MSDS Chain in ChatGPT, enable it, and sign in when prompted. Works on web, desktop, and mobile.

Gemini CLI

Listed in the Gemini CLI extensions gallery:

gemini extensions install https://github.com/littleblakew/msds-chain-mcp

Gemini asks you to confirm twice: once to trust the workspace, once to review the extension and the skill it carries. Your first chemical question starts the sign-in automatically; the server supports Dynamic Client Registration, so Gemini registers itself and completes the OAuth exchange on its own. Check the connection with gemini mcp list, then just ask in chat:

Can acetone and sodium hypochlorite be stored in the same cabinet?
OpenAI Codex CLI
codex marketplace add https://github.com/littleblakew/msds-chain-mcp
Microsoft Copilot Studio and Power Platform

MSDS Chain ships a certified Power Platform connector, so there is nothing to configure by hand. In Copilot Studio, add a tool from the connector directory and search MSDS Chain; the connector handles the OAuth exchange against the same hosted endpoint.

SSE-only clients (悟空 / Wukong, Dify, Coze)

These clients do not speak streamable HTTP yet, so point them at /sse and pass a static key:

  1. Open the MCP server or tool integration settings
  2. Transport type: SSE
  3. URL: https://mcp.lagentbot.com/sse
  4. Header: Authorization : Bearer sk-msds-your-key
Any other MCP client

Use the endpoint table above. Clients that implement OAuth 2.1 with Dynamic Client Registration need no pre-registration; everything else uses the static Authorization header.

Privacy & Data Handling

  • Privacy Policy: msdschain.lagentbot.com/privacy
  • Read-only tools send only the chemical names and queries you provide; no personal data is required.
  • API-key tools (upload_msds_pdf, create_audit_session, get_audit_report) associate activity with your account for audit traceability.
  • Uploaded MSDS PDFs are processed for data extraction and contribute to the verified ChainSDS database per your account's data-sharing settings.

Data Coverage

Industry-sourced, AI-verified, and cryptographically signed.

  • 4,000,000+ chemical records with multi-language aliases (EN/ZH/JA)
  • NFPA/GHS classification for compatibility rules
  • 23 regulatory watch lists across major jurisdictions (EU, US, CN, JP, KR, CA, AU, SG) plus international conventions
  • Occupational exposure limits from 5 standards (OSHA PEL, ACGIH TLV, EU IOELV, JP OEL, CN GBZ)
  • UN transport data for 16+ common lab chemicals
  • Version tracking: detects a newer SDS and diffs its hazard classification against the one you relied on

Troubleshooting

SymptomLikely causeFix
401 Unauthorized on connectMissing or invalid API keyCheck the Authorization: Bearer sk-msds-... header. Generate a fresh key at msdschain.lagentbot.com > API Keys.
Tools don't appear in the clientServer not loadedFully restart the client after adding the server, then confirm msds-chain shows in the MCP/tools list.
Connection drops or times outWrong transportPrefer https://mcp.lagentbot.com/mcp; SSE sessions can drop when the server redeploys. GET https://mcp.lagentbot.com/health should return {"status":"ok"}.
Credit balance exhaustedCredit allowance used upThe error says how to continue: an upgrade link and, on the free plan, when credits reset.
Empty results for a known chemicalName not matchedRetry with the CAS number or a common synonym; search_chemical_database accepts name, synonym, or CAS.
OAuth sign-in failsOAuth metadata unreachableConfirm GET https://mcp.lagentbot.com/.well-known/oauth-authorization-server returns 200; the client should auto-discover the authorize and token endpoints.

Still stuck? Email contact@lagentbot.com or open an issue at github.com/littleblakew/msds-chain-mcp/issues.

License

MIT

About

Built by LAgentBot, AI-powered chemical safety infrastructure.

Part of the MSDS Chain platform: the world's first AI Agent-driven chemical safety data trust network, powered by ChainSDS.

问 PopNx