@datadive-tools/mcp vs io.github.houtini-ai/seo-audit-console
@datadive-tools/mcp is an MCP server published by @datadive-tools. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.houtini-ai/seo-audit-console is an MCP server published by houtini-ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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.houtini-ai/seo-audit-console | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.20.1 Downloads/month (npm): 1 986 Downloads/week (npm): 793 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.17.0 Downloads/month (npm): 2 312 Downloads/week (npm): 1 205 Forks (GitHub): 7 Stars (GitHub): 86 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.17.0 Downloads/month (npm): 2 312 Downloads/week (npm): 1 205 Forks (GitHub): 7 Stars (GitHub): 86 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 | @datadive-tools/mcp | io.github.houtini-ai/seo-audit-console |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 86 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 7 (better) |
| Last release (differs) | 2026-10-27 (better) | 2026-10-25 (worse) |
| Where it runs (differs) | On your machine (@datadive-tools/mcp) | On your machine (@houtini/seo-audit-console) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 3 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/data-dive-tools/datadive-mcp | github.com/houtini-ai/seo-audit |
| Changes in the last 7 days (differs) | 1 | 3 |
| First seen (differs) | 2026-10-12 | 2026-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
@datadive-tools/mcp
MCP server for DataDive — query your niches, keywords, competitors, and Rank Radar data from Claude Desktop, Claude Code, or Cursor.
io.github.houtini-ai/seo-audit-console
Technical SEO in Claude: GSC + crawl + DataForSEO - audit, portfolio, market sizing, content recon.
How to run each
@datadive-tools/mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.houtini-ai/seo-audit-console As a local MCP server: npm package
claude mcp add --env "CRUX_API_KEY=<YOUR_CRUX_API_KEY>" --env "DATAFORSEO_PASSWORD=<YOUR_DATAFORSEO_PASSWORD>" --env "GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS>" --env "MAJESTIC_API_KEY=<YOUR_MAJESTIC_API_KEY>" --transport stdio seo-audit-console -- npx -y @houtini/seo-audit-consoleRequires: CRUX_API_KEY (secret), DATAFORSEO_PASSWORD (secret), GOOGLE_APPLICATION_CREDENTIALS, MAJESTIC_API_KEY (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
The marketplaces of @datadive-tools/mcp publish no settings it asks for, so we do not compare settings.
What it can do: @datadive-tools/mcp · What it can do: io.github.houtini-ai/seo-audit-console · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.