공개 SearXNG 인스턴스를 쿼리하고 HTML 콘텐츠를 JSON 결과로 구문 분석하는 MCP 서버
제가 본 모든 SearXNG용 MCP 서버는 출력 형식으로 "json"을 사용합니다. SearXNG MCP 서버를 코딩하는 데는 확실히 더 빠른 방법이지만, JSON 형식을 제공하지 않는 거의 모든 공개 서버에서는 제대로 작동하지 않습니다.
이 서버는 최대 3개의 공개 SearXNG 서버(하나는 기본으로, 다른 하나는 대체 서버로 사용)에서 데이터를 읽고 그 결과를 JSON으로 구문 분석합니다.
Related MCP server: mcp-searxng
npm install mcp-serxng-public 통해 설치합니다.
서버가 설치된 경우 실행 구성은 다음과 같습니다.
지엑스피1
( https://searx.space/ 의 모든 서버를 선택한 서버로 사용할 수 있습니다)
서버는 하나의 엔드포인트( search 를 노출합니다. 엔드포인트는 두 개의 인수를 받습니다. query - 검색 쿼리와 선택적 time_range - https://docs.searxng.org/dev/search\_api.html 사양에 따라 시간 범위 매개변수( day , month 또는 year )를 받습니다.
반환되는 것은 객체의 배열입니다.
[
{
"url": "https://github.com/searxng/searxng",
"summary": "You can start SearXNG using make run in the terminal or by pressing Ctrl+Shift+B"
},
{
"url": "https://searx.bndkt.io/",
"summary": "Powered by searxng - 2025.3.22+5986629c6 — a privacy-respecting, open metasearch engine Source code | Issue tracker | Engine stats | Public instances | Contact instance maintainer"
},
{
"url": "https://docs.searxng.org/"
"summary": "SearXNG is a free internet metasearch engine which aggregates results from up to 243 search services. Users are neither tracked nor profiled. Additionally, SearXNG can be used over Tor …"
}
{
"url": "https://en.wikipedia.org/wiki/SearXNG",
"summary": "SearXNG is federated, and as such is hosted by several instances, public and private. Private instances are hosted on a local network, or run on the user's desktop computer itself, and are …"
}
]Performs a web search for a given query using the public SearXNG search servers. Returns an array of result objects with 'url' and 'summary' for each result.
| Name | Required | Description | Default |
|---|---|---|---|
| detailed | No | Optionally, if true, will perform a more thorough search - will ask for more pages of results and will merge results from multiple servers. Warning: this might overload the servers and cause errors. Do not set to true by default unless explicitly asked to perform a detailed or comprehensive query. | |
| language | No | The optional language code for the search (e.g., en, es, fr). | |
| query | Yes | The search query. | |
| time_range | No | The optional time range for the search, from: [day, week, month, year]. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, open-world, non-idempotent, and non-destructive behavior. The description adds valuable context beyond this: it specifies the search servers used (public SearXNG), warns about server overload risks with the 'detailed' parameter, and describes the return format. However, it doesn't mention rate limits or authentication needs.
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 two sentences that efficiently convey the tool's purpose, method, and output. Every sentence adds value: the first defines the action and resource, and the second specifies the return format, with no wasted words.
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 the tool's moderate complexity (4 parameters, no output schema), the description is mostly complete. It covers the core functionality and output, but lacks details on error handling or performance considerations. With annotations providing safety context, it's sufficient but could be enhanced with more behavioral insights.
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 100%, so the schema fully documents all parameters. The description adds no additional parameter semantics beyond what's in the schema, such as explaining the 'query' parameter's format or 'time_range' values. Baseline 3 is appropriate when the schema handles parameter documentation.
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 specific action ('Performs a web search'), resource ('using the public SearXNG search servers'), and output format ('Returns an array of result objects with 'url' and 'summary' for each result'). It distinguishes this as a general web search tool with no siblings to differentiate from.
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 implies usage for web searches but provides no explicit guidance on when to use this tool versus alternatives (e.g., other search methods or tools). Since there are no sibling tools, this is less critical, but it lacks any context about prerequisites or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search' has a single, clearly defined purpose for performing web searches.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'search' is clear and follows a simple verb pattern.
A single tool is too few for a server named 'SearXNG MCP Server', which suggests a search engine interface. While the tool covers basic search functionality, the scope feels thin, lacking features like advanced search options, result filtering, or multi-engine support that might be expected.
The tool surface is severely incomplete for a search engine server. It only provides a basic search function, missing obvious capabilities such as setting search parameters (e.g., language, time range), handling pagination, or accessing other SearXNG features like image or news searches, which limits agent effectiveness.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for Google search results via SERP API
Serper MCP — wraps the Serper Google Search API (serper.dev)
One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pwilkin/mcp-searxng-public'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
