Реализация сервера MCP, интегрирующаяся с SearXNG, предоставляющая возможности метапоиска, ориентированные на конфиденциальность.
Мета-поиск : объединяет результаты из нескольких поисковых систем.
Конфиденциальность : без отслеживания и профилирования пользователей
Несколько категорий : поддержка общих тем, новостей, науки, файлов, изображений, видео и многого другого.
Поддержка языков : поиск на определенных языках или на всех языках
Фильтрация по временному диапазону : фильтрация результатов по дню, неделе, месяцу или году.
Безопасный поиск : три уровня фильтрации безопасного поиска
Поддержка отката : несколько экземпляров SearXNG для надежности
Related MCP server: SearXNG MCP Server
Чтобы автоматически установить SearXNG MCP Server для Claude Desktop через Smithery :
npx -y @smithery/cli install @kevinwatt/mcp-server-searxng --client claudenpm install -g @kevinwatt/mcp-server-searxngmcp-server-searxngНажмите «+ Добавить сервер MCP» в Dive Desktop.
Скопируйте и вставьте эту конфигурацию:
{
"mcpServers": {
"searxng": {
"command": "npx",
"args": [
"-y",
"@kevinwatt/mcp-server-searxng"
]
}
}
}Нажмите «Сохранить», чтобы установить сервер MCP.
веб-поиск
Выполнять метапоиск в нескольких поисковых системах
Входные данные:
query (строка): Условия поиска
page (номер, необязательно): Номер страницы (по умолчанию: 1)
language (строка, необязательно): Код языка (например, «en», «all», по умолчанию: «all»)
categories (массив, необязательно): Категории поиска (по умолчанию: ['general'])
Доступно: «общие», «новости», «наука», «файлы», «изображения», «видео», «музыка», «социальные сети», «it»
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. Подробности см. в файле LICENSE.
Вам нужен запущенный локальный экземпляр 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 следующим образом:
Изменить список поисковых систем
Настройте параметры безопасности
Настроить язык пользовательского интерфейса
Изменить ограничения API
Подробные параметры конфигурации см. в документации SearXNG.
SEARXNG_INSTANCES : список URL-адресов экземпляров SearXNG, разделенных запятыми. По умолчанию: 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 provided, the description carries the full burden. It discloses that the tool 'returns relevant results from multiple search engines combined,' adding useful behavioral context about result aggregation. However, it doesn't cover aspects like rate limits, authentication needs, or error handling, leaving gaps for a search tool.
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?
The description is front-loaded with the core purpose and efficiently lists key features in a single, well-structured sentence. Every phrase adds value without redundancy, making it appropriately sized and easy to parse.
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?
Given no annotations, no output schema, and moderate schema coverage (67%), the description is somewhat complete but has gaps. It covers the tool's purpose and key features but lacks details on return format, error cases, or advanced usage, which could help an agent use it more effectively in varied contexts.
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 description coverage is 67%, and the description adds some value by mentioning support for 'multiple search categories, languages, time ranges and safe search filtering,' which aligns with parameters like categories, language, time_range, and safesearch. However, it doesn't provide additional semantics beyond what the schema already documents, such as details on query formatting or page behavior.
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 clearly states the tool 'performs a web search using SearXNG' and specifies it's for 'general queries, news, articles and online content.' It provides a specific verb ('performs') and resource ('web search'), though it doesn't need to distinguish from siblings since none exist.
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 mentions it's 'ideal for general queries, news, articles and online content,' which implies usage context but doesn't explicitly state when to use it versus alternatives or any exclusions. No sibling tools exist, so differentiation isn't needed, but broader guidance is limited.
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. Dates show when Glama detected each change.
web_searchWith 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Search the web, images, videos, news, and local businesses with robust filters, freshness controls…
Multi-engine search for AI agents. Trust scoring, local corpus, MCP-native. Self-hostable, BYOK.
Federated commerce search across independent WooCommerce merchants. Keyless, read-only MCP server.
Live web search, image search, topic filters and full-text fetch over our own crawled index.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevinwatt/mcp-server-searxng'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
