mcp-searxng

Created By
erhwenkuoa year ago
About 一個用來讓 AI Agent 可透過 SearXNG 服務來搜尋外部網站內容與資訊的 MCP server 。
Overview

What is mcp-searxng?

mcp-searxng is an MCP server designed for AI Agents to search for external information using the SearXNG open-source meta-search engine, allowing for a more comprehensive search experience across multiple search engines.

How to use mcp-searxng?

To use mcp-searxng, set up the SearXNG service using Docker, then run the MCP server with the appropriate configurations to connect to the SearXNG instance. You can interact with the server through the MCP Inspector to perform web searches and retrieve web content.

Key features of mcp-searxng?

  • Integrates with SearXNG for enhanced search capabilities.
  • Supports multiple search engines to provide diverse results.
  • Allows AI Agents to access external data securely and privately.

Use cases of mcp-searxng?

  1. Enabling AI Agents to gather information from various sources for research.
  2. Assisting in data retrieval for applications requiring real-time information.
  3. Providing a privacy-focused search solution for businesses.

FAQ from mcp-searxng?

  • Can mcp-searxng be used with any AI Agent?

Yes! It is designed to work with any AI Agent that can connect to the MCP server.

  • Is mcp-searxng free to use?

Yes! mcp-searxng is open-source and free to use.

  • How does mcp-searxng ensure privacy?

By using SearXNG, it allows users to search without tracking, maintaining user privacy.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
erhwenkuo
Star
1
Language
Python
License
MIT license

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)

4 hours ago
Gpt Scrambler

a day ago