Web search, content extraction, PDF parsing, plus datetime and geolocation tools. No API keys.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"search-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server providing 27 tools for web search, content extraction, and data processing. No API keys required.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in maps / search
Web and local search using Brave Search API
Production ready MCP server with real-time search, extract, map & crawl.
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
MCP server for Firecrawl — search, scrape, and interact with the web. Supports both cloud and self-hosted instances. Features include web search, scraping, page interaction, batch processing, and LLM-powered content analysis.
MCP Security Weekly
Get CVE alerts and security updates for Search MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server providing 27 tools for web search, content extraction, and data processing. No API keys required.
Built with a modular registry architecture for dynamic tool loading, categorization, and discovery.
pip install mcp-search-server
git clone https://github.com/KazKozDev/mcp-search-server.git
cd mcp-search-server
pip install -e .
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"search": {
"command": "mcp-search-server"
}
}
}
Why LLMs need this: With 27 tools available, finding the right one for a task is challenging. This meta-tool enables LLMs to search through available tools by keywords, categories, or use cases.
What it does: Searches the tool registry by name, description, category, or tags. Returns ranked results with relevance scores.
Parameters:
query (required): Search query (e.g., "find web pages", "date time", "github")limit: Max results (default: 5)Example:
{"query": "search academic papers", "limit": 3}
Why LLMs need this: Tools are organized into categories (web, knowledge, social, etc.). This tool helps discover what categories exist and how many tools are in each.
What it does: Returns all available tool categories with counts.
Example:
{}
Why LLMs need this: Before using a tool, LLMs need to understand its parameters, return format, and usage examples. This tool provides complete documentation for any registered tool.
What it does: Returns detailed metadata for a specific tool including description, parameters, category, priority, and usage info.
Parameters:
tool_name (required): Name of the toolExample:
{"tool_name": "search_arxiv"}
Why LLMs need this: LLMs have a knowledge cutoff date and cannot access current information. This tool gives them real-time access to the web, enabling answers about recent events, current prices, latest news, and up-to-date documentation.
What it does: Searches the web using DuckDuckGo with support for web and news modes, time filtering, and region-specific results.
Parameters:
query (required): Search querylimit: Max results (default: 10)mode: "web" or "news"timelimit: "d" (day), "w" (week), "m" (month), "y" (year)Example:
{"query": "Python async programming", "limit": 5, "mode": "news", "timelimit": "w"}
Why LLMs need this: LLMs cannot look up real addr