Ext Ops Panel
Open dashboard
Comparison

Apify vs com.airaptr/raptr-domains

Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.airaptr/raptr-domains is an MCP server published by airaptr.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceApifycom.airaptr/raptr-domains
Docker MCP Catalog Listed
Version: sha256:42cc91f13363
Forks (GitHub): 368
Pulls (Docker Hub): 36 678
Stars (Docker Hub): 0
Stars (GitHub): 12 426
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

Apify vs com.airaptr/raptr-domains
FactApifycom.airaptr/raptr-domains
Marketplaces that list it11
Stars (GitHub) (differs)12 426 (better)0 (worse)
Pulls (Docker Hub) (differs)36 678No figure on Docker Hub
Forks (GitHub) (differs)368 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/apify-mcp-server)Remote server (api.airaptr.com/domains/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/apify/actors-mcp-servergithub.com/airaptr/airaptr.github.io
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 h 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

In its own words, on Docker MCP Catalog:

Apify is the world's largest marketplace of tools for web scraping, data extraction, and web automation. You can extract structured data from social media, e-commerce, search engines, maps, travel sites, or any other website.

com.airaptr/raptr-domains

In its own words, on Official MCP Registry:

Check and price up to 20 domain names at once; agents can register them, paying per request.

How to run each

Apify As a local MCP server: Docker image

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio apify-mcp-server -- docker run -i --rm -e APIFY_TOKEN mcp/apify-mcp-server

Requires: APIFY_TOKEN (secret)

com.airaptr/raptr-domains As a remote MCP server

Claude Code
claude mcp add --transport http raptr-domains https://api.airaptr.com/domains/mcp

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

Only com.airaptr/raptr-domains has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of com.airaptr/raptr-domains publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of com.airaptr/raptr-domains publish no settings it asks for, so we do not compare settings.

What it can do: Apify · What it can do: com.airaptr/raptr-domains · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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