Cap Js MCP Server vs KiCad MCP Pro
Both are Grade A and 0.1 points apart, so choose on what you weigh most. Cap Js MCP Server leads on adoption; KiCad MCP Pro leads on supply-chain integrity and maintenance.
MCP server for AI-assisted development of CAP applications
Choose Cap Js MCP Server if adoption matters most.
- +0.7Adoption: 68.1k weekly downloads against 8.4k
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.
Choose KiCad MCP Pro if supply-chain integrity and maintenance matter most.
- +2.9Maintenance: last push today, against 5d ago
- +1.0Safety / Integrity: 100% of recent commits signed, against 94%
- +0.5Transparency: OSSF Scorecard 8.5 against 7.9
Where they differ
1 dimension identical: Identity 18.0 · Full evidence table
An independent, evidence-based trust comparison of Cap Js MCP Server and KiCad MCP Pro, two MCP Servers projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | Cap Js MCP Servercap-js/mcp-server | KiCad MCP Prooaslananka/kicad-mcp-pro |
|---|---|---|
| HVTrust score | 88.4 | 88.5 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #55 | #52 |
| Rank in MCP Servers | #15 | #13 |
| GitHub stars | 118 | 190 |
| Last updated | 5d ago | today |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 7.9 / 10 | 8.5 / 10 |
| License | Apache-2.0 | MIT |
| Downloads | 68k/wk | 8k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 22.1 | 23.1 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 15.2 | 15.7 |
| Maintenance / 20 | 17.1 | 20.0 |
| Adoption / 20 | 11.4 | 10.7 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 1 — Anthropic | 4 — Anthropic, Google Gemini, OpenAI, … |
| Requires API keys | No | No |
| Plugin surface | plugins | plugins |
| Provenance drift | Match | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →