Desearch vs Hub MCP
A side-by-side look at the Desearch and Hub MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Desearch for developer tools work as a local process; choose Hub MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Desearch when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DESEARCH_API_KEY.
Choose Hub MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HUB_PAT_TOKEN, MCP_AUTH_TOKEN. - You want tools like
search, query, architectures.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 35/100 · Fair | 77/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | DESEARCH_API_KEY | HUB_PAT_TOKENMCP_AUTH_TOKEN |
Tools & capabilities
Desearch tools
No tool names declared yet. Check the project README from the listing page.
Hub MCP tools 35
searchSearch repositories and content using Search V4 APIquerySearch query parameter (string, required)architecturesFilter on architectures (string, optional)badgesFilter by image content type badges (string, optional)categoriesFilter on categories (string, optional)extension_reviewedFilter on reviewed extensions (boolean, optional)fromNumber of documents to skip for pagination (number, optional)imagesFilter on image names (string, optional)operating_systemsFilter on operating systems (string, optional)orderChange the ordering of results (string, optional)sizeMaximum number of results to return (number, optional)sortSort results by search field (string, optional)- +23 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Desearch
{
"mcpServers": {
"desearch": {
"command": "npx",
"args": [
"-y",
"desearch-mcp-server"
],
"env": {
"DESEARCH_API_KEY": "YOUR_DESEARCH_API_KEY_HERE"
}
}
}
}
Hub MCP
{
"mcpServers": {
"docker-hub-mcp": {
"url": "https://docs.docker.com/ai/gordon/mcp/yaml/"
}
}
}
Frequently asked questions
Desearch is categorized under Developer Tools and uses a local stdio subprocess. Hub MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Desearch for developer tools work and Hub MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Desearch has no declared pricing — check the project's own site. Hub MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add desearch and docker-hub-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Desearch has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Hub MCP has 77/100 (Great) with 37 views, 0 installs and 170 GitHub stars.
