health_check
Check the health and connectivity status of the SearxNG bridge
LABSCO SUMMARY
The search runs through an instance you operate, so which engines answer is your decision rather than the tool's.
The instance address is configuration, which puts the choice of upstream engines — and whatever properties follow from it — on your side of the line. The parameters are the ones SearXNG itself exposes: categories, language, time range and safesearch, so results are narrowed at the source instead of filtered afterwards. The health check earns its place because the failure mode here is an instance that has gone away, which is worth telling apart from a query that found nothing.
What it is
A bridge to a SearXNG instance you run, with a health check on the connection to it.
What you get
- Searches against the configured instance with categories, language, time range, safesearch level, a maximum result count and a response format.
- A health check reporting whether the bridge can reach the instance.
Requirements
A running SearXNG instance you can reach, with its address in SEARXNG_INSTANCE_URL.
Setup effort
One command — npx -y @nitish-raj/searxng-mcp-bridge
USE CASES
01
Searching through an instance you run rather than a hosted engine
Categories, language, time range and safesearch are applied at the instance, so the narrowing happens before results come back.
02
Telling an unreachable instance apart from an empty result
A self-hosted dependency fails differently from a query that found nothing, and the two look identical without a check.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
search
Perform a search using the configured SearxNG instance
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected. It requires Node.js >=25.0.0 <26.
Requires
- npx on PATH
- Node.js >=25.0.0
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @nitish-raj/searxng-mcp-bridgeMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"searxng-bridge": {
"command": "npx",
"args": [
"-y",
"@nitish-raj/searxng-mcp-bridge"
],
"env": {
"SEARXNG_INSTANCE_URL": "http://localhost:8080"
}
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"searxng-bridge": {
"command": "npx",
"args": [
"-y",
"@nitish-raj/searxng-mcp-bridge"
],
"env": {
"SEARXNG_INSTANCE_URL": "http://localhost:8080"
},
"disabled": false
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"searxng-bridge": {
"command": "npx",
"args": [
"-y",
"@nitish-raj/searxng-mcp-bridge"
],
"env": {
"SEARXNG_INSTANCE_URL": "http://localhost:8080"
},
"disabled": false
}
}
}HTTP server
HTTP SERVER · TERMINAL
TRANSPORT=http PORT=3002 SEARXNG_INSTANCE_URL=http://localhost:8080 npx -y @nitish-raj/searxng-mcp-bridge
