Ext Ops Panel
Open dashboard
Comparison

Vibe Prospecting vs ai.explorium/mcp-explorium

Vibe Prospecting is a plugin bundle for AI coding tools published by explorium-ai. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). 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-28. 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
MarketplaceVibe Prospectingai.explorium/mcp-explorium
Claude Code: claude-plugins-official Listed
Version: 0.1.107
Forks (GitHub): 4
Stars (GitHub): 272
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 0.1.107
Forks (GitHub): 4
Stars (GitHub): 272
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.1.107
Forks (GitHub): 4
Stars (GitHub): 272
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 202
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

Vibe Prospecting vs ai.explorium/mcp-explorium
FactVibe Prospectingai.explorium/mcp-explorium
Marketplaces that list it (differs)4 (better)2 (worse)
Stars (GitHub) (differs)272 (better)22 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub13 202
Forks (GitHub)44
Last release (differs)2026-10-16Not published
Where it runs (differs)Installs as a plugin bundleRemote 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
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/explorium-ai/vibeprospecting-plugingithub.com/explorium-ai/mcp-explorium
Changes in the last 7 days00
First seen2026-10-112026-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

Vibe Prospecting

In its own words, on Claude Code: claude-plugins-official:

Vibe Prospecting connects Claude to live B2B company and contact data so users can search, match, enrich, filter, and export prospects at scale. It turns natural-language requests into structured GTM workflows for lead generation, CRM enrichment, company research, executive discovery, and multi-step prospecting automation inside Claude Cowork and Claude Code.

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

Vibe Prospecting As a Claude Code plugin

Claude Code
/plugin install vibe-prospecting@claude-plugins-official

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 Vibe Prospecting publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Vibe Prospecting publish no settings it asks for, so we do not compare settings.

What it can do: Vibe Prospecting · What it can do: ai.explorium/mcp-explorium · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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