Electronic component sourcing, BOM management, and PCB design workflows.
A Model Context Protocol (MCP) server for sourcing electronic parts with multi-EDA integration. Parts MCP enables AI assistants to search for electronic components, compare prices, check availability, and process BOMs from popular EDA tools. It provides a unified interface for component sourcing workflows powered by the Source Parts API. Tool | BOM Format | Status | ------|------------|--------|…
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A Model Context Protocol (MCP) server for sourcing electronic parts with multi-EDA integration. Parts MCP enables AI assistants to search for electronic components, compare prices, check availability, and process BOMs from popular EDA tools. It provides a unified interface for component sourcing workflows powered by the Source Parts API. Tool | BOM Format | Status | ------|------------|--------| KiCad | CSV, XML | Full support + CLI integration | Altium Designer | CSV, XLS | Full support |…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.