DomainDNA: Tech Stack Detector, WHOIS & Domain Age API vs Google Search Console
DomainDNA: Tech Stack Detector, WHOIS & Domain Age API is an MCP server published by CyberMax-tools. Marketplaces we read that list it: 1 (Official MCP Registry). Google Search Console is an MCP server published by acamolese. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-29. 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 |  DomainDNA: Tech Stack Detector, WHOIS & Domain Age API |  Google Search Console |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 No figure published Not marked · First seen |
Listed Version: 3.0.1 Downloads/month (PyPI): 986 Downloads/week (PyPI): 674 Forks (GitHub): 4 Stars (GitHub): 9 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 3.0.1 Downloads/month (PyPI): 986 Downloads/week (PyPI): 674 Forks (GitHub): 4 Stars (GitHub): 9 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 | DomainDNA: Tech Stack Detector, WHOIS & Domain Age API | Google Search Console |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 9 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (mcp-google-search-console) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 6, secrets among them: 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cybermax-tools/product-factory | github.com/acamolese/google-search-console-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-24 | no remote endpoint we check |
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
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.
Google Search Console
Google Search Console: SEO audits, performance queries, URL inspection, indexing checks.
How to run each
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
Google Search Console As a local MCP server: PyPI package
claude mcp add --env "GSC_CLIENT_SECRET=<YOUR_GSC_CLIENT_SECRET>" --env "GSC_REFRESH_TOKEN=<YOUR_GSC_REFRESH_TOKEN>" --transport stdio google-search-console-mcp -- uvx mcp-google-search-consoleRequires: GSC_CLIENT_SECRET (secret), GSC_REFRESH_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only DomainDNA: Tech Stack Detector, WHOIS & Domain Age API 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
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: DomainDNA: Tech Stack Detector, WHOIS & Domain Age API · What it can do: Google Search Console · 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.