updated 2026-11-11 00:08 UTC

KiCad MCP Pro

Repository Website by oaslananka

MCP server for KiCad, connecting AI agents to schematic and PCB workflows, ERC/DRC validation, DFM checks, BOM analysis, and manufacturing preparation—with controlled edits and human-gated release workflows.

MCP Servers Python Listed MIT

Is KiCad MCP Pro safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 8.5 / 10
Provenance Attested
Signed commits 100%
Last push yesterday
Advisories None known
Compare KiCad MCP Pro

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: KiCad MCP Pro scores 88.5/100 (Grade A), ranked #55 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 8.5/10; 100% of recent commits are signed; no published advisory affects its latest release (kicad-mcp-pro, kicad-mcp-pro); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How KiCad MCP Pro could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships KiCad MCP Pro and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/oaslananka/kicad-mcp-pro, MIT, last pushed 2026-11-10. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 8.5/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review6
    • Branch Protection4
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 5
    Code-Review 6
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 10
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 10
    SAST 10
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked and attested

    • npm kicad-mcp-pro Source link points back to this repo Build provenance attested
    • PyPI kicad-mcp-pro Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest releases checked: kicad-mcp-pro 4.10.0, kicad-mcp-pro 4.10.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues KiCad MCP Pro’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How KiCad MCP Pro compares in MCP Servers

  1. #12 Ha MCP 88.7 +0.2
  2. #13 Cap Js MCP Server 88.6 +0.1
  3. #14 KiCad MCP Pro 88.5 this agent
  4. #15 ARC-1 88.5 ±0
  5. #16 Mongodb MCP Server 88.5 ±0

Bars show each HVTrust score; the tick marks KiCad MCP Pro’s 88.5.

Where the 88.5 comes from

HVTrust dimensions vs the MCP Servers average

88.5 / 100 · 100.0% confidence

KiCad MCP Pro MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
23.1 / 25
12.3 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
15.7 / 17
3.4 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.6 above avg 12.3
AdoptionLog-scaled stars · package downloads
10.8 / 20
3.2 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-11-05
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-11-05
Rank Moved
Rank dropped 22 spots (#38 → #60)
2026-10-25
Rank Moved
Rank rose 18 spots (#57 → #39)
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
Compare with another agent
View MCP Servers Report missing data
71.1
Activity sub-score · out of 100
#14
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
207
Forks
35
Last Push
2026-11-10
yesterday
Commits (4 wk)
397
Downloads (7d)
8,972
npm+pypi
HN mentions (30d)
—
Open Issues
19
Rank Change
▼3
was #52

Analysis

Activity Inputs

71.1 / 100
StarsRepository reach
13.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
7.2 / 20

Common questions about KiCad MCP Pro

Public supply-chain signals for KiCad MCP Pro are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but KiCad MCP Pro carries less obvious unverified-evidence risk than projects with thin signals.
Does KiCad MCP Pro publish package provenance?
Yes. KiCad MCP Pro's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does KiCad MCP Pro have an OpenSSF Scorecard?
KiCad MCP Pro has an OpenSSF Scorecard score of 8.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is KiCad MCP Pro actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does KiCad MCP Pro use?
KiCad MCP Pro ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are KiCad MCP Pro's commits signed?
100% of the last 100 commits to KiCad MCP Pro are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
KiCad MCP Pro appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • database
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to KiCad MCP Pro's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-11-05
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain KiCad MCP Pro?

For maintainers

HVTrust scores KiCad MCP Pro from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 9Surface 2Delisted 1Listed 1HVTrust 1Grade 1Provenance 1MCP 1Surface 1
2026-11-05
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-11-05
Rank Moved
Rank dropped 22 spots (#38 → #60)
2026-10-25
Rank Moved
Rank rose 18 spots (#57 → #39)
2026-10-22
Rank Moved
Rank dropped 10 spots (#46 → #56)
2026-10-09
Rank Moved
Rank rose 19 spots (#57 → #38)
2026-10-08
Rank Moved
Rank rose 12 spots (#69 → #57)
2026-10-06
Rank Moved
Rank rose 14 spots (#83 → #69)
2026-10-05
Rank Moved
Rank dropped 16 spots (#67 → #83)
2026-10-01
Rank Moved
Rank dropped 14 spots (#56 → #70)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 545 spots (#606 → #61)
2026-09-23
HVTrust Changed
HVTrust up 52.7pts (33.6 → 86.3)
2026-09-22
Newly Listed
First tracked at rank #606
2026-09-21
Removed From Active Tracking
Removed from active tracking
GitHub → Website → PyPI: kicad-mcp-pro npm: kicad-mcp-pro

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 88.5 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/kicad-mcp-pro.svg)](https://hvtracker.net/agents/kicad-mcp-pro)
HTML:
<a href="https://hvtracker.net/agents/kicad-mcp-pro"><img src="https://hvtracker.net/badge/kicad-mcp-pro.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON