Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Chemical safety intelligence — 25 tools: compatibility, hazards, PPE, compliance, SDS lookup
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
MSDS_API_KEY비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
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/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"msds-chain": {
"command": "npx",
"args": [
"-y",
"msds-chain-mcp"
],
"env": {
"MSDS_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"msds-chain": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"msds-chain-mcp"
],
"env": {
"MSDS_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 littleblakew 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: MSDS_API_KEY
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.5.12)은 4일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, MemberVault MCP by usefulapi
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
List courses; add users to courses, remove course access or delete users in MemberVault.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
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.
| Tool | Description |
|---|---|
| `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_compatibility | Pairwise compatibility for 2+ chemicals |
get_chemical_risk_warnings | GHS classification, H-codes, signal words, flash point |
get_ppe_recommendation | Gloves, eye protection, respiratory, body protection |
get_storage_guidance | Storage class, cabinet type, temperature, isolation rules |
get_emergency_response | Spill, fire, or exposure emergency procedures |
get_exposure_limits | OEL/TLV/PEL/MAC across US, EU, JP, CN, INT |
get_transport_classification | UN number, hazard class, packing group, ADR/IATA/IMDG |
check_regulatory_compliance | Multi-region compliance status, list-backed for EU, US, CN, JP, CA, AU, SG |
search_chemical_database | Look up chemicals by name, synonym, or CAS number |
ask_chemical_safety | Natural language catch-all for any safety question |
create_audit_session | Full audit with signed PDF report (requires API key) |
get_audit_report | Download link for the signed audit PDF |
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)
One hosted server, two transports. Pick the row your client supports:
| Transport | Endpoint | Notes |
|---|---|---|
| Streamable HTTP | https://mcp.lagentbot.com/mcp | Preferred: broadest and most robust |
| SSE | https://mcp.lagentbot.com/sse | For 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.
Settings > Connectors, search msds-chain, and enable it. Sign-in happens on first use.
Three routes, any one is enough:
# 1. Remote server only
claude mcp add msds-chain --transport http https://mcp.lagentbot.com/mcp
/plugin install msds-chain@claude-plugins-official
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.
Listed in the OpenAI Plugin Directory. Search MSDS Chain in ChatGPT, enable it, and sign in when prompted. Works on web, desktop, and mobile.
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?
codex marketplace add https://github.com/littleblakew/msds-chain-mcp
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.
These clients do not speak streamable HTTP yet, so point them at /sse and pass a static key:
https://mcp.lagentbot.com/sseAuthorization : Bearer sk-msds-your-keyUse 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.
upload_msds_pdf, create_audit_session, get_audit_report) associate activity with your account for audit traceability.Industry-sourced, AI-verified, and cryptographically signed.
| Symptom | Likely cause | Fix |
|---|---|---|
401 Unauthorized on connect | Missing or invalid API key | Check the Authorization: Bearer sk-msds-... header. Generate a fresh key at msdschain.lagentbot.com > API Keys. |
| Tools don't appear in the client | Server not loaded | Fully restart the client after adding the server, then confirm msds-chain shows in the MCP/tools list. |
| Connection drops or times out | Wrong transport | Prefer 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 exhausted | Credit allowance used up | The error says how to continue: an upgrade link and, on the free plan, when credits reset. |
| Empty results for a known chemical | Name not matched | Retry with the CAS number or a common synonym; search_chemical_database accepts name, synonym, or CAS. |
| OAuth sign-in fails | OAuth metadata unreachable | Confirm 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.
MIT
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.