MCP Retrieval vs PrismSearch
MCP Retrieval is an MCP server published by Role1776. Marketplaces we read that list it: 1 (Official MCP Registry). PrismSearch is an MCP server published by xiaonerner0821. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |  MCP Retrieval |  PrismSearch |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.10 Forks (GitHub): 2 Stars (GitHub): 23 Not marked · First seen |
Listed Version: 0.3.3 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
| Fact | MCP Retrieval | PrismSearch |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 23 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release (differs) | 2026-10-24 (worse) | 2026-11-02 (better) |
| Where it runs (differs) | On your machine (ghcr.io/role1776/mcp-retrieval:0.1.10) | On your machine (prismsearch) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 23, secrets among them: 2 | 5, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/role1776/mcp-retrieval | github.com/xiaonerner0821/prismsearch |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-29 |
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
MCP Retrieval
Local Go MCP server: DuckDuckGo/Bing web + image search, readability scraping to Markdown.
PrismSearch
Multi-engine web, image and WeChat search with page/PDF fetching over local MCP stdio.
How to run each
MCP Retrieval As a local MCP server: Docker image
claude mcp add --env "PROXY_LOGIN=<YOUR_PROXY_LOGIN>" --env "PROXY_PASSWORD=<YOUR_PROXY_PASSWORD>" --transport stdio mcp-retrieval -- docker run -i --rm -e PROXY_LOGIN -e PROXY_PASSWORD ghcr.io/role1776/mcp-retrieval:0.1.10Requires: PROXY_LOGIN (secret), PROXY_PASSWORD (secret)
PrismSearch As a local MCP server: npm package
claude mcp add --env "BRAVE_API_KEY=<YOUR_BRAVE_API_KEY>" --env "GOOGLE_API_KEY=<YOUR_GOOGLE_API_KEY>" --transport stdio prismsearch -- npx -y prismsearchRequires: BRAVE_API_KEY (secret), GOOGLE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only MCP Retrieval asks for
DEFAULT_DOCUMENT_CHARSDEFAULT_IMAGESDEFAULT_RESULTSDEFAULT_TIMEOUT_MSLOG_MODEMAX_DOCUMENT_CHARSMAX_IDLE_CONNS_PER_HOSTMAX_IMAGESMAX_QUERIESMAX_RESULTSMAX_TIMEOUT_MSMCP_NAME
Show the remaining 11
MCP_PATHMCP_TRANSPORTMIN_TIMEOUT_MSPROXY_HOSTPROXY_LOGIN (secret)PROXY_PASSWORD (secret)PROXY_PORTPROXY_SCHEMESERVER_PORTSERVER_READ_TIMEOUTSERVER_WRITE_TIMEOUT
Only PrismSearch asks for
BRAVE_API_KEY (secret)GOOGLE_API_KEY (secret)GOOGLE_CSE_IDPRISMSEARCH_CONFIGPRISMSEARCH_HOME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: MCP Retrieval · What it can do: PrismSearch · Compare two other plugins
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.