Ext Ops Panel
Open dashboard
Comparison

io.github.palthainon/oldweb-diagnostics vs net.softricks/idig-dns

io.github.palthainon/oldweb-diagnostics is an MCP server published by palthainon. Marketplaces we read that list it: 1 (Official MCP Registry). net.softricks/idig-dns is an MCP server published by softricks.net. 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

Where each is published
Marketplaceio.github.palthainon/oldweb-diagnosticsnet.softricks/idig-dns
Official MCP Registry Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
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

io.github.palthainon/oldweb-diagnostics vs net.softricks/idig-dns
Factio.github.palthainon/oldweb-diagnosticsnet.softricks/idig-dns
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.oldweb.tech/diagnostics/mcp)Remote server (mcp.softricks.net/sse)
Transport (differs)Streamable HTTPSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/palthainon/mycodegithub.com/kbhave/mcp-service-idig
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 14 h agoResponded 45 h 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.palthainon/oldweb-diagnostics

In its own words, on Official MCP Registry:

Public DNS, HTTPS and deployment checks, plus offline email header and delivery-log tracing.

net.softricks/idig-dns

In its own words, on Official MCP Registry:

Professional DNS diagnostics: 14 tools for DNS, DNSSEC, email security, SSL, and propagation.

How to run each

io.github.palthainon/oldweb-diagnostics As a remote MCP server

Claude Code
claude mcp add --transport http oldweb-diagnostics https://mcp.oldweb.tech/diagnostics/mcp

net.softricks/idig-dns As a remote MCP server

Claude Code
claude mcp add --transport sse idig-dns https://mcp.softricks.net/sse

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of net.softricks/idig-dns nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.palthainon/oldweb-diagnostics · What it can do: net.softricks/idig-dns · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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