digline vs Calibration Explorer
digline is an MCP server published by digline.dev. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Calibration Explorer is an MCP server published by m-sanchez. 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 |  digline |  Calibration Explorer |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.3 Downloads/month (PyPI): 1 700 Downloads/week (PyPI): 582 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
Listed Version: 0.2.0 Downloads/month (npm): 272 Downloads/week (npm): 81 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.6.3 Downloads/month (PyPI): 1 700 Downloads/week (PyPI): 582 Forks (GitHub): 2 Stars (GitHub): 9 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 | digline | Calibration Explorer |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 9 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release (differs) | 2026-10-26 | Not published |
| Where it runs (differs) | On your machine (digline-mcp) | On your machine (@m-sanchez/calibration-explorer-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/digline/digline | github.com/m-sanchez/calibration-explorer |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen (differs) | 2026-10-12 | 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
digline
Read, measure and explain LLM eval runs of a digline suite. Cannot promote a baseline.
Calibration Explorer
Check classifier confidence against accuracy, fit temperature scaling and save local reports.
How to run each
digline As a local MCP server: PyPI package
claude mcp add --transport stdio digline-mcp -- uvx digline-mcp --root "<YOUR_ROOT>"Requires: --root
Calibration Explorer As a local MCP server: npm package
claude mcp add --transport stdio calibration-explorer -- npx -y @m-sanchez/calibration-explorer-mcp --input-root "<YOUR_INPUT_ROOT>" --output-root "<YOUR_OUTPUT_ROOT>"Requires: --input-root, --output-root
Commands 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: digline · What it can do: Calibration Explorer · 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.