searxng-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server bind address (use 0.0.0.0 for containers) | 127.0.0.1 |
| PORT | No | HTTP server port (when TRANSPORT=http) | 3002 |
| TRANSPORT | No | Transport protocol: stdio or http | stdio |
| CORS_ORIGIN | No | Comma-separated allowed origins for CORS | localhost:3002 (dev) / * (prod) |
| MCP_HTTP_BEARER | No | Bearer token for HTTP endpoint authentication | |
| SEARXNG_BRIDGE_DEBUG | No | Enable debug logging (true to enable) | false |
| SEARXNG_INSTANCE_URL | Yes | Full URL of the SearXNG instance (e.g., http://localhost:8080) |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Perform a search using the configured SearxNG instance |
| health_checkA | Check the health and connectivity status of the SearxNG bridge |
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 2 tools
search and health_check have clearly distinct purposes: one performs searches, the other reports connectivity/health. There is no realistic overlap that would cause an agent to misselect between them.
Both names use snake_case, which is consistent. However, search is a bare verb while health_check is a verb/noun-style check name, so the pattern is mostly but not perfectly consistent.
Two tools is slightly thin in general, but the server is narrowly scoped as a SearxNG bridge. search and health_check both earn their place and cover the essential surface without bloat.
The core lifecycle for this bridge is covered: perform a search and verify health/connectivity. Minor optional gaps might include exposing advanced search parameters or instance/engine metadata, but nothing essential is missing.