Kicad (PyPI) MCP Server

kicad-mcp PyPI v0.1.6

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

KiCad MCP Server

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([queryCurrentFrameType, query_symbol_library]) co-exist with external-action tools ([draw_arc, draw_bezier, draw_rectangle, create_hier_sheet, create_class_label, create_textbox, create_table]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [queryCurrentFrameType, query_symbol_library] → sinks [draw_arc, draw_bezier, draw_rectangle, create_hier_sheet, create_class_label, create_textbox, c

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow queryCurrentFrameType → draw_arc

Tools 72

Each tool and what it can reach — statically extracted from the published source.

  • create_class_labelnetwork egress
  • create_hier_sheetnetwork egress
  • create_tablenetwork egress
  • create_textboxnetwork egress
  • draw_arcnetwork egress
  • draw_beziernetwork egress
  • draw_rectanglenetwork egress
  • query_symbol_libraryingests untrusted input
  • queryCurrentFrameTypeingests untrusted input
  • closeCurrentFrameno sensitive capability
Show 62 more tools ↓
  • closeFrameno sensitive capability
  • create_common_textno sensitive capability
  • create_global_labelno sensitive capability
  • create_hier_labelno sensitive capability
  • create_local_labelno sensitive capability
  • create_pcb_padno sensitive capability
  • create_pcb_trackno sensitive capability
  • create_pcb_viano sensitive capability
  • create_symbol_libraryno sensitive capability
  • create_symbol_pinno sensitive capability
  • deleteToolno sensitive capability
  • draw_circleno sensitive capability
  • draw_multi_busesno sensitive capability
  • draw_multi_wiresno sensitive capability
  • exportNetlistno sensitive capability
  • generate_net_labelsno sensitive capability
  • get_current_kicad_projectno sensitive capability
  • importNonKicadSchematicno sensitive capability
  • importVectorGraphicsFileno sensitive capability
  • modify_pcb_footprint_referenceno sensitive capability
  • modify_pcb_pad_drill_shapeno sensitive capability
  • modify_pcb_pad_drill_sizeno sensitive capability
  • modify_pcb_pad_numberno sensitive capability
  • modify_pcb_pad_sizeno sensitive capability
  • modify_symbol_referenceno sensitive capability
  • modify_symbol_valueno sensitive capability
  • move_pcb_footprintno sensitive capability
  • move_pcb_padno sensitive capability
  • move_symbolno sensitive capability
  • openEditTextAndGraphicPropertyDialogno sensitive capability
  • openFindAndReplaceDialogno sensitive capability
  • openFindDialogno sensitive capability
  • openFrameno sensitive capability
  • openPageSettingDlgno sensitive capability
  • openPlotDlgno sensitive capability
  • openPrintDlgno sensitive capability
  • openSchematicSetupDlgno sensitive capability
  • openSymbolLibraryBrowserno sensitive capability
  • place_all_net_labelsno sensitive capability
  • place_symbolno sensitive capability
  • query_pcb_all_footprint_infono sensitive capability
  • query_pcb_footprint_infono sensitive capability
  • query_pcb_layer_namesno sensitive capability
  • query_symbol_pinno sensitive capability
  • rotate_pcb_footprintno sensitive capability
  • rotate_pcb_padno sensitive capability
  • rotate_symbolno sensitive capability
  • runERCCheckno sensitive capability
  • saveAsFrameno sensitive capability
  • saveFrameno sensitive capability
  • selectAllItemsno sensitive capability
  • set_pcb_footprint_positionno sensitive capability
  • set_pcb_pad_new_positionno sensitive capability
  • showBusSyntaxHelpno sensitive capability
  • showSpiceSimulatorno sensitive capability
  • toggleDesignBlockPanelno sensitive capability
  • toggleHierarchyPanelno sensitive capability
  • toggleNetNavigatorPanelno sensitive capability
  • togglePropertyPanelno sensitive capability
  • toggleSearchPanelno sensitive capability
  • unSelectAllItemsno sensitive capability
  • zoomViewno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.6 latest A 95/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/kicad-mcp/badge.svg)](https://mcptrustchecker.com/registry/kicad-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/kicad-mcp"><img src="https://mcptrustchecker.com/registry/kicad-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/kicad-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan kicad-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Kicad 5

Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →

More in Developer Tools