Search Stock News MCP Server
🔌 ¡ Compatible con Cline, Cursor, Claude Desktop y cualquier otro cliente MCP!
Buscar noticias de acciones MCP funciona a la perfección con cualquier cliente MCP
El Protocolo de Contexto de Modelo (MCP) es un estándar abierto que permite que los sistemas de IA interactúen sin problemas con diversas fuentes de datos y herramientas, lo que facilita conexiones bidireccionales seguras.
El servidor de búsqueda de noticias bursátiles MCP proporciona:
Capacidades de búsqueda de noticias bursátiles en tiempo real a través de la API de Tavily
Varias plantillas de consultas de búsqueda personalizables
Parámetros de búsqueda y filtrado configurables
Filtrado de contenido específico del dominio
Operaciones de tipos seguros con TypeScript
Prerrequisitos 🔧
Antes de comenzar, asegúrese de tener:
Clave API de Tavily
Claude Desktop, Cursor o cualquier cliente compatible con MCP
Node.js (v16 o superior)
Git instalado (solo es necesario si se utiliza el método de instalación Git)
Related MCP server: Tavily News Search MCP Server
Buscar Noticias de Stock Instalación del Servidor MCP ⚡
Corriendo con NPX
npx -y search-stock-news-mcp@latestInstalación mediante herrería
Para instalar Search Stock News MCP Server para Claude Desktop automáticamente a través de Smithery:
npx -y @smithery/cli install search-stock-news-mcp --client claudeConfiguración de clientes MCP ⚙️
Configurando Cline 🤖
La forma más sencilla de configurar el servidor Search Stock News MCP en Cline es a través del mercado:
Abrir Cline en VS Code
Haga clic en el icono de Cline en la barra lateral
Vaya a la pestaña "Servidores MCP"
Busque "Buscar noticias bursátiles" y haga clic en "Instalar".
Cuando se le solicite, ingrese su clave API de Tavily
Alternativamente, configure manualmente el servidor en Cline:
Abra el archivo de configuración de Cline MCP:
# For macOS:
code ~/Library/Application\ Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
# For Windows:
code %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.jsonAgregue la configuración del servidor de búsqueda de noticias bursátiles:
{
"mcpServers": {
"search-stock-news-mcp": {
"command": "npx",
"args": ["-y", "search-stock-news-mcp@latest"],
"env": {
"TAVILY_API_KEY": "your-api-key-here"
},
"disabled": false,
"autoApprove": []
}
}
}Configurando el cursor 🖥️
Para configurar el servidor de búsqueda de noticias bursátiles MCP en Cursor:
Abrir configuración del cursor
Vaya a Características > Servidores MCP
Haga clic en el botón "+ Agregar nuevo servidor MCP"
Complete la siguiente información:
Nombre : "search-stock-news-mcp"
Tipo : "comando"
Comando : GXP5
Configurando Claude Desktop 🖥️
Para macOS:
touch "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"Para Windows:
code %APPDATA%\Claude\claude_desktop_config.jsonAgregue la configuración del servidor:
{
"mcpServers": {
"search-stock-news-mcp": {
"command": "npx",
"args": ["-y", "search-stock-news-mcp@latest"],
"env": {
"TAVILY_API_KEY": "your-api-key-here"
}
}
}
}Ejemplos de uso 🎯
Búsqueda básica de noticias bursátiles :
{
"symbol": "AAPL",
"companyName": "Apple Inc.",
"maxResults": 10
}Búsqueda avanzada con filtros :
{
"symbol": "TSLA",
"companyName": "Tesla Inc.",
"maxResults": 20,
"searchDepth": "advanced",
"minScore": 0.6
}Búsqueda de dominio personalizada :
{
"symbol": "MSFT",
"companyName": "Microsoft Corporation",
"includeDomains": ["reuters.com", "bloomberg.com"]
}Solución de problemas 🛠️
Problemas comunes
Servidor no encontrado
Verificar la instalación de npm
Comprobar la sintaxis de configuración
Asegúrese de que Node.js esté instalado correctamente
Problemas con la clave API
Verifique que su clave API de Tavily sea válida
Compruebe que la clave API esté configurada correctamente en la configuración
Asegúrese de que no haya espacios ni comillas alrededor de la clave API
Problemas con los resultados de búsqueda
Compruebe que los parámetros de búsqueda estén dentro de rangos válidos
Verificar que los filtros de dominio estén formateados correctamente
Asegúrese de que el nombre y el símbolo de la empresa sean precisos
Agradecimientos ✨
Protocolo de contexto de modelo para la especificación MCP
Antrópico para Claude Desktop
Tavily para la API de búsqueda de noticias
Licencia
Instituto Tecnológico de Massachusetts (MIT)
Available Tools
2 toolsgeneral-searchC
Perform a general web search using Tavily API
| Name | Required | Description | Default |
|---|---|---|---|
| maxResults | No | Maximum number of results to return | |
| minScore | No | Minimum relevance score threshold | |
| query | Yes | Search query | |
| searchDepth | No | Search depth level |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. While 'Perform a general web search' implies a read-only operation, it doesn't address important behavioral aspects like rate limits, authentication requirements, error handling, or what constitutes a 'general' versus specialized search. The mention of Tavily API is helpful but insufficient.
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 extremely concise - a single sentence that communicates the core purpose efficiently. There's no wasted language or unnecessary elaboration, making it easy to parse quickly.
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?
For a search tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what results look like, how relevance scoring works, what the searchDepth levels mean, or provide any context about the Tavily API's capabilities or limitations.
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 description adds no parameter-specific information beyond what's already in the schema (which has 100% coverage). It doesn't explain what 'general web search' means in relation to the parameters like searchDepth levels or score thresholds. The baseline of 3 is appropriate since the schema does the heavy lifting.
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 clearly states the action ('Perform a general web search') and specifies the resource/API used ('using Tavily API'), which distinguishes it from generic search tools. However, it doesn't explicitly differentiate from its sibling 'search-stock-news', which appears to be a more specialized search tool.
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?
The description provides no guidance on when to use this tool versus alternatives. There's no mention of its sibling tool 'search-stock-news' or any other search tools, nor does it indicate appropriate contexts or exclusions for using this general web search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search-stock-newsC
Search for stock-related news using Tavily API
| Name | Required | Description | Default |
|---|---|---|---|
| companyName | Yes | Company name (e.g., Apple Inc.) | |
| maxResults | No | Maximum number of results to return | |
| minScore | No | Minimum relevance score threshold | |
| searchDepth | No | Search depth level | |
| symbol | Yes | Stock symbol (e.g., AAPL) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the Tavily API but doesn't describe key behaviors such as rate limits, authentication needs, error handling, or what the search results include (e.g., headlines, summaries, sources). For a search tool with external API dependencies, this is a significant gap.
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, efficient sentence with zero waste. It's front-loaded with the core purpose and includes the API name for context. Every word earns its place, making it highly concise and well-structured.
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 the complexity of a search tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of articles with fields), how results are ordered, or any behavioral traits like pagination or API constraints. For a tool with rich input schema but missing output and behavioral context, it should do more.
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?
Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples of how parameters interact or typical values). Baseline 3 is appropriate when the schema does the heavy lifting.
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 clearly states the verb ('Search') and resource ('stock-related news'), and specifies the API used ('Tavily API'). It distinguishes from the sibling 'general-search' by focusing on stock-related content, though it doesn't explicitly mention this differentiation. The purpose is specific and actionable.
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?
The description provides no guidance on when to use this tool versus alternatives like 'general-search', nor does it mention any prerequisites, exclusions, or contextual triggers. It simply states what the tool does without indicating appropriate scenarios or limitations.
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.
2 tool updates
v1.0.0- First observed
general-search - First observed
search-stock-news
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'general-search' is for broad web searches, while 'search-stock-news' is specifically for stock-related news. There is no overlap or ambiguity between them, making it easy for an agent to select the appropriate tool based on the query context.
Both tool names follow a consistent verb_noun pattern with hyphens: 'general-search' and 'search-stock-news'. They use the same naming convention throughout, making the set predictable and readable without any deviations or mixed styles.
With only two tools, the server feels under-scoped for a 'Search Stock News MCP Server'. While the tools cover general and stock-specific searches, the domain suggests potential for more operations like filtering, sorting, or retrieving detailed news, making the count too low for the apparent purpose.
The tool surface is significantly incomplete for a stock news server. It lacks essential operations such as filtering news by date, source, or stock ticker, retrieving trending news, or accessing detailed article content. This will likely cause agent failures when trying to perform comprehensive stock news analysis.
Maintenance
Related MCP Connectors
Real-time financial news for AI agents: search by ticker and source, with sentiment and entities.
The only News based AI MCP your agents will ever need — custom categories, global regions, and time-scoped results in one tool. We use multi-vector & sparse-hybrid search to search through thousands of articles across the world to find the exact news you're looking for.
GNews MCP — Global news search via GNews API (gnews.io)
Get access to real-time and historical news data including top headlines from global sources
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceThis MCP server performs multi-topic searches in business, news, finance, and politics using the Tavily API, providing high-quality sources and intelligent summaries.1MIT
- -licenseNot gradedqualityNot gradedmaintenanceA remote MCP server that enables searching for news articles on specific topics through the Tavily API without requiring authentication.-
- FlicenseNot gradedqualityFmaintenanceMCP server providing access to the GNews API for fetching news articles and headlines. Supports search and top headlines with advanced filtering by language, country, category, and date.1-
- AlicenseAqualityBmaintenanceProvides live stock data and market news for financial analysis via any MCP-compatible AI app.2MIT