MSDS-Chain (littleblakew/msds-chain-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Limited view
69/100
23 days ago

MSDS-Chain

Chemical safety intelligence for AI-assisted experiment design. 18 MCP tools for compatibility checks, hazard analysis, PPE, storage, waste disposal, mixing order, exposure limits, transport classification, regulatory compliance (8 jurisdictions), and signed audit reports. Supports 4,200+ chemicals in 5 languages.

→ littleblakew/msds-chain-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

littleblakew

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
23 tools verified — handlers match their declared behaviour
21 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: MSDS_API_KEY, MCP_SMOKE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretMSDS_API_KEYsk-msds-xxx python server_remote.py
configMSDS_LANGen Response language: en, zh, ja, de, id
configMCP_SMOKE_URL
🔐 secretMCP_SMOKE_KEY
configMCP_SMOKE_MIN_TOOLS
configMSDS_MCP_HOST
configMSDS_MCP_PORT
configMSDS_MCP_TRANSPORT(compatibility). The env var is kept for backward compatibility
// quality suggestions

All four hints declared on every tool

23/23 tools missing one or more hints — check_chemical_compatibility (missing: idempotentHint); get_chemical_risk_warnings (missing: idempotentHint); check_regulatory_compliance (missing: idempotentHint), +20 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

openWorldHint matches behaviour

4 tools claim openWorldHint=false but make outbound HTTP — create_audit_session → dynamic (line 1360); get_audit_report → dynamic (line 1490); search_chemical_database → dynamic (line 1582)

Either flip openWorldHint to true (acknowledging external reach) or refactor the handler to avoid outbound HTTP. If the only network calls are to a known fixed endpoint that you consider part of the tool itself, document that and keep openWorldHint=false; otherwise true is honest.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/littleblakew-msds-chain-mcp-1ct1se)](https://m8ven.ai/mcp/littleblakew-msds-chain-mcp-1ct1se)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1d9385d970f360bbfefc55e02d6c14c8d880ab74
code hash: 5cc0a134ae4915a1e5d859b0de8a34d984a2b920a8434ca7e664aabd3b3dd338
verified: 8/6/2026, 5:28:43 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client