SearxNG MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchC | Perform a web search using SearxNG and return formatted results. Results are returned in either text format (human-readable) or JSON format depending on the result_format parameter selected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'web_search' has a clearly defined and distinct purpose.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'web_search' follows a clear verb_noun pattern and is descriptive.
A single tool is too few for a server named 'SearxNG MCP Server', which suggests a broader search functionality. While web search is core, the scope feels thin without additional tools like image_search, news_search, or configuration options.
The tool surface is severely incomplete for a search server. It only covers basic web search, missing obvious functionalities such as image search, news search, or advanced search parameters that would be expected from a search engine integration.