owl-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | Yes | The 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web through the operator's own SearXNG instance — no API key, no paid tier, no tracking relay. Returns title/url/snippet per result with the engines each hit came from. Requires SEARXNG_URL in the server environment. |
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 confusion or misselection. Its purpose is clearly stated as web search through a SearXNG instance.
The single tool name 'web_search' follows a clear, readable snake_case convention. There are no competing conventions to create inconsistency.
A single-tool surface is thin for a search server, even if well-scoped. It lacks separate operations for pagination, content fetching, or search options.
The core web search operation is covered, but there are minor gaps such as no pagination, no full-page fetch, and no explicit advanced search parameters in the description.