Ext Ops Panel
Open dashboard
Comparison

@datadive-tools/mcp vs ai.explorium/mcp-explorium

@datadive-tools/mcp is an MCP server published by @datadive-tools. Marketplaces we read that list it: 1 (npm registry (MCP servers)). ai.explorium/mcp-explorium is an MCP server published by explorium.ai. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). 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

Where each is published
Marketplace@datadive-tools/mcpai.explorium/mcp-explorium
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
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 4
Stars (GitHub): 22
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:48f0b580857b
Forks (GitHub): 4
Pulls (Docker Hub): 13 214
Stars (Docker Hub): 0
Stars (GitHub): 22
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

@datadive-tools/mcp vs ai.explorium/mcp-explorium
Fact@datadive-tools/mcpai.explorium/mcp-explorium
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (worse)22 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub13 214
Forks (GitHub) (differs)0 (worse)4 (better)
Last release (differs)2026-10-27Not published
Where it runs (differs)On your machine (@datadive-tools/mcp)Remote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published12
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/data-dive-tools/datadive-mcpgithub.com/explorium-ai/mcp-explorium
Changes in the last 7 days (differs)10
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-23

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

In its own words, on npm registry (MCP servers):

MCP server for DataDive — query your niches, keywords, competitors, and Rank Radar data from Claude Desktop, Claude Code, or Cursor.

ai.explorium/mcp-explorium

In its own words, on Official MCP Registry:

Access live company and contact data from Explorium's AgentSource B2B platform.

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.

ai.explorium/mcp-explorium As a remote MCP server

Claude Code
claude mcp add --transport http mcp-explorium https://mcp-github-registry.explorium.ai/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ai.explorium/mcp-explorium has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of @datadive-tools/mcp publish no list of tools, so we do not compare tools.

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: ai.explorium/mcp-explorium · 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. 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.

Where the data comes from: how the catalog is built