Skip to main content
Glama
sleepysoong

Stock Price MCP Server

by sleepysoong

Stock Price MCP Server

MCP (Model Context Protocol) server that provides real-time stock price information using Yahoo Finance API.

Features

  • πŸ“ˆ Real-time stock price data

  • πŸ• Price update timestamps

  • 🏦 Market state information (PRE, REGULAR, AFTER, POST, CLOSED)

  • πŸ’± Multi-currency support

  • 🌍 Global market coverage

  • πŸ†“ Completely free with no rate limits

Related MCP server: Stock Data MCP Server

Installation

npm install
npm run build

Usage

As an MCP Server

Add to your MCP client configuration:

{
  "mcpServers": {
    "stock-price": {
      "command": "node",
      "args": ["/path/to/stock-price-mcp/dist/index.js"]
    }
  }
}

Available Tools

get_stock_price

Get real-time stock price information for a ticker symbol.

Input:

{
  "ticker": "AAPL"
}

Output:

{
  "ticker": "AAPL",
  "last_price": 150.25,
  "timestamp": "2024-01-15T16:00:00.000Z",
  "market_state": "CLOSED",
  "currency": "USD"
}

Market States

  • PRE - Pre-market trading

  • REGULAR - Regular trading hours

  • AFTER - After-hours trading

  • POST - Post-market trading

  • CLOSED - Market closed

Supported Markets

  • US Stocks: AAPL, TSLA, MSFT

  • Korean Stocks: 005930.KS (Samsung)

  • European Stocks: BMW.DE

  • And many more global exchanges

Development

npm run dev

License

MIT

Available Tools

1 tool
get_stock_priceA

Get real-time stock price information for a given ticker symbol. Returns last price, timestamp, market state (PRE/REGULAR/AFTER/POST/CLOSED), and currency.

ParametersJSON Schema
NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., AAPL, TSLA, 005930.KS)

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses the return data (price, timestamp, market state, currency) but does not mention behavioral traits like rate limits, error handling, data freshness, or authentication needs. This is a significant gap for a tool with no annotation coverage.

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 appropriately sized and front-loaded, with two concise sentences that efficiently convey the tool's purpose and return values without any wasted words. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is complete enough for basic use. However, it lacks details on behavioral aspects like rate limits or error handling, which are important for a real-time data tool with no annotation coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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 the single parameter ('ticker'). The description adds marginal value by specifying the resource ('stock price information') and implying the ticker's purpose, but does not provide additional syntax or format details beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get real-time stock price information') and resource ('for a given ticker symbol'), with no siblings to differentiate from. It precisely explains what the tool does without being vague or tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (real-time stock price lookup) but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. With no sibling tools, this is adequate but lacks explicit guidance.

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. 1 tool updatev1.0.0
    • First observedget_stock_price

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_stock_price' has a clearly distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming pattern cannot be inconsistent when there is only one tool. The tool name 'get_stock_price' follows a clear verb_noun convention that would be consistent if more tools existed.

Tool Count2/5

A single tool is generally too few for a server's purpose unless it's extremely narrow. For a stock price server, one might expect additional tools like historical data, multiple tickers, or market indicators, making this feel thin and limited in scope.

Completeness2/5

The server is severely incomplete for a stock price domain. While it provides real-time prices, it lacks essential operations such as historical price data, volume information, company details, or batch queries for multiple stocks, which are common in financial applications.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

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

Related MCP Servers

  • F
    license
    Not graded
    quality
    F
    maintenance
    Provides real-time stock market data and financial analysis through Yahoo Finance integration. Enables users to get quotes, historical prices, fundamentals, dividends, analyst forecasts, and growth projections for any stock symbol.
    4
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    Provides real-time stock market data through Yahoo Finance without requiring an API key. Get quotes, historical data, company information, financial statements, and ticker search capabilities.
    -
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Provides real-time financial data from Yahoo Finance, enabling stock price lookups, historical data analysis, company information retrieval, and multi-stock comparisons through natural language queries.
    -
  • A
    license
    A
    quality
    C
    maintenance
    Provides access to Yahoo Finance data including real-time stock quotes, historical prices, financial statements, company info, symbol search, and news.
    6
    28
    1
    MIT