Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EasyEDA MCP

NPM · EASYEDA-PRO-MCP

Read and draw EasyEDA Pro schematics and PCBs through a bridge extension, with guarded edits.

Available components

+15 this week 63 Trust /100

Last scanned (20 hours ago)

Scores higher than 32% of npm servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 1 of 2 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability50
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4542 tokens (~378/item across 12 items; 12 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "eda_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 48

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/easyeda-pro-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 2 packages
Packages resolved 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~4,363 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
eda_api ~173

Look up the EasyEDA Pro extension API (offline, from the official typings; doc comments are in Chinese). `query`: keyword search over method names and docs. `name`: full listing of a class/eda object (sch_PrimitiveWire), an interface, enum or type, or one method with remarks and example (sch_PrimitiveWire.modify). No arguments: overview of all eda.* objects.

NameTypeReqDescription
examplesboolean–With `name` of a class: include remarks and examples for every method (long).
limitinteger–Max search results (default 20).
namestring–Class, eda property, interface, enum, type, or Class.method.
querystring–Keywords, e.g. 'netlist' or 'pin modify'.

No output schema declared.

No examples provided.

eda_call ~124

Call one EasyEDA API method by path, e.g. method 'sch_PrimitiveWire.getAll' with args ['GND']. Shortcut for simple reads and single writes; for anything with loops use eda_exec. Look up signatures with eda_api.

NameTypeReqDescription
argsarray–Positional arguments (default none).
maxCharsinteger––
methodstringyesPath under eda, e.g. dmt_Schematic.getCurrentSchematicPageInfo
saveTostring––
timeoutMsinteger––

No output schema declared.

No examples provided.

eda_exec ~1,483

Run JavaScript inside EasyEDA Pro and get the returned value. The code is the body of an async function with `eda` (the EasyEDA extension API), `h` (helpers), `args` (your JSON), `console` (captured) and `store` (object that persists between calls). Use `return` for the result. Do many operations in ONE call with loops instead of many calls. EasyEDA primitives are returned as plain objects built from their getState_* getters; File/Blob results are saved to disk and returned as a path. Nothing is guarded or confirmed: read back what you changed. Schematic y axis points up. Helpers available as `h` inside eda_exec code (all async unless noted): h.ctx() current project/document/schematic/page | h.pages() | h.openPage(uuidOrName) h.parts({pins?, des?, region?:[x1,y1,x2,y2], type?, allPages?}) compact components; h.part("U1") one component with pins h.wires(net?) | h.snapshot({region?, pins?}) parts+flags+wires of the page h.nets() {net:["U1.3",...]} from the native PADS netlist (all pages) | h.net("GND" | "U1.3") | h.checkNets({NET:["U1.3","R2.1"]}) h.lcsc("C1234" | [..]) -> {found:{id:{uuid,libraryUuid}}, missing} h.draw(ops, {trial?, expect?:{NET:[pins]}, allowShorts?, rollback?, guard?, keepGoing?, verbose?}) one change, all or nothing (see sch_draw) ops: {op:"wire",line:[x1,y1,x2,y2,..],net?} {op:"part",lcsc|device,x,y,rot?,des?} {op:"flag",kind:"Ground"|"Power",net,x,y,rot?} {op:"port",dir:"IN"|"OUT"|"BI",net,x,y,rot?} {op:"move",part,x?,y?,rot?} {op:"set",part,props} {op:"nc",pin:"U1.3"} {op:"unname",wire} {op:"rewire",wire,line} {op:"delete",wires?,parts?,others?} {op:"text",x,y,text,size?,rot?} {op:"rect",x,y,w,h} {op:"circle",x,y,r} {op:"line",line:[..]} {op:"attr",part,key:"Designator"|"Name",x?,y?,rot?,visible?} h.netDiff(before, after) what changed between two h.nets() results (shorts, joined, dropped, split, renamed, connected; sync) h.erc({strict?, ui?}) floating pins, single-pin nets, unnumbered and duplicate designators + EasyEDA's o…

NameTypeReqDescription
args––Any JSON value, available in the code as `args`.
codestringyesBody of an async function. Example: const w = await h.wires('GND'); return w.length;
maxCharsinteger–Inline result limit (default 12000); larger results are saved to a file and previewed.
saveTostring–Absolute path: save the result (or the returned File) there instead of returning it inline.
timeoutMsinteger–Time limit in ms (default 30000). Code that times out keeps running in EasyEDA.

No output schema declared.

No examples provided.

eda_status ~58

Check the bridge: is EasyEDA Pro connected, which editor/extension version, and what project/document/page is active.

NameTypeReqDescription
waitMsinteger–How long to wait for EasyEDA to connect before giving up (default 8000).

No output schema declared.

No examples provided.

lib_search ~142

Search the EasyEDA/LCSC device library by words ('100nF 0402 X7R', 'STM32F103C8T6') or look up LCSC numbers. Returns name, LCSC number, footprint, JLCPCB class (Basic/Extended) and the uuid pair that {op:'part', device:{uuid, libraryUuid}} takes.

NameTypeReqDescription
datasheetboolean–Include datasheet links.
lcscarray–Instead of query: LCSC numbers like C25804.
limitinteger–Default 10.
pageinteger––
querystring–Words to search for.

No output schema declared.

No examples provided.

pcb_do ~204

Whole-board actions. action: 'open' (open a PCB of the project by `name` or uuid, the first one by default), 'import' (bring the schematic's changes onto the board; lists the changes and applies them, apply:false only lists), 'rebuild' (refill all pours), 'autoroute' (EasyEDA's own router; `props` like {RoutingNets:['A','B'], layers:[1,2], ignoreNets:[...]}), 'unroute' (delete all tracks and vias of `net`, or of every net when none is given).

NameTypeReqDescription
actionstringyes–
applyboolean–import: default true.
namestring–open: PCB name or uuid.
netstring–unroute: only this net.
propsobject–autoroute: IPCB_AutoRoutingProps.
timeoutMsinteger–Default 300000.

No output schema declared.

No examples provided.

pcb_draw ~520

Apply a list of operations to the active PCB as ONE change. The design rule check runs before and after (guard): a new error other than a not-yet-routed connection (clearance, short, overlap with a keep-out) takes the whole change back, as does a failed op; pours are refilled before judging. trial:true reports and takes it back in any case. Coordinates in mil, y up (unit:'mm' for millimetres); layer by number or name (top, bottom, topsilk, bottomsilk, outline, document, inner1...). ops: {op:'track',net,layer,points:[x1,y1,x2,y2,...],width?} | {op:'via',net,x,y,hole?,dia?} | {op:'move',part:'R1',x?,y?,rot?,layer?} | {op:'place',lcsc|device|footprint,x,y,layer?,rot?,des?} | {op:'set',part,props} | {op:'outline',rect:[x,y,w,h]|points:[...]|circle:[x,y,r]} | {op:'pour',net,layer,rect|points,name?,priority?} | {op:'region',layer,rect|points,rules?} (keep-out) | {op:'fill',layer,rect|points|circle,net?} | {op:'text',layer,x,y,text,size?,width?,rot?} | {op:'line',layer,points,width?} (silkscreen or document line) | {op:'delete',ids:[...]}. A rectangle starts at its top left corner. Components normally come from the schematic (pcb_do action:'import'); deleted shapes, texts and components cannot be put back by a rollback, tracks and vias can.

NameTypeReqDescription
allowErrorsboolean–Keep the change even if it adds rule errors (they are still reported).
guardboolean–Default true. false skips the rule checks.
keepGoingboolean––
opsarrayyes–
rebuildboolean–Default true: refill pours before the rule check.
rollbackboolean–Default true: take everything back on a failed op or a new rule error.
timeoutMsinteger–Default 300000.
trialboolean–Do it, report the rule check, then take everything back.
unitstring––
verboseboolean––

No output schema declared.

No examples provided.

pcb_export ~166

Export from the active PCB to a file and return its path: gerber (zip for fabrication), pnp (pick and place csv), bom, netlist, step, obj (3D), dxf, dsn (for external routers), ipc356, ipc2581, odb, testpoints, info, altium, pads, view (picture of what the canvas shows). Nothing is ordered: EasyEDA's ordering functions are never called.

NameTypeReqDescription
formatstringyes–
optionsobject–Passed to h.pcb.exportFile: {name?, type?, unit?, layers?, objects?, ...}.
pathstring–Absolute file path or directory. Default: ~/.easyeda-mcp/out/
timeoutMsinteger–Default 180000.

No output schema declared.

No examples provided.

pcb_read ~255

Read the active PCB (open one with pcb_do action:'open'). what: 'info' (layers, rule set, outline size, counts), 'parts' (components; pads:true adds pad coordinates and nets), 'tracks', 'vias', 'shapes' (polylines, pours, regions, fills, texts), 'nets' (pads, track length, tracks and vias per net; `net` for one), 'unrouted' (pads still waiting for a connection), 'drc' (design rule check with the list of errors). Coordinates are in mil with y up; unit:'mm' switches to millimetres.

NameTypeReqDescription
desarray–parts: only these designators.
layer––tracks: layer number or name (top, bottom, topsilk, outline, inner1...).
maxinteger–drc: how many errors to list (default 60).
maxCharsinteger––
netstring–tracks, vias, nets: only this net.
padsboolean–parts: include pad coordinates.
saveTostring––
unitstring––
whatstring––

No output schema declared.

No examples provided.

sch_draw ~745

Apply a list of drawing operations to the active schematic page as ONE change: afterwards either all of it is on the page or none of it. The netlist is read before and after (guard): nets with different names that became one net are a short, and a short takes the whole change back, as does a failed op or an `expect` that does not hold; the report says what happened to the nets (connected, joined, dropped, split, renamed) and `restored:true` confirms that the netlist is back to what it was. trial:true does the change, reports, and takes it back in any case (a dry run on the real editor). ops: {op:'wire',line:[x1,y1,x2,y2,...],net?} | {op:'part',lcsc:'C1234'|device:{libraryUuid,uuid},x,y,rot?,mirror?,des?} | {op:'flag',kind:'Ground'|'Power'|'AnalogGround'|'ProtectGround',net,x,y,rot?} | {op:'port',dir:'IN'|'OUT'|'BI',net,x,y,rot?} | {op:'move',part:'R1',x?,y?,rot?,mirror?} | {op:'set',part,props:{designator?,name?}} | {op:'nc',pin:'U1.3'} | {op:'unname',wire:id} | {op:'rewire',wire:id,line} | {op:'delete',wires?:[ids],parts?:[ids|designators],others?:[ids of texts/shapes]} | {op:'text',x,y,text,size?,rot?,color?} | {op:'rect',x,y,w,h} (x,y top left) | {op:'circle',x,y,r} | {op:'line',line:[...]} (drawing line, not a wire) | {op:'attr',part,key:'Designator'|'Name',x?,y?,rot?,visible?,value?} (move or edit a label of a part). Notes: y points up; a wire with `net` gets a visible label; EasyEDA merges a new wire with every wire whose end it touches (reported as merged, the old wire keeps its id); pins touching end to end without a wire are not connected; parts placed without `des` are numbered by EasyEDA (unique across all pages); the netlist also numbers any other 'R?' part of the project; deleted parts cannot be put back by a rollback.

NameTypeReqDescription
allowShorts––true, or a list of net names that may be joined on purpose.
expectobject–{NET: ['U1.3','R2.1']}: these nets must consist of exactly these pins afterwards, else the change is taken back. A key starting with '?' checks an unnamed net.
guardboolean–Default true. false skips the two netlists (faster, no short detection).
keepGoingboolean–Continue after a failed op (turns rollback off unless it is set).
opsarrayyes–
rollbackboolean–Default true: take everything back on a failed op, a short or a failed expect. false keeps what was done.
timeoutMsinteger–Default 180000.
trialboolean–Do it, report what it does to the nets, then take everything back.
verboseboolean–Return an entry for every op, not only parts and problems.

No output schema declared.

No examples provided.

sch_export ~160

Export from the active schematic to a file and return its path: pdf (look at the real drawing; open the path with the Read tool), png, svg, netlist (PADS text), bom (csv), view (image of what the canvas currently shows; may be stale).

NameTypeReqDescription
formatstringyes–
optionsobject–Passed to h.exportFile: {name?, params?, resolution?, type?, tabId?, object?, objectParams?}. pdf exports the current page by default; object: 'Current Schematic' or 'All Schematic' for more.
pathstring–Absolute file path or directory. Default: ~/.easyeda-mcp/out/
timeoutMsinteger–Default 90000.

No output schema declared.

No examples provided.

sch_read ~333

Read the active schematic page compactly. what: 'summary' (counts, designators, net names of wires), 'parts' (components with pin coordinates), 'wires', 'snapshot' (parts+flags+wires), 'nets' (whole-schematic netlist {net: pins}), 'net' (one net by name or by pin like 'U1.3', needs `net`), 'check' (floating pins, single-pin nets, unnumbered or duplicate designators, EasyEDA's own rule check counts), 'overlaps' (parts, labels and wires lying on each other), 'free' (room for a block of `size` [w,h]: rectangles touching nothing), 'boxes' (the rectangle every object takes). Filter with `des` (designators) or `region` [x1,y1,x2,y2]. Pin x,y is the outer end where a wire attaches.

NameTypeReqDescription
countinteger–what:'free': how many places to return (default 1).
desarray–Only these designators (parts).
maxCharsinteger––
netstring–Net name (wires, net) or a pin like U1.3 (net).
pinsboolean–Include pins for parts/snapshot (default true).
regionarray–[x1,y1,x2,y2]
saveTostring––
sizearray–what:'free': [width, height] of the block to fit.
whatstring––

No output schema declared.

No examples provided.

Install

How do I install the EasyEDA MCP server?

EasyEDA MCP runs locally as an npm package, launched with npx -y easyeda-pro-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · easyeda-pro-mcp

# add to Claude Code
claude mcp add zzvllvzz-easyeda-mcp -- npx -y easyeda-pro-mcp
Common questions

What is the EasyEDA MCP server?

EasyEDA MCP is listed in the public MCP registry as io.github.zzvllvzz/easyeda-mcp. Read and draw EasyEDA Pro schematics and PCBs through a bridge extension, with guarded edits. This page covers its npm package (easyeda-pro-mcp).

Is the EasyEDA MCP server safe to use?

EasyEDA MCP scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the EasyEDA MCP server expose?

EasyEDA MCP exposes 12 tools: eda_status, eda_exec, eda_call, eda_api, sch_read, and 7 more. Their descriptions and schemas cost roughly 4,363 tokens of context every time the server is loaded.

Is the EasyEDA MCP server still maintained?

EasyEDA MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the EasyEDA MCP server under?

EasyEDA MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the EasyEDA MCP server?

VerifyMCP ran 15 checks on EasyEDA MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about EasyEDA MCP: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.