Lex API MX vs io.github.matematicsolutions/jp-eli-mcp
Lex API MX is an MCP server published by Julio-Patron. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.matematicsolutions/jp-eli-mcp is an MCP server published by matematicsolutions. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  Lex API MX |  io.github.matematicsolutions/jp-eli-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 319 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.3 Downloads/month (PyPI): 147 Downloads/week (PyPI): 69 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.3.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 319 Forks (GitHub): 0 Stars (GitHub): 0 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 | Lex API MX | io.github.matematicsolutions/jp-eli-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | On your machine (lex-api-mx-mcp) | On your machine (jp-eli-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/julio-patron/lexapi-mx | github.com/matematicsolutions/jp-eli-mcp |
| 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
Lex API MX
Legislación federal mexicana vigente con fuente, checksum y vigencia para agentes de IA
io.github.matematicsolutions/jp-eli-mcp
MCP server for Japan's e-Gov law search API: search, fetch, and cite national legislation.
How to run each
Lex API MX As a local MCP server: PyPI package
claude mcp add --env "LEX_API_MX_KEY=<YOUR_LEX_API_MX_KEY>" --transport stdio lex-api-mx -- uvx lex-api-mx-mcpRequires: LEX_API_MX_KEY (secret)
io.github.matematicsolutions/jp-eli-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio jp-eli-mcp -- uvx jp-eli-mcpCommands 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
The marketplaces of io.github.matematicsolutions/jp-eli-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Lex API MX · What it can do: io.github.matematicsolutions/jp-eli-mcp · 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). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.