SearXNG MCP Server

web_search

Submit a web search query to a privacy-respecting metasearch engine that aggregates results from multiple sources.

Instructions

Perform a web search using a privacy-respecting SearXNG metasearch instance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Search query to submit to SearXNG
`categories`	No	Optional list of categories to search in (e.g. general, news, science, files, images, videos, music, it, social_media)
`engines`	No	Optional list of specific search engines to use
`language`	No	Language code for search results (e.g. en-US)	en-US
`pageno`	No	Page number of results to fetch

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.11.1May 22, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / categories / description

Previous value: -"Categories to search in (e.g., 'general', 'images', 'news'). Default: null (all categories)."New value: +"Optional list of categories to search in (e.g. general, news, science, files, images, videos, music, it, social_media)"

changedInput schema / properties / engines / description

Previous value: -"Specific search engines to use. Default: null (all available engines)."New value: +"Optional list of specific search engines to use"

changedInput schema / properties / language / default
```
Previous value: -"en"New value: +"en-US"
```

changedInput schema / properties / language / description

Previous value: -"Language code for search results (e.g., 'en', 'de', 'fr'). Default: 'en'"New value: +"Language code for search results (e.g. en-US)"

removedInput schema / properties / max_results

Removed value: -{
-  "default": 10,
-  "description": "Maximum number of search results to return. Range: 1-50. Default: 10.",
-  "maximum": 50,
-  "minimum": 1,
-  "type": "integer"
-}

changedInput schema / properties / pageno / description

Previous value: -"Page number for results. Must be minimum 1. Default: 1."New value: +"Page number of results to fetch"

removedInput schema / properties / pageno / minimum
```
Removed value: -1
```
removedInput schema / properties / query / default
```
Removed value: -null
```

changedInput schema / properties / query / description

Previous value: -"Search query"New value: +"Search query to submit to SearXNG"

removedInput schema / properties / safesearch

Removed value: -{
-  "default": 1,
-  "description": "Safe search level: 0 (off), 1 (moderate), 2 (strict). Default: 1 (moderate).",
-  "type": "integer"
-}

removedInput schema / properties / time_range

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Time range for search results. Options: 'day', 'week', 'month', 'year'. Default: null (no time restriction)."
-}

addedInput schema / required
```
Added value: +[
+  "query"
+]
```

First observedv1.0.0Oct 16, 2025

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. It only mentions 'privacy-respecting' but omits details like rate limits, authentication needs, result pagination, or caching behavior. The output schema exists but is not referenced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that conveys the essential purpose without extraneous words. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity, the schema covers all parameters, and an output schema exists, the description is largely complete. However, it could briefly mention pagination or result limits associated with the pageno parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with all 5 parameters described in the schema. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('perform a web search') and the specific resource ('privacy-respecting SearXNG metasearch instance'), making the tool's purpose unambiguous. With no sibling tools provided, differentiation is not required.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives, nor does it specify when not to use it. The mention of 'privacy-respecting' hints at a use case but does not explicitly state conditions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

web_searchB