这是一个模型上下文协议 (MCP) 服务器，提供来自 Alpha Vantage API 的股票市场数据。它允许 Claude 和其他 MCP 客户端访问实时和历史股票数据。
获取可自定义间隔的盘中股票数据
获取每日股票数据
根据价格变动生成股票警报
访问股票数据作为资源
Related MCP server: Alpha Vantage MCP Server
Node.js 16 或更高版本
Alpha Vantage API 密钥（可在Alpha Vantage免费获取）
克隆此存储库
安装依赖项：
npm install在根目录中创建一个.env文件并添加您的 Alpha Vantage API 密钥：
ALPHA_VANTAGE_API_KEY=your_api_key_here构建 TypeScript 代码：
npm run build运行服务器：
npm start对于自动重新加载的开发：
npm run dev测试 API 客户端：
npm test要将此 MCP 服务器与 Claude for Desktop 一起使用：
打开 Claude 桌面版
前往“设置”>“开发者”>“编辑配置”
将以下内容添加到您的claude_desktop_config.json中：
{
"mcpServers": {
"alpha-vantage": {
"command": "node",
"args": ["/absolute/path/to/dist/index.js"],
"env": {
"ALPHA_VANTAGE_API_KEY": "YOUR_API_KEY"
}
}
}
}将/absolute/path/to/dist/index.js替换为构建的 index.js 文件的绝对路径。
重启 Claude 桌面版
获取特定代码的盘中股票数据。
参数：
symbol （必填）：股票代码（例如 IBM、AAPL）
interval （可选）：数据点之间的时间间隔（1分钟、5分钟、15分钟、30分钟、60分钟）。默认值：5分钟
outputsize （可选）：返回的数据量（紧凑型：最新 100 个数据点，完整型：最多 20 年的数据）。默认值：紧凑型
获取特定代码的每日股票数据。
参数：
symbol （必填）：股票代码（例如 IBM、AAPL）
outputsize （可选）：返回的数据量（紧凑型：最新 100 个数据点，完整型：最多 20 年的数据）。默认值：紧凑型
分析股票数据以根据价格变动生成警报。
参数：
symbol （必填）：股票代码（例如 IBM、AAPL）
threshold （可选）：价格波动警报的百分比阈值。默认值：5
直接访问股票数据作为资源。
URI 模板： stock://{symbol}/{interval}
参数：
symbol ：股票代码（例如 IBM、AAPL）
interval ：时间间隔（每日、1分钟、5分钟、15分钟、30分钟、60分钟）。默认值：每日
Claude 中的用法示例：
“您能分析一下这个股票数据吗：stock://AAPL/daily”
“您如何看待此数据：stock://MSFT/5min”
麻省理工学院
| 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) |
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.
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.
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.
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.
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.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Stock symbol (e.g., IBM, AAPL) | |
| threshold | No | Percentage threshold for price movement alerts (default: 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.
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.
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.
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.
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.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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) |
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.
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.
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.
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0get-daily-stock-dataget-stock-alertsget-stock-dataScored across 3 tools
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 differences. 'get-stock-alerts' might be distinct but lacks context, making it unclear how it differs from the data retrieval tools. This setup will likely cause frequent agent misselection.
The naming follows a consistent pattern with kebab-case and a 'get-' verb prefix across all tools, which is predictable and readable. However, the lack of descriptions prevents full evaluation of semantic consistency, but structurally, the naming is uniform.
With only 3 tools, this server feels under-scoped for a stock analysis domain, which typically requires more operations like historical data, indicators, or portfolio management. The count is too low to provide comprehensive coverage, limiting agent capabilities.
The tool set is severely incomplete for stock analysis. It lacks essential operations such as intraday data, technical indicators, company fundamentals, or search functions. With only basic data retrieval and alerts, agents will face dead ends and cannot perform meaningful analysis.
Alpha Vantage MCP — Stock market data, fundamentals, and earnings
Financial data MCP server for Claude, ChatGPT, Cursor and Codex. Real-time stock quotes, financial statements, options flow, SEC filings, insider trades, 13F holdings, macro data and market news from gloom.sh, the open-source Bloomberg Terminal alternative.
Twelve Data MCP: real-time & historical market data (stocks, crypto, forex, etc).
Stock market data for AI agents: real-time quotes, financials, options, SEC filings and news.
