Ext Ops Panel
Open dashboard
Comparison

DLBrowser vs io.github.babelwrap/babelwrap-mcp

DLBrowser is an MCP server published by DekryptLabs. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.babelwrap/babelwrap-mcp is an MCP server published by babelwrap. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceDLBrowserio.github.babelwrap/babelwrap-mcp
Official MCP Registry Listed
Version: 4.0.2
Downloads/month (PyPI): 115
Downloads/week (PyPI): 23
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 118
Downloads/week (npm): 25
Forks (GitHub): 1
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

DLBrowser vs io.github.babelwrap/babelwrap-mcp
FactDLBrowserio.github.babelwrap/babelwrap-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (dlbrowser)On your machine (babelwrap-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/dekryptlabs/dlbrowsergithub.com/babelwrap/babelwrap-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

DLBrowser

In its own words, on Official MCP Registry:

Self-healing web access for AI agents — recovers through bot blocks, captchas and JS pages.

io.github.babelwrap/babelwrap-mcp

In its own words, on Official MCP Registry:

MCP server for BabelWrap — give AI agents web browsing superpowers.

How to run each

DLBrowser As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DLBROWSER_API_KEY=<YOUR_DLBROWSER_API_KEY>" --transport stdio dlbrowser -- uvx dlbrowser

Requires: DLBROWSER_API_KEY (secret)

io.github.babelwrap/babelwrap-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "BABELWRAP_API_KEY=<YOUR_BABELWRAP_API_KEY>" --transport stdio babelwrap-mcp -- npx -y babelwrap-mcp

Requires: BABELWRAP_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

Only DLBrowser asks for

  • DLBROWSER_API_KEY (secret)

Only io.github.babelwrap/babelwrap-mcp asks for

  • BABELWRAP_API_KEY (secret)

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

What it can do: DLBrowser · What it can do: io.github.babelwrap/babelwrap-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