searxng-http-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | API key for authentication (optional). When set, all requests require x-api-key header or HTTP Basic Auth. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the web using SearXNG metasearch engine. Aggregates results from 200+ search engines (Google, Bing, DuckDuckGo, Brave, etc.) with privacy. Returns results, answers, suggestions, corrections, and infoboxes. Use 'categories' to focus on specific content types. Use 'pages' for more results. Not suitable for autocomplete suggestions (use autocomplete tool) or discovering available engines/categories (use engine_info tool). Results are cached for 60 seconds. |
| autocompleteA | Get search query suggestions from SearXNG. Returns a list of autocomplete suggestions for the given partial query. Use this to discover relevant search terms before performing a full search. Best results come from 1-2 meaningful keywords (e.g., "python async"). Single characters return overly broad suggestions; full sentences return none. Makes an external API call to the configured autocomplete backend (e.g., Bing, Google). Not suitable for full web search (use search tool) or engine discovery (use engine_info tool). |
| engine_infoA | Get available search engines and categories from the SearXNG instance. Returns the list of enabled engines grouped by category. Use this to discover what engines and categories are available before calling search with specific engines or categories filters. Response is cached for 5 minutes. Does not perform any web search — use the search tool for that. |
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 3 tools
Each tool has a clearly distinct purpose: search performs web searches, autocomplete provides query suggestions, and engine_info lists available engines/categories. The descriptions explicitly state which tool to use for which task, eliminating any ambiguity.
All tool names are lowercase and use underscores for compound names (engine_info), maintaining a consistent and predictable naming style. Though not following a strict verb_noun pattern, the convention is uniform and easy to learn.
Three tools is a well-scoped count for this server's purpose. Each tool serves a distinct and necessary function for a search metasearch service, and none feel redundant or missing.
The tool set covers the essential search lifecycle: performing searches, getting autocomplete suggestions, and discovering engine/category options. No obvious gaps exist for the stated purpose of providing a SearXNG interface.