Ext Ops Panel
Open dashboard
Comparison

Data Breach Notification Deadlines vs io.github.matematicsolutions/de-eli-mcp

Data Breach Notification Deadlines is an MCP server published by Nero-Engine. Marketplaces we read that list it: 1 (Official MCP Registry). 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)). 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
MarketplaceData Breach Notification Deadlinesio.github.matematicsolutions/de-eli-mcp
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.5.4
Downloads/month (PyPI): 271
Downloads/week (PyPI): 218
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.5.4
Downloads/month (PyPI): 271
Downloads/week (PyPI): 218
Forks (GitHub): 0
Stars (GitHub): 4
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

Data Breach Notification Deadlines vs io.github.matematicsolutions/de-eli-mcp
FactData Breach Notification Deadlinesio.github.matematicsolutions/de-eli-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (breach-notification-deadlines.nerolabs.workers.dev/mcp)On your machine (de-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/de-eli-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 34 h agono 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

Data Breach Notification Deadlines

In its own words, on Official MCP Registry:

Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced.

io.github.matematicsolutions/de-eli-mcp

In its own words, on Official MCP Registry:

German law MCP: legislation (NeuRIS), case law (RII, Open Legal Data), Bundestag DIP documents.

How to run each

Data Breach Notification Deadlines As a remote MCP server

Claude Code
claude mcp add --transport http breach-notification-deadlines https://breach-notification-deadlines.nerolabs.workers.dev/mcp

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

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

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

Only Data Breach Notification Deadlines 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: Data Breach Notification Deadlines · What it can do: io.github.matematicsolutions/de-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