Ext Ops Panel
Open dashboard
Comparison

dns-cache vs io.github.whois-api-llc/mcp-whoisxmlapi

dns-cache is an MCP server published by weiseer. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.whois-api-llc/mcp-whoisxmlapi is an MCP server published by whois-api-llc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacedns-cacheio.github.whois-api-llc/mcp-whoisxmlapi
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 135
Downloads/week (npm): 18
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.9.0
Downloads/month (npm): 508
Downloads/week (npm): 45
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

dns-cache vs io.github.whois-api-llc/mcp-whoisxmlapi
Factdns-cacheio.github.whois-api-llc/mcp-whoisxmlapi
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (@weiseer/dns-cache-mcp)On your machine (@whoisxmlapidotcom/mcp-whoisxmlapi)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 01, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/weiseer/dns-cache-mcpgithub.com/whoisxmlapi/mcp-whoisxmlapi
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

dns-cache

In its own words, on Official MCP Registry:

DNS/WHOIS/SSL/geo-IP cache MCP server for AI agents.

io.github.whois-api-llc/mcp-whoisxmlapi

In its own words, on Official MCP Registry:

34 WHOIS, DNS, IP, threat intelligence, email, and bulk tools for AI agents via WhoisXML API.

How to run each

dns-cache As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dns-cache -- npx -y @weiseer/dns-cache-mcp

io.github.whois-api-llc/mcp-whoisxmlapi As a local MCP server: npm package

Claude Code
claude mcp add --env "WHOISXMLAPI_TOKEN=<YOUR_WHOISXMLAPI_TOKEN>" --transport stdio mcp-whoisxmlapi -- npx -y @whoisxmlapidotcom/mcp-whoisxmlapi

Requires: WHOISXMLAPI_TOKEN (secret)

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

Only dns-cache asks for

  • DNS_CACHE_LOCAL_ONLY
  • DNS_CACHE_URL

Only io.github.whois-api-llc/mcp-whoisxmlapi asks for

  • WHOISXMLAPI_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: dns-cache · What it can do: io.github.whois-api-llc/mcp-whoisxmlapi · 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