A
licenseNot graded
qualityF
maintenanceA proxy MCP server for Tavily search and extract APIs with support for multiple API keys, random rotation, and bearer token authentication.
MIT
tavily-pool-mcp
tavily-pool-mcp
Tavily検索ツールを公開し、複数のTavily APIキーをローテーションするローカルModel Context Protocolサーバー。
機能
tavily_searchをMCPツールとして公開複数のTavily APIキーをローテーション
401、403、または429エラー発生時に別のキーで再試行OpenCodeおよびその他のMCP互換クライアントで動作
Related MCP server: AIE7-MCP
要件
Node.js 18以上
Tavily APIキー
インストール
npm install設定
TAVILY_API_KEYS をスペース、カンマ、またはセミコロン区切りのリストとして設定します：
export TAVILY_API_KEYS="tvly-dev-key-1 tvly-dev-key-2 tvly-dev-key-3"Windows PowerShellの場合：
$env:TAVILY_API_KEYS="tvly-dev-key-1 tvly-dev-key-2 tvly-dev-key-3"実行
npm startnpm start はstdio MCPサーバーを起動するため、ターミナルはMCP入力を待機します。これは正常な動作です。
OpenCodeの設定
OpenCodeの opencode.json に以下を追加します：
{
"mcp": {
"tavily-pool": {
"type": "local",
"enabled": true,
"command": ["node", "C:/path/to/tavily-pool-mcp/src/index.mjs"],
"environment": {
"TAVILY_API_KEYS": "{env:TAVILY_API_KEYS}"
}
}
}
}ツール
tavily_search
引数：
query: 検索クエリmax_results: 1〜20、デフォルトは5search_depth:basicまたはadvanced、デフォルトはbasicinclude_answer: ブール値、デフォルトはfalseinclude_raw_content: ブール値、デフォルトはfalse
セキュリティ
実際のAPIキーをコミットしないでください。環境変数またはシークレットマネージャーを使用してください。
ライセンス
MIT
Available Tools
1 tooltavily_searchC
Search the web using Tavily. This MCP rotates across multiple API keys.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| max_results | No | ||
| search_depth | No | basic | |
| include_answer | No | ||
| include_raw_content | No |
TDQS
C2.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description mentions a behavioral trait: 'rotates across multiple API keys', which is beyond the (missing) annotations. However, it omits other important details like rate limits, costs, or result format, which would be expected for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is succinct with two sentences. The first sentence clearly states the core purpose, and the second adds a key behavioral detail. No extraneous information is present.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 5 parameters, no output schema, and no annotations, the description is too minimal. The agent lacks information about return values, pagination, or how to interpret results, making it insufficient for effective use.
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?
The schema coverage is low (20%), with only 'query' having a description. The description adds no information about parameters such as max_results, search_depth, include_answer, or include_raw_content, leaving the agent without guidance on their meaning or usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Search' and the resource 'web using Tavily', which is a specific search engine. The purpose is unambiguous, and since there are no sibling tools, differentiation is not required.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
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 alternatives or when not to use it. The description only implies usage for web searches, but lacks exclusion criteria or context for decision-making.
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 tool update
v0.1.0- First observed
tavily_search
TDQS
B3.4/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion or overlap.
Naming Consistency5/5
The single tool follows a clear verb_noun pattern (tavily_search), which is consistent and predictable.
Tool Count3/5
One tool is on the low end but reasonable for a focused search service; it is borderline but not inappropriate.
Completeness5/5
The search tool fully covers the server's purpose of web search; no obvious missing operations.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Free web search for AI agents. No API key required. Hosted MCP in active development.
Related MCP Servers
- FlicenseAqualityDmaintenanceMCP server that provides web search capabilities using the Tavily API.3-
- AlicenseBqualityDmaintenanceMCP server providing search, extract, map, and crawl tools powered by Tavily for real-time web data access.411 npmMIT
- FlicenseNot gradedqualityCmaintenanceAn experimental MCP server that provides web search capabilities using the Tavily API. Still in progress, not production-ready.-