Skip to main content
Glama
deenesjakoruzh
jimbul

You.com MCP Server

by jimbul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Servidor MCP de You.com

Este servidor MCP (Protocolo de Contexto de Modelo) permite a los asistentes de IA buscar en la web, obtener noticias y realizar investigaciones mediante la API de You.com. Agradecemos sus comentarios.

Características

  • Búsqueda web : acceso a la funcionalidad de búsqueda web de You.com

  • Búsqueda inteligente : respuestas basadas en IA con soporte para citas

  • Investigación : Respuestas completas y basadas en citas para consultas académicas

  • Búsqueda de noticias : Últimos artículos de noticias sobre cualquier tema

Related MCP server: Kagi MCP Server

Prerrequisitos

  • Node.js (v16 o superior)

  • npm o hilo

  • Clave API de You.com (obtén una en api.you.com )

Instalación

  1. Clonar este repositorio:

    git clone https://github.com/jimbul/youcom-mcp.git
cd youcom-mcp

  2. Instalar dependencias:

    npm install

  3. Cree un archivo .env basado en el ejemplo:

    cp .env.example .env

  4. Añade tu clave API de You.com al archivo .env :

    YOU_API_KEY=your_actual_api_key_here

  5. Construir el proyecto:

    npm run build

Ejecución local (opcional)

Puede ejecutar el servidor localmente para realizar pruebas:

npm start

Configurando con Claude

Para utilizar este servidor MCP con Claude (Anthropic Assistant), debe configurar Claude para usar este servidor:

  1. Abra la configuración de la extensión Claude en VS Code:

    • Haga clic en el ícono de Claude en la barra lateral de VS Code

    • Haga clic en el icono de configuración (⚙️) y seleccione "Configuración de MCP"

  2. Agregue la siguiente configuración a la sección mcpServers :

"youcom-mcp": {
  "autoApprove": [],
  "disabled": false,
  "command": "node",
  "args": [
    "/absolute/path/to/your/youcom-mcp/dist/index.js"
  ],
  "env": {
    "YOU_API_KEY": "your_actual_api_key_here"
  },
  "transportType": "stdio"
}

Notas importantes:

  • Reemplace /absolute/path/to/your/youcom-mcp/dist/index.js con la ruta real en su sistema

  • Reemplace your_actual_api_key_here con su clave API de You.com

Ejemplos de uso

Una vez configurado, podrás utilizar las herramientas MCP directamente en tus conversaciones con Claude:

Búsqueda web

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>web_search</tool_name>
<arguments>
{
  "query": "latest research on renewable energy"
}
</arguments>
</use_mcp_tool>

Búsqueda inteligente

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>smart_search</tool_name>
<arguments>
{
  "query": "how do quantum computers work",
  "instructions": "explain in simple terms"
}
</arguments>
</use_mcp_tool>

Investigación

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>research</tool_name>
<arguments>
{
  "query": "effects of climate change on ocean ecosystems",
  "instructions": "focus on coral reefs"
}
</arguments>
</use_mcp_tool>

Búsqueda de noticias

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>news_search</tool_name>
<arguments>
{
  "query": "latest developments in AI"
}
</arguments>
</use_mcp_tool>

Contribuyendo

¡Agradecemos sus contribuciones! No dude en enviar una solicitud de incorporación de cambios.

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Expresiones de gratitud

Este proyecto utiliza la API de You.com para la funcionalidad de búsqueda.

Available Tools

4 tools
researchD
ParametersJSON Schema
NameRequiredDescriptionDefault
instructionsNoCustom instructions for tailoring the response (optional)
queryYesThe research query to send to You.com's Research API

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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. 4 tool updatesv1.0.0
    • First observednews_search
    • First observedresearch
    • First observedsmart_search
    • First observedweb_search
Deploy Server
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

TDQS

D1.4/5.0

Scored across 4 tools

Disambiguation1/5

The tools are highly ambiguous with overlapping purposes, as all four tools appear to perform search-related functions without clear distinctions. Without descriptions, it's impossible to differentiate between 'news_search', 'research', 'smart_search', and 'web_search', making them effectively indistinguishable for an agent.

Naming Consistency3/5

The naming shows mixed conventions: 'news_search' and 'web_search' follow a consistent noun_verb pattern, but 'research' and 'smart_search' deviate with different structures. While readable, the inconsistency in verb usage and pattern reduces predictability across the set.

Tool Count3/5

With 4 tools, the count is borderline for a search-focused server, as it feels thin but not unreasonable. However, the lack of descriptions makes it hard to assess if this number adequately covers the domain, suggesting potential under-scoping or redundancy.

Completeness2/5

Inferred as a search server, there are significant gaps in coverage, such as missing filtering, sorting, or result management tools. The surface is severely incomplete for a robust search domain, likely causing agent failures due to limited operational capabilities.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

  • Kagi MCP Server by kagisearch

    Kagi MCP Serverofficial

    kagisearch
    A
    license
    A
    quality
    D
    maintenance
    An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
    2
    533
    MIT

  • Perplexity MCP Server

    RossH121
    A
    license
    A
    quality
    D
    maintenance
    An MCP server that enables Claude to perform web searches using Perplexity's API with intelligent model selection based on query intent and support for domain and recency filtering.
    6
    4
    MIT

Appeared in Searches