C
Emerging
74/100
15 days ago

jlc-mcp

Local Model Context Protocol server that exposes EasyEDA Pro design capabilities as MCP tools, enabling project inspection, schematic editing, PCB design, validation, and manufacturing exports through natural language.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

InkRoad

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 →

Install from

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

// key findings
172 tools verified — handlers match their declared behaviour
102 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.
// 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.
configJLC_01810_REPORT_FILE
configJLC_01812_NET
configJLC_01812_REPORT_FILE
configJLC_01812_TIMEOUT_MS
configJLC_01813_REPORT_FILE
configJLC_01813_TIMEOUT_MS
configJLC_0187_REPORT_FILE
configJLC_0188_FOOTPRINT_ASSIGNMENTS_FILE
configJLC_0188_REPORT_FILE
configJLC_0189_PATH_FILE
configJLC_0189_REPORT_FILE
configJLC_0189_TUNE_FILE
configJLC_0190_REPORT_FILE
configJLC_0190_TIMEOUT_MS
configJLC_0191_REPORT_FILE
configJLC_0191_TIMEOUT_MS
configJLC_BOARD_OUTLINE_REPORT_FILE
configJLC_DESIGN_RULES_REPORT_FILE
configJLC_E2E_EXPORT_DIR
configJLC_E2E_KEEP_ARTIFACTS
configJLC_E2E_MODE
configJLC_E2E_REPORT_FILE
configJLC_E2E_TARGET
configJLC_LOW_SPEED_REPORT_FILE
configJLC_MCP_DISCOVERY_FANOUT
configJLC_MCP_ENABLE_COMPATIBILITY_API
configJLC_MCP_URL
configJLC_PHASE14_NET
configJLC_PHASE14_PRIMITIVE_ID
configJLC_PHASE14_REPORT_FILE
configJLC_PHASE15_NET
configJLC_PHASE15_PRIMITIVE_ID
configJLC_PHASE15_REPORT_FILE
configJLC_PHASE16_DEVICE_QUERY
configJLC_PHASE16_REPORT_FILE
configJLC_PHASE17_LCSC_ID
configJLC_PHASE17_REPORT_FILE
configJLC_PHASE18_REPORT_FILE
configJLC_PLACEMENT_REPORT_FILE
configJLC_POST_ROUTE_REPORT_FILE
configJLC_ROUTING_REPORT_FILE
// quality suggestions

Tool inputs are validated

Only 55/172 tool handlers declare input schemas (32%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

168/172 tool handlers wrap calls in try/catch (98%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 1/172 tools referenced in tests (1%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 4 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/inkroad-jlc-mcp-1vodnh)](https://m8ven.ai/mcp/inkroad-jlc-mcp-1vodnh)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b1055fce4ba59e70741160c1dd5494b347c36607
code hash: 7bb9f81c8bf064bd5d882d30810a4e0aa131bdff98cfe70e7dc12fe54ef95a2c
verified: 8/4/2026, 8:57:40 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