SearXNG

Created By
8 months ago
A network search server based on MCP technology, providing privacy-friendly web search functionality using the SearXNG search engine.
Overview

what is SearXNG?

SearXNG is a network search server based on MCP technology that provides privacy-friendly web search functionality using the SearXNG search engine.

how to use SearXNG?

To use SearXNG, configure it as an MCP service by adding the appropriate command to your MCP configuration file, and then perform web searches using the provided tools.

key features of SearXNG?

  • Web search via multiple search engines
  • Supports various search categories (general, images, news, etc.)
  • Customizable search engine selection
  • Language filtering
  • Time range filtering
  • Control over the number of search results

use cases of SearXNG?

  1. Conducting private web searches without tracking.
  2. Searching for images or news articles across multiple platforms.
  3. Customizing search results based on user preferences.

FAQ from SearXNG?

  • Is SearXNG free to use?

Yes! SearXNG is open-source and free to use.

  • Can I customize the search engines used?

Yes! You can select which search engines to use in your queries.

  • How does SearXNG ensure privacy?

SearXNG does not track users and provides a privacy-friendly search experience.

Server Config

{
  "mcpServers": {
    "searxng": {
      "command": "uvx",
      "args": [
        "searxng",
        "--instance-url=https://searx.party"
      ]
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
-
Star
-
Language
-
License
-
Category
search

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago