Private Web Search vs VistaLink Hotels
Private Web Search is an MCP server published by nickclyde. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). VistaLink Hotels is an MCP server published by vistalink.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5617c4c60f48 Forks (GitHub): 196 Pulls (Docker Hub): 1 025 213 Stars (Docker Hub): 11 Stars (GitHub): 1 572 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 572 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.0 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
| Fact | Private Web Search | VistaLink Hotels |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 572 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 1 025 213 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 196 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/duckduckgo) | Remote server (api.vistalink.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nickclyde/duckduckgo-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 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
Community-maintained server for DuckDuckGo search. Not published by or affiliated with DuckDuckGo.
VistaLink Hotels
Search 650,000 hotels, get each hotel's direct price with full offer lists, match rooms, book.
How to run each
Private Web Search As a local MCP server: Docker image
claude mcp add --transport stdio duckduckgo -- docker run -i --rm mcp/duckduckgo
VistaLink Hotels As a remote MCP server
claude mcp add --transport http hotels https://api.vistalink.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only VistaLink Hotels has a remote endpoint we check. How we check endpoints
Tools each declares
Only Private Web Search has
fetch_contentsearch
Only VistaLink Hotels has
get_hotel_detailssearch_hotels
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (VistaLink Hotels as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.
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: VistaLink Hotels · 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.