{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-mcp-searxng","slug":"npm-mcp-searxng","name":"mcp-searxng","type":"mcp","url":"https://www.npmjs.com/package/mcp-searxng","page_url":"https://unfragile.ai/npm-mcp-searxng","categories":["mcp-servers"],"tags":["mcp","modelcontextprotocol","searxng","search","web-search","claude","ai","pagination","smithery","url-reader"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-mcp-searxng__cap_0","uri":"capability://search.retrieval.web.search.via.searxng.metasearch","name":"web-search-via-searxng-metasearch","description":"Executes web searches through a SearXNG instance (self-hosted or public) using the MCP protocol, enabling Claude and other MCP clients to query multiple search engines simultaneously without direct API dependencies. Implements MCP tool registration to expose search as a callable function with query and optional pagination parameters, abstracting away HTTP communication with the SearXNG backend.","intents":["I want Claude to search the web in real-time without using OpenAI's Bing integration","I need to route search queries through my self-hosted SearXNG instance for privacy","I want to give my AI agent access to metasearch results from multiple engines at once","I need to integrate web search into an MCP-compatible application without writing custom HTTP clients"],"best_for":["developers building privacy-focused AI agents with Claude","teams running self-hosted SearXNG instances who want MCP integration","builders creating multi-tool AI applications using the Model Context Protocol","organizations avoiding direct dependencies on commercial search APIs"],"limitations":["Depends on external SearXNG instance availability — no built-in fallback if SearXNG is down","Search quality and result freshness tied to SearXNG configuration and underlying engine sources","No built-in result ranking or deduplication across multiple search engines","Pagination support may be limited by SearXNG API response structure","No caching layer — each query hits SearXNG directly, adding latency"],"requires":["Node.js 16+ (MCP SDK requirement)","Running SearXNG instance (self-hosted or public endpoint)","MCP-compatible client (Claude Desktop, custom MCP host, or compatible AI application)","Network access to SearXNG endpoint"],"input_types":["text (search query string)","optional parameters (page number for pagination, result count limit)"],"output_types":["structured JSON (search results with title, URL, snippet, source engine)","paginated result sets"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-searxng__cap_1","uri":"capability://tool.use.integration.mcp.tool.registration.for.search","name":"mcp-tool-registration-for-search","description":"Registers search functionality as an MCP tool with schema validation, parameter definitions, and callable interface that MCP clients (like Claude) can discover and invoke. Uses MCP's tool definition format to expose search with typed parameters (query string, pagination options) and structured response schemas, enabling semantic understanding of search capabilities by AI clients.","intents":["I want Claude to automatically discover that search is available and understand its parameters","I need to define search input/output schemas so Claude can validate queries before sending them","I want to expose search as a callable tool in an MCP-compatible application","I need search to appear in Claude's tool list with proper documentation"],"best_for":["MCP server developers integrating third-party capabilities","teams building multi-tool AI agents with proper capability discovery","developers who want type-safe tool invocation with schema validation"],"limitations":["Tool schema must be defined statically at server startup — no dynamic schema updates","Parameter validation happens at MCP level, not at SearXNG level — mismatches may cause runtime errors","No built-in error handling for malformed search queries or SearXNG API failures"],"requires":["MCP SDK for Node.js","Understanding of MCP tool definition format (JSON schema)","MCP-compatible client that supports tool discovery"],"input_types":["JSON schema definitions","tool parameter specifications"],"output_types":["MCP tool definitions","callable tool interface for MCP clients"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-searxng__cap_2","uri":"capability://search.retrieval.pagination.aware.search.result.retrieval","name":"pagination-aware-search-result-retrieval","description":"Handles paginated search results from SearXNG by accepting page parameters and returning result sets with metadata about total results and current page position. Implements offset-based or cursor-based pagination depending on SearXNG API capabilities, allowing clients to retrieve large result sets incrementally without loading all results into memory at once.","intents":["I want to retrieve the next page of search results without re-querying","I need to know how many total results are available for a search query","I want to iterate through search results in batches to avoid memory overhead","I need to implement search result browsing in my AI agent"],"best_for":["applications handling high-volume search queries with large result sets","AI agents that need to explore multiple result pages for comprehensive research","builders implementing search result browsing UIs"],"limitations":["Pagination implementation depends on SearXNG version and configuration — may not be consistent across instances","No built-in result caching between page requests — each page fetch hits SearXNG","Page size and maximum page depth may be limited by SearXNG configuration","Cursor-based pagination not guaranteed if SearXNG uses offset-based approach"],"requires":["SearXNG instance with pagination support enabled","MCP client capable of passing pagination parameters"],"input_types":["search query string","page number or offset","optional result count per page"],"output_types":["paginated result set with metadata","total result count","current page indicator"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-searxng__cap_3","uri":"capability://search.retrieval.multi.engine.metasearch.aggregation","name":"multi-engine-metasearch-aggregation","description":"Leverages SearXNG's ability to query multiple search engines (Google, Bing, DuckDuckGo, etc.) simultaneously and returns aggregated results through a single MCP interface. SearXNG handles engine selection, result deduplication, and ranking internally; this capability exposes that aggregation to MCP clients without requiring separate API calls to individual engines.","intents":["I want search results from multiple engines without managing multiple API keys","I need to compare results across different search engines programmatically","I want to avoid search engine bias by querying multiple sources at once","I need comprehensive search coverage without direct dependencies on Google/Bing APIs"],"best_for":["research-focused AI agents that need comprehensive result coverage","privacy-conscious teams avoiding single-engine dependency","applications requiring search engine diversity for bias mitigation"],"limitations":["Result quality varies by engine — SearXNG aggregation may not optimize for relevance","No control over which engines are queried — determined by SearXNG configuration","Deduplication logic is SearXNG-specific and may miss near-duplicate results","Latency increases with number of engines queried — slower than single-engine search"],"requires":["SearXNG instance with multiple search engines enabled","Network connectivity to all configured search engines"],"input_types":["search query string","optional engine selection filter (if SearXNG supports it)"],"output_types":["aggregated results from multiple engines","engine source attribution per result"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-searxng__cap_4","uri":"capability://tool.use.integration.self.hosted.search.endpoint.configuration","name":"self-hosted-search-endpoint-configuration","description":"Allows configuration of a custom SearXNG endpoint (self-hosted or public instance) at MCP server initialization, enabling organizations to route all search queries through their own infrastructure. Configuration is typically passed via environment variables or config files, and the MCP server maintains a persistent connection to the configured endpoint for all subsequent search requests.","intents":["I want to run search through my organization's self-hosted SearXNG instance","I need to ensure all search queries stay within my network for compliance","I want to customize SearXNG engine configuration for my use case","I need to point my MCP server at a specific SearXNG endpoint without code changes"],"best_for":["enterprises with data residency or privacy requirements","teams running self-hosted SearXNG for cost control","organizations wanting to customize search engine selection"],"limitations":["Endpoint configuration is static — requires server restart to change endpoints","No built-in endpoint health checking or failover to backup instances","Self-hosted SearXNG requires separate infrastructure management and maintenance","Configuration errors at startup may not be caught until first search attempt"],"requires":["Running SearXNG instance (self-hosted or public endpoint URL)","Environment variable or config file support in MCP server","Network access from MCP server to SearXNG endpoint"],"input_types":["SearXNG endpoint URL (environment variable or config parameter)","optional authentication credentials if SearXNG requires them"],"output_types":["validated endpoint connection","search requests routed to configured endpoint"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-searxng__cap_5","uri":"capability://tool.use.integration.mcp.protocol.server.implementation","name":"mcp-protocol-server-implementation","description":"Implements the Model Context Protocol (MCP) server specification in Node.js, handling MCP message serialization/deserialization, tool registration, request routing, and response formatting. Uses MCP SDK to manage the server lifecycle, client connections, and protocol compliance, abstracting away low-level MCP communication details from the search integration logic.","intents":["I want to expose SearXNG search as an MCP tool to Claude and other MCP clients","I need a standards-compliant MCP server without building protocol handling from scratch","I want my search integration to work with any MCP-compatible client","I need proper error handling and response formatting for MCP clients"],"best_for":["developers building MCP servers for AI integrations","teams standardizing on MCP for tool integration","builders who want to avoid custom protocol implementation"],"limitations":["MCP protocol overhead adds latency compared to direct HTTP calls","Server must maintain MCP connection state — not suitable for serverless deployments","Error handling is MCP-specific — may not map cleanly to SearXNG errors","MCP client compatibility depends on client implementation — not all clients support all MCP features"],"requires":["Node.js 16+","MCP SDK (@modelcontextprotocol/sdk)","MCP-compatible client (Claude Desktop, custom host, etc.)"],"input_types":["MCP protocol messages (JSON-RPC format)","tool invocation requests from MCP clients"],"output_types":["MCP protocol responses","tool results formatted for MCP clients"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-searxng__cap_6","uri":"capability://tool.use.integration.claude.desktop.integration.via.mcp","name":"claude-desktop-integration-via-mcp","description":"Registers the MCP server with Claude Desktop through MCP's client discovery mechanism, making search available as a native tool within Claude's interface. Claude Desktop automatically discovers the MCP server, loads tool definitions, and enables users to invoke search directly in conversations without manual tool binding or configuration.","intents":["I want to use SearXNG search directly in Claude Desktop conversations","I need Claude to automatically discover my search tool without manual setup","I want to give Claude real-time web search capability through my self-hosted SearXNG","I need search to appear in Claude's tool list alongside other capabilities"],"best_for":["Claude Desktop users wanting self-hosted search integration","teams deploying MCP servers for Claude integration","developers building privacy-focused Claude workflows"],"limitations":["Requires Claude Desktop 0.2.0+ with MCP support — not available in web version","MCP server must be running locally or accessible from Claude Desktop's environment","Tool discovery happens at Claude startup — changes require restart","No built-in rate limiting or quota management at Claude level"],"requires":["Claude Desktop 0.2.0 or later with MCP support","MCP server running and accessible to Claude Desktop","MCP server configuration in Claude's config file (typically ~/.claude/config.json)"],"input_types":["natural language search queries from Claude conversations"],"output_types":["search results displayed in Claude conversation","formatted result summaries for Claude to process"],"categories":["tool-use-integration","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":27,"verified":false,"data_access_risk":"moderate","permissions":["Node.js 16+ (MCP SDK requirement)","Running SearXNG instance (self-hosted or public endpoint)","MCP-compatible client (Claude Desktop, custom MCP host, or compatible AI application)","Network access to SearXNG endpoint","MCP SDK for Node.js","Understanding of MCP tool definition format (JSON schema)","MCP-compatible client that supports tool discovery","SearXNG instance with pagination support enabled","MCP client capable of passing pagination parameters","SearXNG instance with multiple search engines enabled"],"failure_modes":["Depends on external SearXNG instance availability — no built-in fallback if SearXNG is down","Search quality and result freshness tied to SearXNG configuration and underlying engine sources","No built-in result ranking or deduplication across multiple search engines","Pagination support may be limited by SearXNG API response structure","No caching layer — each query hits SearXNG directly, adding latency","Tool schema must be defined statically at server startup — no dynamic schema updates","Parameter validation happens at MCP level, not at SearXNG level — mismatches may cause runtime errors","No built-in error handling for malformed search queries or SearXNG API failures","Pagination implementation depends on SearXNG version and configuration — may not be consistent across instances","No built-in result caching between page requests — each page fetch hits SearXNG","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.24,"ecosystem":0.5000000000000001,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:38.317Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-mcp-searxng","compare_url":"https://unfragile.ai/compare?artifact=npm-mcp-searxng"}},"signature":"5ekKDYmuqIOWegoTfjg6Um5a8IVH+0iOq4CR0HmFNhus4yAdOr4EyuZnGr89zqmIXZ2BCT1dh/+2CRQV4A3XDA==","signedAt":"2026-06-21T20:15:09.163Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-mcp-searxng","artifact":"https://unfragile.ai/npm-mcp-searxng","verify":"https://unfragile.ai/api/v1/verify?slug=npm-mcp-searxng","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}