mcp-searxng-public

Created By
pwilkina year ago
An MCP server that queries public SearXNG instances, parsing HTML contents into a JSON result
Overview

what is mcp-searxng-public?

mcp-searxng-public is an MCP server designed to query public SearXNG instances, parsing HTML content into a JSON format for easier data handling.

how to use mcp-searxng-public?

To use mcp-searxng-public, install it via npm install mcp-searxng-public and configure the server with the desired SearXNG instances. The server exposes a search endpoint that accepts a query and an optional time_range parameter.

key features of mcp-searxng-public?

  • Queries multiple public SearXNG instances for search results.
  • Parses HTML content into a structured JSON format.
  • Supports fallback mechanisms for enhanced reliability.

use cases of mcp-searxng-public?

  1. Aggregating search results from various SearXNG instances.
  2. Building privacy-respecting search applications.
  3. Enhancing data retrieval processes for research purposes.

FAQ from mcp-searxng-public?

  • What is SearXNG?

SearXNG is a privacy-respecting metasearch engine that aggregates results from multiple search services.

  • How does mcp-searxng-public handle errors?

It uses fallback servers to ensure that search queries are processed even if one or more instances fail.

  • Is mcp-searxng-public free to use?

Yes! It is open-source and available for anyone to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pwilkin
Star
3
Language
JavaScript
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