DeepSeek Web版に基づいたオンライン検索MCPサーバーです。DeepSeekの検索拡張対話機能を通じて、MCPクライアントにリアルタイムのWeb検索能力を提供します。
web_search MCPツールを提供し、リアルタイムWeb検索をサポート
DeepSeekのデフォルトモデルおよびエキスパートモデルをサポート
思考プロセス（thinking）の出力をサポート
ゼロ依存、純粋なNode.js実装
stdio転送、すべてのMCPクライアントと互換性あり
Related MCP server: google-search-mcp
Claude Desktopの設定ファイル（claude_desktop_config.json）を編集し、envフィールドを通じて直接認証情報を渡します（.envファイルは不要です）：
{
"mcpServers": {
"web-search": {
"command": "node",
"args": ["D:/ai-projects/web-search-mcp/src/index.js"],
"env": {
"DEEPSEEK_AUTH_TOKEN": "your_token_here"
}
}
}
}プロジェクトの .claude/settings.json に以下を追加します：
{
"mcpServers": {
"web-search": {
"command": "node",
"args": ["D:/ai-projects/web-search-mcp/src/index.js"],
"env": {
"DEEPSEEK_AUTH_TOKEN": "your_token_here"
}
}
}
}MCP設定に env を記述するのが不便な場合は、.env ファイルも使用できます：
cp .env.example .env
# 编辑 .env 填入凭据環境変数の優先順位：システム環境変数 > MCP
env設定 >.envファイル
web_searchDeepSeekの検索拡張対話を使用してWeb検索を行い、検索結果に基づいた回答を返します。
パラメータ：
パラメータ | 型 | 必須 | 説明 |
| string | はい | 検索クエリの内容 |
| boolean | いいえ | DeepSeekの思考/推論モードを有効にするかどうか。有効にするとモデルは推論してから回答し、推論プロセスがレスポンスに含まれます（デフォルトは false） |
| string | いいえ | モデルモード： |
変数 | 必須 | デフォルト値 | 説明 |
| 二者択一 | - | DeepSeekログイン用トークン |
| 二者択一 | - | DeepSeekブラウザ用Cookie |
| いいえ |
| モデルタイプ： |
| いいえ |
| 思考プロセスをデフォルトで有効にするかどうか |
| いいえ |
| PoWソルバーWASMファイルのパス |
| いいえ |
| ログレベル： |
chat.deepseek.com を開き、ログインします
ブラウザの開発者ツール（F12）を開き、Console（コンソール） パネルに切り替えます
以下のコマンドを入力してEnterキーを押すと、トークンがコピーされます：
copy(JSON.parse(localStorage.getItem("userToken")).value)DEEPSEEK_AUTH_TOKEN 環境変数に貼り付けます
注意：認証情報は期限切れになります。期限切れになった場合は再取得が必要です。トークン期限切れの典型的な兆候は、リクエストがCloudflareの検証ページを返すことです。
# 运行所有测试
npm test
# 运行单个测试文件
node --test tests/mcp-protocol.test.js
node --test tests/config.test.jssrc/
index.js # 入口，初始化所有组件并启动 MCP 服务器
mcp-server.js # MCP 协议处理（stdio 传输、JSON-RPC 分发）
deepseek-client.js # DeepSeek 网页版 API 客户端（会话管理、PoW、SSE 流式解析）
pow-solver.js # SHA3 PoW WASM 求解器
env.js # .env 文件加载器
config.js # 环境变量配置解析Search the web using DeepSeek's search-enabled chat. Returns a search-grounded response with up-to-date information.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The search query | |
| thinking | No | Enable DeepSeek thinking/reasoning mode. When true, the model will reason through the query before answering, and the reasoning trace is included in the response. (default: false) | |
| model | No | DeepSeek model mode (default: from server config) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states that the tool returns a 'search-grounded response with up-to-date information', which implies read-only behavior, but it does not explicitly disclose side effects, authentication needs, or limitations. Without annotations, the description carries a heavier burden and falls short of full transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that conveys the essential function without unnecessary words. While it is concise, it could be slightly expanded to improve clarity without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there is no output schema, the description should elaborate on the return format. It mentions 'search-grounded response' but does not specify structure or content. The lack of sibling tools reduces the need for differentiation, but completeness is only moderate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for all three parameters, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides for the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Search' and clearly identifies the resource 'the web using DeepSeek's search-enabled chat', leaving no ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus any alternatives, nor are there any conditions or prerequisites mentioned. The description lacks context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0web_searchScored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
The single tool name 'web_search' is clear and follows a common verb_noun pattern, but with only one tool, consistency cannot be fully assessed.
One tool is minimal for a web search server. It covers the core action but may lack supporting tools for refined queries or result handling.
The tool provides basic web search functionality, but there are no tools for advanced filtering, pagination, or retrieving structured results, leaving potential gaps.
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
Web search, scraping, RAG answers with citations, and translation as MCP tools.
Free web search for AI agents. No API key required. Hosted MCP in active development.
Search the agentic web. 4,100+ sites, 11 tools incl. check_url + verify_mcp for probe-before-use.
