Ext Ops Panel
Open dashboard
Comparison

DirectCase Legal Search vs io.github.matematicsolutions/gb-eli-mcp

DirectCase Legal Search is an MCP server published by directcase.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.matematicsolutions/gb-eli-mcp is an MCP server published by matematicsolutions. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-28. 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

Where each is published
MarketplaceDirectCase Legal Searchio.github.matematicsolutions/gb-eli-mcp
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.5.3
Downloads/month (PyPI): 220
Downloads/week (PyPI): 176
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.5.3
Downloads/month (PyPI): 220
Downloads/week (PyPI): 176
Forks (GitHub): 0
Stars (GitHub): 0
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

DirectCase Legal Search vs io.github.matematicsolutions/gb-eli-mcp
FactDirectCase Legal Searchio.github.matematicsolutions/gb-eli-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.directcase.ai)On your machine (gb-eli-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedApache-2.0
Repository (differs)Not statedgithub.com/matematicsolutions/gb-eli-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

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

DirectCase Legal Search

In its own words, on Official MCP Registry:

Search national and EU case law, legislation and regulation, with citations you can verify.

io.github.matematicsolutions/gb-eli-mcp

In its own words, on Official MCP Registry:

MCP server for UK legislation, case law (Find Case Law), GOV.UK tribunal decisions and HMRC manuals.

How to run each

DirectCase Legal Search As a remote MCP server

Claude Code
claude mcp add --transport http directcase https://mcp.directcase.ai

io.github.matematicsolutions/gb-eli-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio gb-eli-mcp -- uvx gb-eli-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only DirectCase Legal Search 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: DirectCase Legal Search · What it can do: io.github.matematicsolutions/gb-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). 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.

Where the data comes from: how the catalog is built