KiCad MCP Pro vs Supabase MCP Server
Both are Grade A and 0.8 points apart, so choose on what you weigh most. KiCad MCP Pro leads on supply-chain integrity and maintenance; Supabase MCP Server leads on adoption.
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.
- +3.4Maintenance: last push today, against 2d ago
- +3.1Safety / Integrity: 100% of recent commits signed, against 88%
- +1.7Transparency: OSSF Scorecard 8.5 against 6.5
Connect Supabase to your AI assistants
Choose Supabase MCP Server if adoption matters most.
- +4.8Adoption: 67.9k weekly downloads against 5.7k
Where they differ
1 dimension identical: Identity 18.0 · Full evidence table
An independent, evidence-based trust comparison of KiCad MCP Pro and Supabase MCP Server, 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 | KiCad MCP Prooaslananka/kicad-mcp-pro | Supabase MCP Serversupabase/mcp |
|---|---|---|
| HVTrust score | 88.9 | 88.1 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #33 | #40 |
| Rank in MCP Servers | #7 | #8 |
| GitHub stars | 122 | 2.9k |
| Last updated | today | 2d ago |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 8.5 / 10 | 6.5 / 10 |
| License | MIT | Apache-2.0 |
| Downloads | 6k/wk | 68k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 23.1 | 20.0 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 15.7 | 14.0 |
| Maintenance / 20 | 20.0 | 16.6 |
| Adoption / 20 | 10.0 | 14.8 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 3 — Anthropic, Google Gemini, OpenAI | 1 — Supabase |
| 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 →