MCP SearXNG vs Agent Search MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP SearXNG vs Agent Search MCP
In-depth architectural comparison of the MCP SearXNG and Agent Search MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP SearXNG
Search & Data Extraction · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Agent Search MCP
Search & Data Extraction · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose MCP SearXNG if you need specialized Search & Data Extraction tools running via a local process. Choose Agent Search MCP if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP SearXNG when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Free multi-engine MCP search server — 8 free engines (DDG, Sogou, Bing, Baidu, Wikipedia, Startpage, Yandex, Mojeek), waterfall progressive search, multi-source verification, content enrichment, news search, language auto-detection, CLI. Zero API keys needed. npx agent-search-mcp
Category & Scope
Tools & Capabilities Breakdown
MCP SearXNG Tools (4)
searxng_web_search
Searches the web using SearXNG and returns a list of results, each with a title, URL, and content snippet. CRITICAL: The required parameter name is exactly `query` (not `prompt`, `q`, or any other name). Calls an external SearXNG instance; availability depends on the `SEARXNG_URL` configuration. Use `pageno` to paginate results; combine `time_range` and `language` to narrow scope. When `engines` and `time_range` are both provided, every selected engine must explicitly advertise time-range support via SearXNG /config; otherwise the request is rejected before search. To read the full text of a result URL, follow up with `web_url_read`.
searxng_search_suggestions
Returns autocomplete suggestions from the configured SearXNG instance. Use this to refine vague or partial queries before searching.
searxng_instance_info
Discovers capabilities from all reachable configured SearXNG instances via /config, including categories.common/available, engines.common/available, defaults, locales, and plugins.
web_url_read
Fetches a URL and returns readable content as markdown. Content-type aware: HTML is converted to markdown; JSON is pretty-printed; plain text, YAML, TOML, and XML are returned as fenced readable text. PDF text extraction is supported with bounded input, output, page count, time, concurrency, and memory; OCR is not supported. Binary, media, archive, and octet-stream downloads other than PDFs are intentionally rejected instead of being returned as raw bytes. When the operator configures browser solvers, mcp-searxng attempts FlareSolverr first and then Byparr only after a busy or transient-unavailable acquisition; cache hits bypass acquisition and a final busy or unavailable provider uses one uncached direct-fetch fallback. Three modes: (1) Full content — omit filtering params; use `startChar`/`maxLength` to paginate large pages. (2) Section extraction — set `section` to return content under a specific heading. (3) Headings only — set `readHeadings: true` to list all headings (mutually exclusive with other filtering params). Returns an error string if the URL is unreachable or content cannot be extracted. Use after `searxng_web_search` to read the full content of individual result URLs.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP SearXNG is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Agent Search MCP belongs to Search & Data Extraction using local stdio subprocess. Select MCP SearXNG when you need capabilities focused on search & data extraction and Agent Search MCP when you require tools for search & data extraction.
Quick public-web search for current facts and discovery.
Use free_search_advanced for verification or domain filters. Use free_extract for one selected URL.
Returns compact multi-source evidence with confidence, relevance, source_count, stop_reason, evidence_budget, and partialFailures. Provider families are counted once even when several adapters use the same upstream. Optional API providers run only when credentials and policy allow.
@readOnly true @idempotent true — makes outbound HTTP requests to configured search engines. Injection detection and SSRF protection active.
free_search_advanced
Verification-oriented search with domain filters and waterfall fallback.
Use for claim checking, Chinese-source search, or publisher restrictions. Start with free_search for quick discovery. The response exposes source_count, stop_reason, evidence_budget, and partialFailures.
@readOnly true @idempotent true — runs waterfall progressive search across policy-allowed engines. Makes outbound HTTP requests to search engines and optionally to Jina Reader for content enrichment.
free_extract
Extract one selected URL into clean Markdown.
Use after search when snippets are insufficient, or for a URL supplied by the user. It fetches one page; it does not search or bulk-extract URLs.
Behavior: Makes an outbound HTTP request to Jina Reader (r.jina.ai) which fetches and converts the page to markdown. Has SSRF protection: blocks private IPs, localhost, and metadata endpoints. 10s request timeout — pages exceeding this will fail with a timeout error. HTTP errors (4xx, 5xx) are returned as structured error responses.
fetch_github_readme
Fetch README content from a GitHub repository.
Best for: Getting project documentation quickly.
Not recommended for: Non-GitHub URLs — use free_extract instead.
@readOnly true @idempotent true — makes outbound HTTP requests to raw.githubusercontent.com.
fetch_csdn_article
Fetch content from a CSDN blog article.
Best for: Chinese developer blog content on CSDN.
Not recommended for: Other Chinese sites — use free_extract instead.
@readOnly true @idempotent true — makes outbound HTTP requests to the CSDN article URL.
fetch_juejin_article
Fetch content from a Juejin article.
Best for: Chinese developer articles on Juejin.
Not recommended for: Non-Juejin content — use free_extract instead.
@readOnly true @idempotent true — makes outbound HTTP requests to juejin.cn API.
search_with_synthesis
Opt-in deep search with waterfall verification and content enrichment. Returns structured results plus a prompt_hint; it does not call an external LLM.
Use when multi-source evidence needs a synthesis handoff. free_search is the default for discovery; this path uses more tokens and network time.
@readOnly true @idempotent true — runs waterfall search across free+paid engines with content enrichment.