io.github.erikirby/web-network-tools vs Domain Liveness
io.github.erikirby/web-network-tools is an MCP server published by erikirby. Marketplaces we read that list it: 1 (Official MCP Registry). Domain Liveness is an MCP server published by ottobot.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  io.github.erikirby/web-network-tools |  Domain Liveness |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Downloads/month (npm): 126 Downloads/week (npm): 42 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 1 052 Stars (GitHub): 7 464 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
| Fact | io.github.erikirby/web-network-tools | Domain Liveness |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 7 464 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 052 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@erikirby/web-network-tools) | Remote server (domain-liveness-mcp.ottobot2025.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/erikirby/toolcompare-fyi | github.com/modelcontextprotocol/registry |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 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.erikirby/web-network-tools
DNS lookup, WHOIS, SSL checker, and HTTP status tools. Uses public APIs only, no scraping.
Domain Liveness
Is this business's website still there? Checks apex and www, and DNS separately from HTTP.
How to run each
io.github.erikirby/web-network-tools As a local MCP server: npm package
claude mcp add --transport stdio web-network-tools -- npx -y @erikirby/web-network-toolsDomain Liveness As a remote MCP server
claude mcp add --transport http domain-liveness https://domain-liveness-mcp.ottobot2025.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Domain Liveness 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: io.github.erikirby/web-network-tools · What it can do: Domain Liveness · 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.