MCP-searxng

MCP server that exposes a single tool to perform web searches through a configured searXNG instance (default http://localhost:8080 via SEARXNG_URL).

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ Search mcp search searxng agentic-ai web-search
⚙ Agent Friendliness
42
/ 100
Can an agent use this?
🔒 Security
29
/ 100
Is it safe for agents?
⚡ Reliability
24
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
50
Error Messages
0
Auth Simplicity
90
Rate Limits
10

🔒 Security

TLS Enforcement
30
Auth Strength
10
Scope Granularity
0
Dep. Hygiene
55
Secret Handling
60

The MCP wrapper itself has no documented auth/authorization and exposes a simple search capability. Security largely depends on how searXNG is configured (TLS, authentication, and rate limiting). README suggests SEARXNG_URL default is http://localhost:8080 (not TLS), and provides no guidance about sanitizing logs, handling upstream errors, or restricting the MCP server’s network exposure.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
40
Error Recovery
20
AF Security Reliability

Best When

You have (or control) a searXNG instance you trust and want a lightweight MCP wrapper for basic search.

Avoid When

You need strong authentication/authorization for search operations, detailed error/rate-limit semantics, or you cannot control the security posture of the upstream searXNG endpoint.

Use Cases

  • Enable LLM agents to perform live web search via MCP
  • Route agent search requests through an existing self-hosted searXNG deployment
  • Provide a simple search tool interface for agentic workflows

Not For

  • Production use without validating searXNG security, authentication, and rate-limiting
  • Use cases requiring authenticated, scoped user access to search results
  • Environments requiring strict compliance controls over where queries/results are sent

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication mechanisms are described for the MCP server. Upstream searXNG authentication (if any) is not documented in this README.

Pricing

Free tier: No
Requires CC: No

Open-source package; costs depend on your searXNG hosting and any infrastructure you run.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Single tool described; no guidance on query formatting, result size limits, or failure modes
  • Relies on SEARXNG_URL; if upstream searXNG is slow/unreachable, agent behavior may degrade without documented retry/backoff
  • No documented rate-limit handling for the MCP layer

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for MCP-searxng.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered