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