Search Stock News MCP Server
The Search Stock News MCP Server enables real-time stock news searches through the Tavily API. With this server, you can:
Search for stock-related news using a stock symbol and company name as required inputs
Configure search parameters such as maximum results, search depth, and minimum score
Filter search results by including specific domains
Use with various MCP clients like Cline, Cursor, and Claude Desktop
Perform both basic and advanced search queries with type-safe operations
Required as a runtime environment for the Search Stock News MCP server, with version 16 or higher needed.
Used for type-safe operations within the Search Stock News MCP server.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Search Stock News MCP Serverget me the latest news for Tesla (TSLA) with financial analysis"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🔌 Compatible with Cline, Cursor, Claude Desktop, and any other MCP Clients!
Search Stock News MCP works seamlessly with any MCP client
The Model Context Protocol (MCP) is an open standard that enables AI systems to interact seamlessly with various data sources and tools, facilitating secure, two-way connections.
The Search Stock News MCP server provides:
Real-time stock news search capabilities via Tavily API
Multiple customizable search query templates
Configurable search parameters and filtering
Domain-specific content filtering
Type-safe operations with TypeScript
Prerequisites 🔧
Before you begin, ensure you have:
Tavily API Key
Claude Desktop, Cursor, or any MCP-compatible client
Node.js (v16 or higher)
Git installed (only needed if using Git installation method)
Related MCP server: Tavily News Search MCP Server
Search Stock News MCP Server Installation ⚡
Running with NPX
npx -y search-stock-news-mcp@latestInstalling via Smithery
To install Search Stock News MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install search-stock-news-mcp --client claudeConfiguring MCP Clients ⚙️
Configuring Cline 🤖
The easiest way to set up the Search Stock News MCP server in Cline is through the marketplace:
Open Cline in VS Code
Click on the Cline icon in the sidebar
Navigate to the "MCP Servers" tab
Search "Search Stock News" and click "install"
When prompted, enter your Tavily API key
Alternatively, manually configure the server in Cline:
Open the Cline MCP settings file:
# 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.jsonAdd the Search Stock News server configuration:
{
"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": []
}
}
}Configuring Cursor 🖥️
To set up the Search Stock News MCP server in Cursor:
Open Cursor Settings
Navigate to Features > MCP Servers
Click on the "+ Add New MCP Server" button
Fill out the following information:
Name: "search-stock-news-mcp"
Type: "command"
Command:
env TAVILY_API_KEY=your-api-key-here npx -y search-stock-news-mcp@latest
Configuring Claude Desktop 🖥️
For macOS:
touch "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"For Windows:
code %APPDATA%\Claude\claude_desktop_config.jsonAdd the server configuration:
{
"mcpServers": {
"search-stock-news-mcp": {
"command": "npx",
"args": ["-y", "search-stock-news-mcp@latest"],
"env": {
"TAVILY_API_KEY": "your-api-key-here"
}
}
}
}Usage Examples 🎯
Basic Stock News Search:
{
"symbol": "AAPL",
"companyName": "Apple Inc.",
"maxResults": 10
}Advanced Search with Filters:
{
"symbol": "TSLA",
"companyName": "Tesla Inc.",
"maxResults": 20,
"searchDepth": "advanced",
"minScore": 0.6
}Custom Domain Search:
{
"symbol": "MSFT",
"companyName": "Microsoft Corporation",
"includeDomains": ["reuters.com", "bloomberg.com"]
}Troubleshooting 🛠️
Common Issues
Server Not Found
Verify npm installation
Check configuration syntax
Ensure Node.js is properly installed
API Key Issues
Verify your Tavily API key is valid
Check the API key is correctly set in config
Ensure no spaces or quotes around the API key
Search Results Issues
Check search parameters are within valid ranges
Verify domain filters are correctly formatted
Ensure company name and symbol are accurate
Acknowledgments ✨
Model Context Protocol for the MCP specification
Anthropic for Claude Desktop
Tavily for the News Search API
License
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.
TDQS
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
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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)
AI-enriched financial news for AI agents & trading bots: search, trending, insider, scored 1-10.
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-
- AlicenseAqualityCmaintenanceProvides live stock data and market news for financial analysis via any MCP-compatible AI app.2MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cognitive-Stack/search-stock-news-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server