@missionsquad/mcp-searxng-puppeteer
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Performs a web search using the SearXNG API, ideal for general queries, news, articles, and online content. Use this for broad information gathering, recent events, or when you need diverse web sources. |
| get_url_contentA | Get the content of a URL. Use this for further information retrieving to understand the content of each URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.