mcp_server_searXNG

The materials explicitly state that no keys or environment variables are required, and there is no indication that API tokens, account passwords, or other sensitive credentials are needed, so credential exposure appears limited.

Its core function is web search, so by design it will access a SearXNG/search service over the network; although no fixed remote endpoint is provided, user queries will likely be sent to the configured search instance, creating a normal data-egress surface.

The system flags it as executing code, indicating that the MCP tool runs a local service process or related logic; this is a normal capability for such tools, and the provided materials do not show requests for unusual system privileges beyond the search use case.

The materials do not declare access to specific local files, databases, or sensitive system resources, but as a locally running MCP service it will at least process user input and runtime configuration. The current information is insufficient to show overbroad read/write access, but also insufficient to fully rule out local data exposure.

It has a public GitHub repository and an MIT license, which are positive for auditability; however, it comes from a third-party registry, has 0 stars, unknown maintenance status, and no README, so supply-chain confidence is only moderate and the source and dependencies should be reviewed before installation.