Easyeda MCP Pro
MCP server for EasyEDA Pro, connecting AI agents to schematic and PCB workflows, controlled design operations, DRC, BOM sourcing, board analysis, and manufacturing export—with profile-gated tools and safety controls.
Is Easyeda MCP Pro safe? Strong public trust posture, backed by multiple independent signals.
Compare Easyeda MCP Pro
How does it stack up against its MCP Servers neighbours?
- Firecrawl MCP Server +0.1 higher
- Apify MCP Server +0.1 higher
- Containers Kubernetes MCP Server same score
In detail: Easyeda MCP Pro scores 89.6/100 (Grade A), ranked #35 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 9/10; 100% of recent commits are signed; no published advisory affects its latest release (easyeda-mcp-pro); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Chain of custody
Scanners check what the code says. This traces who ships Easyeda 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.
-
Source Signed
github.com/oaslananka/easyeda-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.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 9.0/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review7
- Branch Protection4
- Signed Releases10
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies10
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 4CI-Tests 10CII-Best-Practices 7Code-Review 7Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 10License 10Maintained 10Packaging 10Pinned-Dependencies 10SAST 10Security-Policy 10Signed-Releases 10Token-Permissions 10Vulnerabilities 10 -
Published packages Linked and attested
- npm easyeda-mcp-pro Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: easyeda-mcp-pro 1.13.1. No published advisory affects it (OSV, checked 2026-11-10).
Changes to this chain
- 2026-11-02 License changed from NOASSERTION to MIT
- 2026-09-23 Package provenance attestation detected
- 2026-09-16 License changed from MIT to NOASSERTION
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 Easyeda 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.
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 Easyeda MCP Pro compares in MCP Servers
- #7 Firecrawl MCP Server 89.7 +0.1
- #8 Apify MCP Server 89.7 +0.1
- #9 Easyeda MCP Pro 89.6 this agent
- #10 Containers Kubernetes MCP Server 89.6 ±0
- #11 SearXNG Search 88.9 −0.7
Bars show each HVTrust score; the tick marks Easyeda MCP Pro’s 89.6.
Where the 89.6 comes from
HVTrust dimensions vs the MCP Servers average
89.6 / 100 · 100.0% confidenceEasyeda MCP Pro MCP Servers average (779 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
66.9 / 100Common questions about Easyeda MCP Pro
Does Easyeda MCP Pro publish package provenance?
Does Easyeda MCP Pro have an OpenSSF Scorecard?
Is Easyeda MCP Pro actively maintained?
What license does Easyeda MCP Pro use?
Are Easyeda MCP Pro's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Easyeda 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.
Maintain Easyeda MCP Pro?
For maintainers
HVTrust scores Easyeda 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/easyeda-mcp-pro)
<a href="https://hvtracker.net/agents/easyeda-mcp-pro"><img src="https://hvtracker.net/badge/easyeda-mcp-pro.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON