MCP SearxNG Search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_BASE_URL | Yes | The base URL of your SearxNG instance |
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 |
|---|---|
| searxng_searchA | |
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 'searxng_search' has a clear, distinct purpose for web searching.
The single tool name 'searxng_search' follows a consistent pattern (noun_verb style), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and descriptive.
A single tool for a search server is too minimal for effective agent use. While it covers the core search function, it lacks supporting tools (e.g., for filtering, advanced queries, or handling different search types), making the scope feel thin and incomplete for a typical search domain.
The tool surface is severely incomplete for a search server. It only provides basic search functionality without any tools for related operations like image search, news search, autocomplete, or result management, leading to significant gaps that will limit agent capabilities.