Skip to main content
Glama
enesjakozh
qubaomingg

@qubaomingg/stock-mcp

by qubaomingg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Alpha Vantage Stock MCP 服务器

这是一个模型上下文协议 (MCP) 服务器，提供来自 Alpha Vantage API 的股票市场数据。它允许 Claude 和其他 MCP 客户端访问实时和历史股票数据。

特征

  • 获取可自定义间隔的盘中股票数据

  • 获取每日股票数据

  • 根据价格变动生成股票警报

  • 访问股票数据作为资源

Related MCP server: Stock Market MCP Server

先决条件

  • Node.js 16 或更高版本

  • Alpha Vantage API 密钥（可在Alpha Vantage免费获取）

安装

  1. 克隆此存储库

  2. 安装依赖项：

    npm install

  3. 在根目录中创建一个.env文件并添加您的 Alpha Vantage API 密钥：

    ALPHA_VANTAGE_API_KEY=your_api_key_here

构建和运行

构建 TypeScript 代码：

npm run build

运行服务器：

npm start

对于自动重新加载的开发：

npm run dev

测试 API 客户端：

npm test

与 Claude for Desktop 一起使用

要将此 MCP 服务器与 Claude for Desktop 一起使用：

  1. 打开 Claude 桌面版

  2. 前往“设置”>“开发者”>“编辑配置”

  3. 将以下内容添加到您的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 文件的绝对路径。

  1. 重启 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”

执照

国际学习中心

Available Tools

3 tools
get-daily-stock-dataD
ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol (e.g., IBM, AAPL)
outputsizeNoAmount 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
NameRequiredDescriptionDefault
symbolYesStock symbol (e.g., IBM, AAPL)
thresholdNoPercentage 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
NameRequiredDescriptionDefault
symbolYesStock symbol (e.g., IBM, AAPL)
intervalNoTime interval between data points (default: 5min)
outputsizeNoAmount 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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.0
    • Changedget-daily-stock-data2 fields changed
      • addedInput schema / $schema
        Added value: +"http://json-schema.org/draft-07/schema#"
      • addedInput schema / additionalProperties
        Added value: +false
    • Changedget-stock-alerts2 fields changed
      • addedInput schema / $schema
        Added value: +"http://json-schema.org/draft-07/schema#"
      • addedInput schema / additionalProperties
        Added value: +false
    • Changedget-stock-data2 fields changed
      • addedInput schema / $schema
        Added value: +"http://json-schema.org/draft-07/schema#"
      • addedInput schema / additionalProperties
        Added value: +false
  2. 3 tool updates
    • First observedget-daily-stock-data
    • First observedget-stock-alerts
    • First observedget-stock-data
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.4/5.0

Scored across 3 tools

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
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches