Is KiCad MCP Pro safe to use?

KiCad MCP Pro has an HVTrust score of 86.5/100 (Grade A), ranked #60 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for KiCad MCP Pro?

KiCad MCP Pro scores 86.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 102 GitHub stars and is categorized under MCP Servers.

KiCad MCP Pro

oaslananka/kicad-mcp-pro

AI-ready MCP server for KiCad: automate schematic, PCB, ERC/DRC, DFM, BOM and manufacturing review from Claude, Cursor, Copilot and other AI agents.

MCP Servers Python Listed MIT

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

OSSF Scorecard 7.2 / 10

Provenance Attested

Signed commits 100%

Last push 2d ago

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 86.5/100 (Grade A), ranked #60 of 1325 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 7.2/10; 100% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How KiCad MCP Pro compares in MCP Servers

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

Where the 86.5 comes from

HVTrust dimensions vs the MCP Servers average

86.5 / 100 · 100.0% confidence

KiCad MCP Pro MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

21.5 / 25

11.2 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.6 / 17

2.4 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

9.4 / 20

2.2 above avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

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

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 Get email alerts for KiCad MCP Pro View MCP Servers Report missing data

67.8

Activity sub-score · out of 100

#18

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

102

Forks

Last Push

2026-09-24

2 days ago

Commits (4 wk)

121

Downloads (7d)

2,601

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #61

Analysis

Activity Inputs

67.8 / 100

StarsRepository reach

12.1 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

5.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm, pypi attestation

OSSF Scorecard

7.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 0

CII-Best-Practices 2

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 7

Security-Policy 10

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 3

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 7.2/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 2 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

3 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
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-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

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

2026-08-08

Newly Listed

First tracked at rank #54

GitHub → PyPI: kicad-mcp-pro npm: kicad-mcp-pro

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON