Ext Ops Panel
Open dashboard
Comparison

io.github.ScrapeGraphAI/scrapegraph-mcp vs io.github.bamchi/scrapi

io.github.ScrapeGraphAI/scrapegraph-mcp is an MCP server published by ScrapeGraphAI. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.bamchi/scrapi is an MCP server published by bamchi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplaceio.github.ScrapeGraphAI/scrapegraph-mcpio.github.bamchi/scrapi
Official MCP Registry Listed
Version: 1.0.1
Downloads/month (PyPI): 433
Downloads/week (PyPI): 121
Forks (GitHub): 38
Stars (GitHub): 115
Not marked · First seen
Listed
Version: 2.0.6
Downloads/month (npm): 185
Downloads/week (npm): 25
Forks (GitHub): 4
Stars (GitHub): 5
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:43e315d80397
Forks (GitHub): 38
Pulls (Docker Hub): 19 521
Stars (Docker Hub): 4
Stars (GitHub): 115
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

io.github.ScrapeGraphAI/scrapegraph-mcp vs io.github.bamchi/scrapi
Factio.github.ScrapeGraphAI/scrapegraph-mcpio.github.bamchi/scrapi
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)115 (better)5 (worse)
Pulls (Docker Hub) (differs)19 521No figure on Docker Hub
Forks (GitHub) (differs)38 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineRemote server (scrapi.ai/mcp)
Transport (differs)stdio, Streamable HTTPStreamable HTTP
Tools it declares (differs)8Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/scrapegraphai/scrapegraph-mcpgithub.com/bamchi/scrapi-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot checked yet

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

io.github.ScrapeGraphAI/scrapegraph-mcp

In its own words, on Official MCP Registry:

AI-powered web scraping and data extraction capabilities through ScrapeGraph API

io.github.bamchi/scrapi

In its own words, on Official MCP Registry:

Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.

How to run each

io.github.ScrapeGraphAI/scrapegraph-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "SGAI_API_KEY=<YOUR_SGAI_API_KEY>" --transport stdio scrapegraph-mcp -- uvx scrapegraph-mcp

Requires: SGAI_API_KEY (secret)

io.github.bamchi/scrapi As a remote MCP server

Claude Code
claude mcp add --transport http scrapi https://scrapi.ai/mcp

Requires: SCRAPI_API_KEY (secret)

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

Tools each declares

The marketplaces of io.github.bamchi/scrapi publish no list of tools, so we do not compare tools.

Settings each asks for

Only io.github.ScrapeGraphAI/scrapegraph-mcp asks for

  • SGAI_API_KEY (secret)

Only io.github.bamchi/scrapi asks for

  • SCRAPI_API_KEY (secret)

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

What it can do: io.github.ScrapeGraphAI/scrapegraph-mcp · What it can do: io.github.bamchi/scrapi · 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