Which integrations are available for this server?

Supports loading environment variables from a .env file to securely store and access the Alpha Vantage API key needed for authentication. Runs on Node.js as the server environment, with compatibility for Node.js 16 or higher versions. Uses npm for package management and running scripts for building, testing, and launching the server. Built using TypeScript for type safety and improved code organization, requiring compilation to JavaScript before execution.

How do I use @qubaomingg/stock-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@qubaomingg/stock-mcp get daily stock data for AAPL" 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.

en es ja ko zh

@qubaomingg/stock-mcp

by qubaomingg

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Alpha Vantage Stock MCP Server

This is a Model Context Protocol (MCP) server that provides stock market data from Alpha Vantage API. It allows Claude and other MCP clients to access real-time and historical stock data.

Features

Get intraday stock data with customizable intervals
Get daily stock data
Generate stock alerts based on price movements
Access stock data as resources

Related MCP server: Stock Market MCP Server

Prerequisites

Node.js 16 or higher
An Alpha Vantage API key (get one for free at Alpha Vantage)

Installation

Clone this repository
Install dependencies:
```
npm install
```
Create a .env file in the root directory and add your Alpha Vantage API key:
```
ALPHA_VANTAGE_API_KEY=your_api_key_here
```

Building and Running

Build the TypeScript code:

npm run build

Run the server:

npm start

For development with auto-reloading:

npm run dev

Test the API client:

npm test

Using with Claude for Desktop

To use this MCP server with Claude for Desktop:

Open Claude for Desktop
Go to Settings > Developer > Edit Config
Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "alpha-vantage": {
      "command": "node",
      "args": ["/absolute/path/to/dist/index.js"],
      "env": {
        "ALPHA_VANTAGE_API_KEY": "YOUR_API_KEY"
      } 
    }
  }
}

Replace /absolute/path/to/dist/index.js with the absolute path to the built index.js file.

Restart Claude for Desktop

Available Tools

get-stock-data

Gets intraday stock data for a specific symbol.

Parameters:

symbol (required): Stock symbol (e.g., IBM, AAPL)
interval (optional): Time interval between data points (1min, 5min, 15min, 30min, 60min). Default: 5min
outputsize (optional): Amount of data to return (compact: latest 100 data points, full: up to 20 years of data). Default: compact

get-daily-stock-data

Gets daily stock data for a specific symbol.

Parameters:

symbol (required): Stock symbol (e.g., IBM, AAPL)
outputsize (optional): Amount of data to return (compact: latest 100 data points, full: up to 20 years of data). Default: compact

get-stock-alerts

Analyzes stock data to generate alerts based on price movements.

Parameters:

symbol (required): Stock symbol (e.g., IBM, AAPL)
threshold (optional): Percentage threshold for price movement alerts. Default: 5

Available Resources

stock-data

Access stock data directly as a resource.

URI Template: stock://{symbol}/{interval}

Parameters:

symbol: Stock symbol (e.g., IBM, AAPL)
interval: Time interval (daily, 1min, 5min, 15min, 30min, 60min). Default: daily

Example usage in Claude:

"Can you analyze this stock data: stock://AAPL/daily"
"What do you think about this data: stock://MSFT/5min"

License

ISC

Available Tools

3 tools

get-daily-stock-dataD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Stock symbol (e.g., IBM, AAPL)
`outputsize`	No	Amount of data to return (compact: latest 100 data points, full: up to 20 years of data)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-stock-alertsD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Stock symbol (e.g., IBM, AAPL)
`threshold`	No	Percentage threshold for price movement alerts (default: 5)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-stock-dataD

ParametersJSON Schema

Name	Required	Description
`symbol`	Yes	Stock symbol (e.g., IBM, AAPL)
`interval`	No	Time interval between data points (default: 5min)
`outputsize`	No	Amount of data to return (compact: latest 100 data points, full: up to 20 years of data)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.4/5.0

Disambiguation1/5

The tools are highly ambiguous and overlapping. 'get-daily-stock-data' and 'get-stock-data' appear to serve nearly identical purposes, with no description to clarify their differences. 'get-stock-alerts' might be distinct but lacks context, making the overall set confusing and prone to misselection.

Naming Consistency5/5

The naming is perfectly consistent, using a kebab-case pattern with a 'get-' prefix followed by a noun phrase. All three tools follow this exact convention, making them predictable and easy to parse.

Tool Count2/5

With only 3 tools, the set feels thin and under-scoped for a stock data server. It lacks essential operations like search, update, or delete, and the limited coverage suggests it may not support comprehensive agent workflows in this domain.

Completeness1/5

The tool surface is severely incomplete for a stock data domain. It only provides 'get' operations with no ability to set, modify, or manage data (e.g., no create, update, delete, or search tools). This will cause significant agent failures in handling stock-related tasks.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

stocksense-ai
io.github.doc2mcp
MCP server for stocksense-ai documentation, generated by doc2mcp.
Documentation Access Finance
24
Alphavantage A
io.github.pipeworx-io
Alpha Vantage MCP — Stock market data, fundamentals, and earnings
Finance Search Open Data
372
smithery-ai-cookbook-python-quickstart
ai.smithery
A simple MCP server built with FastMCP and python
Developer Tools
213
Second server!
com.fenetresurciel.verylongmcp
A non functional MCP server (yet)
Developer Tools
2

Related MCP Servers

findata-mcp-server
Finance RAG Systems
xBlueCode
A
license
B
quality
D
maintenance
This is an MCP server that provides access to the Alpha Vantage API, allowing stock data retrieval to be used as context to LLMs.
Updated a year ago (2025-04-03 18:10 UTC)
2
24
9
MIT
Stock Market MCP Server
Finance Search
MCP-100
F
license
B
quality
D
maintenance
A TypeScript-based MCP server that fetches real-time stock market data and company financial information through the Alpha Vantage API.
Updated a year ago (2025-03-17 19:24 UTC)
4
6
MCP Server for stock and
Cryptocurrency Finance Web Scraping
aahl
A
license
A
quality
C
maintenance
📈 提供股票、加密货币的数据查询和分析功能MCP服务器
Updated 5 months ago (2026-03-26 03:14 UTC)
18
391
MIT
Financial Data MCP Server
Finance Research & Data
fastmcp-me
A
license
B
quality
D
maintenance
This is an MCP server that provides access to the Alpha Vantage API, allowing stock data retrieval to be used as context to LLMs.
Updated a year ago (2025-10-05 14:29 UTC)
2
24
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/qubaomingg/stock-analysis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server