websearch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_MODEL | Yes | Model name for chat completions | |
| VLM_MODEL | No | Model name for image description (defaults to LLM_MODEL) | |
| LLM_API_KEY | Yes | API key for the LLM endpoint | |
| LLM_TIMEOUT | No | LLM request timeout in seconds | 60 |
| SEARXNG_URL | Yes | Base URL of SearXNG instance | |
| VLM_API_KEY | No | API key for VLM endpoint (defaults to LLM_API_KEY) | |
| LLM_BASE_URL | Yes | OpenAI-compatible endpoint base URL | |
| VLM_BASE_URL | No | OpenAI-compatible endpoint for VLM (defaults to LLM_BASE_URL) | |
| FETCH_TIMEOUT | No | Per-page fetch timeout in seconds | 30 |
| MAX_IMAGE_SIZE | No | Max image size in bytes (10MB) | 10485760 |
| MAX_CONTENT_SIZE | No | Max content size in bytes (5MB) | 5242880 |
| CACHE_MAX_ENTRIES | No | Max cache entries before LRU eviction | 1000 |
| CACHE_TTL_SECONDS | No | Cache TTL in seconds (0 to disable) | 900 |
| DEFAULT_MAX_RESULTS | No | Default result count for web_search | 10 |
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 |
|---|---|
| web_searchA | Search the web using SearXNG, fetch top result pages, and synthesize with LLM. |
| webfetchB | Fetch a single URL, extract content, and process with LLM. |
| image_descriptionA | Describe an image using a vision language model. |
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 with no overlap: image_description handles visual analysis, webfetch processes single URLs, and web_search performs multi-result web searches. The boundaries are well-defined, preventing agent misselection.
Two tools follow a consistent 'web_' prefix pattern (web_search, webfetch), but image_description deviates with a different naming convention. The naming is still readable and mostly predictable, with only minor inconsistency.
Three tools is reasonable for a web search server, covering core functionalities (image analysis, URL fetching, web searches). It's slightly thin but well-scoped, with each tool earning its place without bloat.
The toolset covers key web search operations (searching, fetching, image analysis), but there are notable gaps like missing update/delete operations for saved searches or history management. Agents can work around this, but the surface is not fully comprehensive for extended workflows.