io.github.matematicsolutions/de-eli-mcp vs Vermont Code
io.github.matematicsolutions/de-eli-mcp is an MCP server published by matematicsolutions. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Vermont Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  io.github.matematicsolutions/de-eli-mcp |  Vermont Code |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.4 Downloads/month (PyPI): 271 Downloads/week (PyPI): 218 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.5.4 Downloads/month (PyPI): 271 Downloads/week (PyPI): 218 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Not listed |
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 | io.github.matematicsolutions/de-eli-mcp | Vermont Code |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (de-eli-mcp) | Remote server (gateway.pipeworx.io/vermont-code/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/matematicsolutions/de-eli-mcp | github.com/pipeworx-io/mcp-vermont-code |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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
io.github.matematicsolutions/de-eli-mcp
German law MCP: legislation (NeuRIS), case law (RII, Open Legal Data), Bundestag DIP documents.
Vermont Code
Vermont Statutes Annotated — state statutes by citation.
How to run each
io.github.matematicsolutions/de-eli-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio de-eli-mcp -- uvx de-eli-mcpVermont Code As a remote MCP server
claude mcp add --transport http vermont-code https://gateway.pipeworx.io/vermont-code/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vermont Code has a remote endpoint we check. How we check endpoints
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: io.github.matematicsolutions/de-eli-mcp · What it can do: Vermont Code · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.