Ext Ops Panel
Open dashboard
Comparison

Private Web Search vs CallAI SEO

Private Web Search is an MCP server published by nickclyde. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). CallAI SEO is an MCP server published by callaiapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplacePrivate Web SearchCallAI SEO
Docker MCP Catalog Listed
Version: sha256:5617c4c60f48
Forks (GitHub): 196
Pulls (Docker Hub): 1 039 956
Stars (Docker Hub): 11
Stars (GitHub): 1 573
Not marked · First seen
Not listed
PyPI (MCP servers) Listed
Version: 0.7.0
Downloads/month (PyPI): 72 062
Downloads/week (PyPI): 35 727
Forks (GitHub): 196
Stars (GitHub): 1 573
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

Private Web Search vs CallAI SEO
FactPrivate Web SearchCallAI SEO
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1 573 (better)0 (worse)
Pulls (Docker Hub) (differs)1 039 956No figure on Docker Hub
Forks (GitHub) (differs)196 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/duckduckgo)Remote server (api.callaiapi.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/nickclyde/duckduckgo-mcp-servergithub.com/hanshengcc/callai-seo-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-03
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 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

Private Web Search

In its own words, on Docker MCP Catalog:

Community-maintained server for DuckDuckGo search. Not published by or affiliated with DuckDuckGo.

CallAI SEO

In its own words, on Official MCP Registry:

Live SEO data: Google/Bing SERP, AI Overview sources, keyword difficulty, backlinks, page audits.

How to run each

Private Web Search As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio duckduckgo -- docker run -i --rm mcp/duckduckgo

CallAI SEO As a remote MCP server

Claude Code
claude mcp add --transport http seo https://api.callaiapi.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only CallAI SEO has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of CallAI SEO publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Private Web Search · What it can do: CallAI SEO · Compare two other plugins

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