SearXNG MCP Server

Created By
hightempa year ago
A Model Context Protocol (MCP) server for integrating with SearXNG metasearch engine.
Overview

What is SearXNG MCP Server?

SearXNG MCP Server is a Model Context Protocol (MCP) server designed for integration with the SearXNG metasearch engine, allowing users to perform various types of searches.

How to use SearXNG MCP Server?

To use the SearXNG MCP Server, start the server with the command line, specifying the SearXNG instance URL and desired transport type. For example: ./go_mcp_server_searxng -searxng http://127.0.0.1:8080 -t sse -p 8892.

Key features of SearXNG MCP Server?

  • General search across multiple categories and engines.
  • Specialized image search functionality.
  • Time-filtered news search.
  • Ability to retrieve available search engines and categories.

Use cases of SearXNG MCP Server?

  1. Integrating with SearXNG for enhanced search capabilities.
  2. Performing image searches for specific queries.
  3. Accessing news articles filtered by time.

FAQ from SearXNG MCP Server?

  • What is the default port for the server?

The default port for the server is 8892.

  • Can I customize the SearXNG instance URL?

Yes, you can specify a custom SearXNG instance URL when starting the server.

  • What transport types are supported?

The server supports both stdio and sse transport types.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hightemp
Star
0
Language
Go
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

3 hours ago