Ext Ops Panel
Open dashboard
Comparison

ai.explorium/mcp-explorium vs io.github.Ali1041/leadloadz

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). io.github.Ali1041/leadloadz is an MCP server published by Ali1041. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceai.explorium/mcp-exploriumio.github.Ali1041/leadloadz
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 4
Stars (GitHub): 22
Not marked · First seen
Listed
Version: 1.1.3
Downloads/month (npm): 178
Downloads/week (npm): 32
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:48f0b580857b
Forks (GitHub): 4
Pulls (Docker Hub): 13 202
Stars (Docker Hub): 0
Stars (GitHub): 22
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

ai.explorium/mcp-explorium vs io.github.Ali1041/leadloadz
Factai.explorium/mcp-exploriumio.github.Ali1041/leadloadz
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)22 (better)0 (worse)
Pulls (Docker Hub) (differs)13 202No figure on Docker Hub
Forks (GitHub) (differs)4 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineOn your machine (@leadloadz/mcp-server)
Transport (differs)Streamable HTTP, stdiostdio
Tools it declares (differs)12Not published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/explorium-ai/mcp-exploriumgithub.com/ali1041/leadloadz-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-23no 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

ai.explorium/mcp-explorium

In its own words, on Official MCP Registry:

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

io.github.Ali1041/leadloadz

In its own words, on Official MCP Registry:

B2B lead search and email verification MCP server

How to run each

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

io.github.Ali1041/leadloadz As a local MCP server: npm package

Claude Code
claude mcp add --env "LEADLOADZ_API_KEY=<YOUR_LEADLOADZ_API_KEY>" --transport stdio leadloadz -- npx -y @leadloadz/mcp-server

Requires: LEADLOADZ_API_KEY (secret)

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 io.github.Ali1041/leadloadz publish no list of tools, so we do not compare tools.

Settings each asks for

Only ai.explorium/mcp-explorium asks for

  • API_ACCESS_TOKEN (secret)

Only io.github.Ali1041/leadloadz asks for

  • LEADLOADZ_API_BASE
  • LEADLOADZ_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: ai.explorium/mcp-explorium · What it can do: io.github.Ali1041/leadloadz · 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.

Where the data comes from: how the catalog is built