Ext Ops Panel
Open dashboard
Comparison

Private Web Search vs Search1API

Private Web Search is an MCP server published by nickclyde. Marketplaces we read that list it: 1 (Docker MCP Catalog). Search1API is a plugin bundle for AI coding tools published by Search1API. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
MarketplacePrivate Web SearchSearch1API
Docker MCP Catalog Listed
Version: sha256:5617c4c60f48
Forks (GitHub): 194
Pulls (Docker Hub): 904 187
Stars (Docker Hub): 11
Stars (GitHub): 1 532
Not marked · First seen
Not listed
Community marketplace superagents-lab/search1api-mcp Not listed Listed
Version: 1.2.1
Forks (GitHub): 38
Stars (GitHub): 173
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 Search1API
FactPrivate Web SearchSearch1API
Marketplaces that list it11
Stars (GitHub) (differs)1 532 (better)173 (worse)
Pulls (Docker Hub) (differs)904 187No figure on Docker Hub
Forks (GitHub) (differs)194 (better)38 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/duckduckgo)Remote server (mcp.search1api.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/nickclyde/duckduckgo-mcp-servergithub.com/superagents-lab/search1api-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)no remote endpoint we checkResponded 37 h ago, requires a key

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.

Search1API

In its own words, on Community GitHub marketplaces:

Search1API brings multi-engine search to AI agents, with Google, Bing, DuckDuckGo, Yahoo, and specialized sources including GitHub, Reddit, X, arXiv, Wikipedia, YouTube, WeChat, and Bilibili. Choose sources that fit your task and compare findings across them. Read full pages, search current news, discover site links, and explore GitHub and Hacker News trends. Browse selected results in interactive source cards, with expandable source lists and links to the original pages. Results include source URLs for citation.

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

Search1API As a Codex plugin

Codex
codex plugin marketplace add superagents-lab/search1api-mcp

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

Only Search1API has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Search1API 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: Search1API · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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