io.github.hostinger/hostinger-api-mcp vs DomainDNA: Tech Stack Detector, WHOIS & Domain Age API
io.github.hostinger/hostinger-api-mcp is an MCP server published by hostinger. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). DomainDNA: Tech Stack Detector, WHOIS & Domain Age API is an MCP server published by shawmena-dotcom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 3.0.0 Downloads/month (npm): 88 830 Downloads/week (npm): 66 261 Forks (GitHub): 58 Stars (GitHub): 161 Not marked · First seen |
Listed Version: 1.0.2 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:53ba798e692f Forks (GitHub): 58 Pulls (Docker Hub): 23 446 Stars (Docker Hub): 2 Stars (GitHub): 161 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 | io.github.hostinger/hostinger-api-mcp | DomainDNA: Tech Stack Detector, WHOIS & Domain Age API |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 161 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 23 446 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 58 | No figure on GitHub |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (mcp.apify.com) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 118 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hostinger/api-mcp-server | github.com/shawmena-dotcom/product-factory |
| Changes in the last 7 days (differs) | 9 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | not checked yet |
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.hostinger/hostinger-api-mcp
MCP server for Hostinger API
DomainDNA: Tech Stack Detector, WHOIS & Domain Age API
DomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record.
How to run each
io.github.hostinger/hostinger-api-mcp As a remote MCP server
claude mcp add --transport http hostinger-api-mcp https://mcp.hostinger.com
Requires: HOSTINGER_API_TOKEN (secret)
DomainDNA: Tech Stack Detector, WHOIS & Domain Age API
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.hostinger/hostinger-api-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of DomainDNA: Tech Stack Detector, WHOIS & Domain Age API publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of DomainDNA: Tech Stack Detector, WHOIS & Domain Age API publish no settings it asks for, so we do not compare settings.
What it can do: io.github.hostinger/hostinger-api-mcp · What it can do: DomainDNA: Tech Stack Detector, WHOIS & Domain Age API · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.