pyslang-mcp vs io.github.daedalus/mcp-sigrok
pyslang-mcp is an MCP server published by ariklapid. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.daedalus/mcp-sigrok is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  pyslang-mcp |  io.github.daedalus/mcp-sigrok |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (PyPI): 127 Downloads/week (PyPI): 36 Forks (GitHub): 4 Stars (GitHub): 23 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 71 Downloads/week (PyPI): 25 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | pyslang-mcp | io.github.daedalus/mcp-sigrok |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 23 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (pyslang-mcp) | On your machine (mcp-sigrok) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ariklapid/pyslang-mcp | github.com/daedalus/mcp-sigrok |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
pyslang-mcp
Compiler-backed read-only Verilog and SystemVerilog project analysis.
io.github.daedalus/mcp-sigrok
MCP server exposing sigrok-cli functionality for logic analyzer hardware and protocol decoding
How to run each
pyslang-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio pyslang-mcp -- uvx pyslang-mcpio.github.daedalus/mcp-sigrok As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-sigrok -- uvx mcp-sigrokCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: pyslang-mcp · What it can do: io.github.daedalus/mcp-sigrok · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.