Skip to main content
Glama
deenesjakoruzh
jimbul

You.com MCP Server

by jimbul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

You.com MCP-Server

Dieser MCP-Server (Model Context Protocol) ermöglicht KI-Assistenten die Suche im Internet, den Abruf von Nachrichten und die Durchführung von Recherchen mithilfe der You.com-API. Feedback ist willkommen.

Merkmale

  • Websuche : Zugriff auf die Websuchfunktion von You.com

  • Intelligente Suche : KI-gestützte Antworten mit Zitationsunterstützung

  • Forschung : Umfassende, zitatgestützte Antworten auf akademische Fragen

  • Nachrichtensuche : Aktuelle Nachrichtenartikel zu jedem Thema

Related MCP server: Kagi MCP Server

Voraussetzungen

  • Node.js (v16 oder höher)

  • npm oder yarn

  • You.com API-Schlüssel (holen Sie sich einen von api.you.com )

Installation

  1. Klonen Sie dieses Repository:

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

  2. Installieren Sie Abhängigkeiten:

    npm install

  3. Erstellen Sie eine .env Datei basierend auf dem Beispiel:

    cp .env.example .env

  4. Fügen Sie Ihren You.com-API-Schlüssel zur .env Datei hinzu:

    YOU_API_KEY=your_actual_api_key_here

  5. Erstellen Sie das Projekt:

    npm run build

Lokale Ausführung (optional)

Sie können den Server zum Testen lokal ausführen:

npm start

Einrichten mit Claude

Um diesen MCP-Server mit Claude (Anthropic Assistant) zu verwenden, müssen Sie Claude für die Verwendung dieses Servers konfigurieren:

  1. Öffnen Sie die Claude-Erweiterungseinstellungen in VS Code:

    • Klicken Sie auf das Claude-Symbol in der VS Code-Seitenleiste

    • Klicken Sie auf das Einstellungssymbol (⚙️) und wählen Sie „MCP-Einstellungen“

  2. Fügen Sie dem Abschnitt mcpServers die folgende Konfiguration hinzu:

"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"
}

Wichtige Hinweise:

  • Ersetzen Sie /absolute/path/to/your/youcom-mcp/dist/index.js durch den tatsächlichen Pfad auf Ihrem System

  • Ersetzen Sie your_actual_api_key_here durch Ihren You.com API-Schlüssel

Anwendungsbeispiele

Nach der Konfiguration können Sie die MCP-Tools direkt in Ihren Gesprächen mit Claude verwenden:

Websuche

<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>

Intelligente Suche

<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>

Forschung

<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>

Nachrichtensuche

<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>

Beitragen

Beiträge sind willkommen! Senden Sie gerne einen Pull Request.

Ausführen von Evaluierungen

Das Evals-Paket lädt einen MCP-Client, der anschließend die Datei index.ts ausführt, sodass zwischen den Tests kein Neuaufbau erforderlich ist. Sie können Umgebungsvariablen laden, indem Sie dem Befehl npx voranstellen. Die vollständige Dokumentation finden Sie hier .

OPENAI_API_KEY=your-key  npx mcp-eval src/evals/evals.ts src/index.ts

Lizenz

MIT

Danksagung

Dieses Projekt verwendet die You.com-API für die Suchfunktion.

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