Ext Ops Panel
Open dashboard
Comparison

apify-scraper vs AgentRead — bounded web context

apify-scraper is a plugin bundle for AI coding tools published by MSApps-Mobile. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AgentRead — bounded web context is an MCP server published by agentread-json-api.army20160422.chatgpt.site. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplaceapify-scraperAgentRead — bounded web context
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.1
No figure published
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

apify-scraper vs AgentRead — bounded web context
Factapify-scraperAgentRead — bounded web context
Marketplaces that list it11
Stars (GitHub) (differs)9No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (agentread-json-api.army20160422.chatgpt.site/agent/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/msapps-mobile/claude-pluginsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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

apify-scraper

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

Full Apify web scraping platform integration for Claude. Run Actors, manage datasets, key-value stores, schedules, webhooks, and tasks — all from within Claude. Includes 27 tools covering the full Apify platform.

AgentRead — bounded web context

In its own words, on Official MCP Registry:

Free HTML parsing; static web context at 0.01 USDC via x402. Paid reads need a wallet adapter.

How to run each

apify-scraper As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install apify-scraper@claude-community

AgentRead — bounded web context As a remote MCP server

Claude Code
claude mcp add --transport http agentread https://agentread-json-api.army20160422.chatgpt.site/agent/mcp

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

Only AgentRead — bounded web context has a remote endpoint we 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

The marketplaces of AgentRead — bounded web context publish no settings it asks for, so we do not compare settings.

What it can do: apify-scraper · What it can do: AgentRead — bounded web context · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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