@missionsquad/mcp-searxng-puppeteer
OfficialRelated Servers
Alternatives to @missionsquad/mcp-searxng-puppeteer
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server implementation that integrates the SearxNG API, providing web search capabilities.212,610 npm1,261MIT
- AlicenseBqualityDmaintenanceAn MCP server that integrates with the SearXNG API to provide comprehensive web search capabilities with features like time filtering, language selection, and safe search. It also enables users to fetch and convert web content from specific URLs into markdown format.216 npm4MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server that integrates the SearXNG API to provide web search with pagination, filtering, and URL content extraction.9 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that integrates the SearXNG API for web search and URL content extraction with advanced features like pagination, caching, and proxy support.412,610 npm2MIT
- AlicenseAqualityBmaintenanceMCP server that exposes SearXNG search and HTTP fetch tools for AI agents, enabling web search and clean page text extraction via natural language.4MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides web search scraping from DuckDuckGo (with Mojeek fallback) and URL content fetching as markdown/text or raw HTML.1-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'get_url_content' retrieves content from a specific URL, while 'web_search' performs broad searches across the web. There is no overlap or ambiguity between them, making it easy for an agent to select the appropriate tool based on the task.
Both tool names follow a consistent verb_noun pattern ('get_url_content' and 'web_search'), using snake_case throughout. This predictability aids in understanding and usage without any deviations or mixed conventions.
With only 2 tools, the server feels thin for its apparent scope of web search and content retrieval. While the tools cover basic operations, the count is too low for a comprehensive web interaction toolset, lacking features like advanced search filters, content analysis, or URL management.
The tool surface is severely incomplete for a web search and content retrieval domain. It provides search and URL fetching but lacks essential operations such as filtering search results, handling pagination, analyzing content (e.g., summarization), or managing search history, which are common in similar toolsets.