与 SearXNG 集成的 MCP 服务器实现，提供以隐私为中心的元搜索功能。
元搜索：整合来自多个搜索引擎的结果
注重隐私：不跟踪，不进行用户分析
多种类别：支持一般、新闻、科学、文件、图像、视频等
语言支持：以特定语言或所有语言搜索
时间范围过滤：按日、周、月或年过滤结果
安全搜索：三级安全搜索过滤
后备支持：多个 SearXNG 实例以确保可靠性
Related MCP server: SearXNG MCP Server
npm install -g @kevinwatt/mcp-server-searxngmcp-server-searxng在 Dive Desktop 中点击“+ 添加 MCP 服务器”
复制并粘贴此配置：
{
"mcpServers": {
"searxng": {
"command": "npx",
"args": [
"-y",
"@kevinwatt/mcp-server-searxng"
]
}
}
}点击“保存”安装 MCP 服务器
网络搜索
跨多个引擎执行元搜索
输入：
query （字符串）：搜索词
page （数字，可选）：页码（默认值：1）
language （字符串，可选）：语言代码（例如，“en”，“all”，默认值：“all”）
categories （数组，可选）：搜索类别（默认值：['general']）
可用：“一般”、“新闻”、“科学”、“文件”、“图像”、“视频”、“音乐”、“社交媒体”、“它”
time_range （字符串，可选）：时间过滤器（日/周/月/年）
safesearch （数字，可选）：安全搜索级别（0：无，1：中等，2：严格，默认值：1）
git clone https://github.com/kevinwatt/mcp-server-searxng.git
cd mcp-server-searxng
npm install
npm run build
npm start此 MCP 服务器采用 MIT 许可证。详情请参阅许可证文件。
您需要运行一个本地 SearXNG 实例。设置方法如下：
# Create config directory
mkdir -p searxng
# Create config file
tee searxng/settings.yml << EOF
use_default_settings: true
server:
bind_address: "0.0.0.0"
secret_key: "CHANGE_THIS_TO_SOMETHING_SECURE" # Generate a random key
port: 8080
search:
safe_search: 0
formats:
- html
- json
engines:
- name: google
engine: google
shortcut: g
- name: duckduckgo
engine: duckduckgo
shortcut: d
- name: bing
engine: bing
shortcut: b
server.limiter: false
EOF
# Start container
docker run -d \
--name searxng \
-p 8080:8080 \
-v "$(pwd)/searxng:/etc/searxng" \
searxng/searxng# Test JSON API with curl
curl -v 'http://localhost:8080/search?q=test&format=json'
# Or visit in browser
http://localhost:8080/search?q=test# Stop container
docker stop searxng
# Remove container
docker rm searxng
# View container logs
docker logs searxng
# Enable auto-start on boot
docker update --restart always searxng--restart always标志可确保：
Docker 守护进程启动时容器自动启动
如果容器崩溃，则会自动重启
容器停止后会自动重启，除非用户明确停止
编辑searxng/settings.yml如下：
修改搜索引擎列表
调整安全设置
配置 UI 语言
更改 API 限制
有关详细配置选项，请参阅SearXNG 文档
SEARXNG_INSTANCES ：以逗号分隔的 SearXNG 实例 URL 列表默认值： http://localhost:8080
SEARXNG_USER_AGENT ：请求的自定义 User-Agent 标头默认值： MCP-SearXNG/1.0
NODE_TLS_REJECT_UNAUTHORIZED ：设置为“0”以绕过 SSL 证书验证（用于使用自签名证书的开发）默认值：未定义（启用 SSL 验证）
包含所有选项的示例配置：
{
"mcpServers": {
"searxng": {
"name": "searxng",
"command": "npx",
"args": [
"-y",
"@kevinwatt/mcp-server-searxng"
],
"env": {
"SEARXNG_INSTANCES": "http://localhost:8080,https://searx.example.com",
"SEARXNG_USER_AGENT": "CustomBot/1.0",
"NODE_TLS_REJECT_UNAUTHORIZED": "0"
}
}
}
}⚠️ 警告：不建议在生产环境中禁用 SSL 证书验证。
Performs a web search using SearXNG, ideal for general queries, news, articles and online content. Supports multiple search categories, languages, time ranges and safe search filtering. Returns relevant results from multiple search engines combined.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| page | No | Page number (default 1) | |
| language | No | Search language code (e.g. 'en', 'zh', 'jp', 'all') | all |
| categories | No | ||
| time_range | No | all_time | |
| safesearch | No | 0: None, 1: Moderate, 2: Strict |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses that results come from multiple search engines combined and that filtering options are supported, but it does not mention limitations, rate limits, result count, or whether the operation is read-only. This is adequate but not deeply transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each earning its place: purpose, supported controls, and output behavior. The most important information is front-loaded, with no filler or repeated schema content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a six-parameter tool with no output schema and no annotations, the description covers purpose and high-level behavior but not result format, pagination behavior, or edge cases like empty results. It is sufficient for basic invocation but leaves some context to be inferred.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67%, and the schema already documents query, page, language, and safesearch values. The description adds a high-level statement that categories, languages, time ranges, and safe search are supported, but it does not add details beyond the schema. The generic references are not enough to meaningfully augment the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Performs a web search using SearXNG', and enumerates concrete use cases such as general queries, news, articles, and online content. It also distinguishes itself from a plain search by noting results come from multiple search engines combined. With no sibling tools to contrast against, this is maximum clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states the tool is 'ideal for general queries, news, articles and online content', which provides clear usage context. It does not state explicit when-not-to-use conditions or alternatives, but that is reasonable since no sibling tools are listed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
web_searchScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as performing web searches using SearXNG, making it distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'web_search' follows a clear verb_noun pattern and is appropriate for its function.
One tool is too few for a server named 'SearXNG MCP Server', which suggests a broader scope for search functionality. While the tool covers general web searches, the lack of additional tools (e.g., for image search, news-specific searches, or configuration) makes the set feel thin and underdeveloped for the domain.
The tool surface is severely incomplete for a search server. It only provides general web search, missing obvious extensions like image search, video search, news search, or advanced filtering tools that would be expected in a comprehensive search interface, leading to significant gaps in functionality.
Search the web, images, videos, news, and local businesses with robust filters, freshness controls…
Web search with quality scores; web pages are read on your computer by the local server.
Google, Bing, DuckDuckGo and Google Maps search results, free without an API key.
Search privacy tools, guides, stacks and glossary, find app replacements, run privacy checks.
