SearchMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JSON_LOGS | No | Output logs in JSON format | false |
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | INFO |
| SEARXNG_URL | No | SearxNG server URL | http://localhost:8080 |
| SEARXNG_TIMEOUT | No | Request timeout in seconds | 10 |
| FALLBACK_ENABLED | No | Enable Google scraping fallback | true |
| RATE_LIMIT_PERIOD | No | Rate limit period in seconds | 60 |
| MAX_CONTENT_LENGTH | No | Max characters in fetched content | 10000 |
| RATE_LIMIT_REQUESTS | No | Max requests per period | 30 |
| DEFAULT_SEARCH_LIMIT | No | Default number of search results | 5 |
| SEARCH_MAX_CANDIDATES | No | Maximum candidates before reranking | 30 |
| SEARCH_GENERAL_ENGINES | No | Engines for general queries (empty = SearxNG defaults) | |
| SEARCH_SECURITY_ENGINES | No | Engines used for security/CVE queries | brave,bing,duckduckgo,wikipedia,github,stackoverflow |
| SEARCH_MIN_QUALITY_SCORE | No | Security-query quality threshold for fallback merge | 2.5 |
| SEARCH_ENGINE_PROFILE_MODE | No | Query-aware engine profile mode (auto or off) | auto |
| FETCH_ALLOW_PRIVATE_NETWORK | No | Allow fetching localhost/private network URLs | false |
| SEARCH_CANDIDATE_MULTIPLIER | No | Candidate expansion before reranking | 5 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchC | Search the web for information. Returns relevant search results with titles, URLs, and descriptions. |
| fetch_contentB | Fetch and extract readable content from a URL. Returns content as markdown. |
| get_suggestionsB | Get search query suggestions. Useful for autocomplete or query refinement. |
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: fetching content from a URL, getting search suggestions, and performing a web search. There is no overlap or ambiguity between them.
All tool names use a consistent verb_noun pattern in snake_case: fetch_content, get_suggestions, web_search. The naming is predictable and follows the same convention.
With 3 tools covering search, suggestions, and content retrieval, the set is well-scoped. It is neither too few nor too many for a search-focused server.
The tool surface covers the core search workflow: querying, getting suggestions, and fetching results. A minor gap is the absence of a tool for advanced search parameters or filtering, but it is not critical.