SearXNG와 통합되어 개인정보 보호에 중점을 둔 메타 검색 기능을 제공하는 MCP 서버 구현입니다.
메타 검색 : 여러 검색 엔진의 결과를 결합합니다.
개인정보 보호 중심 : 추적 없음, 사용자 프로파일링 없음
다양한 카테고리 : 일반, 뉴스, 과학, 파일, 이미지, 비디오 등 지원
언어 지원 : 특정 언어 또는 모든 언어로 검색
시간 범위 필터링 : 일, 주, 월 또는 연도별로 결과를 필터링합니다.
안전 검색 : 3단계 안전 검색 필터링
폴백 지원 : 안정성을 위한 여러 SearXNG 인스턴스
Related MCP server: SearXNG MCP Server
지엑스피1
mcp-server-searxngDive Desktop에서 "+ MCP 서버 추가"를 클릭하세요.
다음 구성을 복사하여 붙여넣으세요.
{
"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 라이선스에 따라 라이선스가 부여됩니다. 자세한 내용은 라이선스 파일을 참조하세요.
로컬 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 : 요청에 대한 사용자 정의 사용자 에이전트 헤더 기본값: MCP-SearXNG/1.0
NODE_TLS_REJECT_UNAUTHORIZED : SSL 인증서 검증을 우회하려면 '0'으로 설정합니다(자체 서명 인증서를 사용하는 개발의 경우). 기본값: 정의되지 않음(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.
