Ext Ops Panel
Open dashboard
Comparison

ScrapeMole Pkgs vs Package Intel MCP

ScrapeMole Pkgs is an MCP server published by scrapemole.pages.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Package Intel MCP is an MCP server published by selflabbs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceScrapeMole PkgsPackage Intel MCP
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

ScrapeMole Pkgs vs Package Intel MCP
FactScrapeMole PkgsPackage Intel MCP
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (pkgs.scrapemole.workers.dev/mcp)Remote server (package.selflabbs.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/selflabbs/package-intel-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 3 days agoNot responding since 2026-10-17

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

ScrapeMole Pkgs

In its own words, on Official MCP Registry:

Pay-per-call x402 npm and PyPI package metadata, versions, search, download counts.

Package Intel MCP

In its own words, on Official MCP Registry:

Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.

How to run each

ScrapeMole Pkgs As a remote MCP server

Claude Code
claude mcp add --transport http pkgs https://pkgs.scrapemole.workers.dev/mcp

Package Intel MCP As a remote MCP server

Claude Code
claude mcp add --transport http package-intel-mcp https://package.selflabbs.com/mcp

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

Only the endpoint of ScrapeMole Pkgs responded at the last daily 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

Neither one's marketplaces publish the settings it asks for.

What it can do: ScrapeMole Pkgs · What it can do: Package Intel MCP · Compare two other plugins

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.

Where the data comes from: how the catalog is built