Skip to main content
Glama
deenesjakoruzh
PXSR

MCP Smart Searcher

by PXSR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MCP Smart Searcher

Un servidor MCP (Model Context Protocol) inteligente para búsqueda web multi-motor con resultados potenciados por IA.

Características

  • Búsqueda multi-motor — Busca en 6 motores simultáneamente: DuckDuckGo, Baidu, Juejin, GitHub, GitHub Code, Tavily

  • Extracción de contenido web — Obtén y extrae texto limpio de cualquier URL pública, con eliminación de ruido y filtrado guiado por prompts

  • Limitación de tasa — Control de concurrencia integrado mediante semáforo

  • Soporte de proxy — Configuración de proxy por motor

  • Lista de permitidos de motores — Restringe qué motores se pueden utilizar

Related MCP server: evo-scry

Instalación

pip install -e ".[dev]"

Uso

Ejecutar el servidor

python -m mcp_smart_searcher

Configuración del cliente MCP

Añádelo a la configuración de tu cliente MCP (por ejemplo, Claude Desktop):

{
  "mcpServers": {
    "smart-searcher": {
      "command": "python",
      "args": ["-m", "mcp_smart_searcher"]
    }
  }
}

Desarrollo

# Run with MCP inspector
mcp dev src/mcp_smart_searcher/server.py

# Run tests
PYTHONPATH=src pytest

# Build
python -m build

Configuración

Variable de entorno

Descripción

Predeterminado

DEFAULT_SEARCH_ENGINE

Motor de búsqueda predeterminado

duckduckgo

ALLOWED_SEARCH_ENGINES

Lista de permitidos de motores separada por comas

(todos permitidos)

TAVILY_API_KEY

Clave de API de Tavily AI Search

(ninguna)

GITHUB_TOKEN

Token de API de GitHub

(ninguno)

USE_PROXY

Habilitar proxy

true

PROXY_URL

URL del proxy

http://127.0.0.1:7890

PROXY_ENGINES

Motores que usan proxy separados por comas

(todos)

MAX_CONCURRENT_SEARCH

Máximo de solicitudes de búsqueda concurrentes

5

LOG_LEVEL

Nivel de registro

INFO

Licencia

Apache-2.0

Available Tools

2 tools
fetch_web_contentA

Fetch and extract text content from any public URL.

Args: url: Public HTTP/HTTPS URL to fetch prompt: Optional hint for what to extract. When provided, the content is filtered to prioritize paragraphs most relevant to the prompt keywords. Useful for AI agents to focus on specific content (e.g., "extract code examples only", "summarize the main argument"). max_chars: Maximum characters to return (default 30000)

Returns: Extracted text content from the webpage, optionally filtered by prompt

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
promptNo
max_charsNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must cover behavioral traits. It mentions 'any public URL' and optional filtering, but omits details on error handling, redirects, authentication, or rate limits. The transparency is basic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with a clear header, Args list, and Returns section. It is not overly long, though the prompt examples could be slightly trimmed. Overall, it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the basic inputs and output, but lacks details on error scenarios, maximum allowable characters, or non-HTTP content handling. With no annotations, more context would be beneficial for complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, requiring the description to add meaning. It does so by describing the URL as 'public HTTP/HTTPS URL,' the prompt as an optional filter with examples, and max_chars with its default. This adds significant value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Fetch and extract text content from any public URL,' providing a specific verb and resource. It distinguishes from the sibling 'web_search' by focusing on fetching a known URL rather than searching for URLs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the prompt parameter and default max_chars, implying usage for targeted extraction. However, it does not explicitly contrast with the sibling 'web_search' or state when not to use this tool, leaving room for ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.2.1
    • First observedfetch_web_content
    • First observedweb_search
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one fetches content from a specific URL, the other performs web searches. There is no overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern (fetch_web_content, web_search) using snake_case, making them predictable and easy to understand.

Tool Count3/5

With only 2 tools, the server is minimal but covers the basic search-and-fetch workflow. It feels slightly thin for a server named 'Smart Searcher' as it lacks additional features like content summarization or multi-URL fetch.

Completeness3/5

The surface covers the core operations of searching and fetching web content, but there are notable gaps such as no tool to fetch search results directly or to handle multiple URLs. Agents may need to combine calls manually.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • crawl-mcp

    gqy20
    A
    license
    A
    quality
    C
    maintenance
    MCP server for web crawling, searching, and AI-powered content extraction, supporting single-page, batch, and full-site crawling along with text, news, image, book, and video search.
    8
    1
    MIT

  • evo-scry

    krich11
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for internet search via direct Google and DuckDuckGo HTML scraping with AI-powered result normalization and optional summarization, requiring no API keys for search.
    MIT

  • MCP Search Server

    ZhenMoon
    A
    license
    Not graded
    quality
    A
    maintenance
    Multi-engine aggregated search MCP server that combines results from 7 search engines with deduplication, relevance ranking, and web page content extraction.
    1
    MIT