en es ja ko zh

@qubaomingg/stock-mcp

Name: @qubaomingg/stock-mcp
Author: qubaomingg

by qubaomingg

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Alpha Vantage ストック MCP サーバー

これは、Alpha Vantage APIから株式市場データを提供するモデルコンテキストプロトコル（MCP）サーバーです。ClaudeをはじめとするMCPクライアントは、このサーバーを通じてリアルタイムおよび過去の株式データにアクセスできます。

特徴

カスタマイズ可能な間隔で日中株価データを取得する
毎日の株価データを取得する
価格変動に基づいて株価アラートを生成する
株価データをリソースとしてアクセス

Related MCP server: Stock Market 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

Claude for Desktop と併用

この 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分）。デフォルト: daily

Claude での使用例:

「この株価データを分析できますか: stock://AAPL/daily」
「このデータについてどう思いますか: stock://MSFT/5min」

ライセンス

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.

Tool Schema Changelog

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

3 tool updatesv1.0.0Jan 3, 2026
- 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
```
3 tool updatesOct 1, 2025
- 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 2026-04-18 11:20 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

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

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
422
FensoryOAuth
com.fensory
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
Finance Cryptocurrency Blockchain
1
mcp-openaiOAuth
io.github.AceDataCloud
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
AI & Machine Learning Image & Video Processing
11

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 2 years ago (2025-04-03 18:10 UTC)
2
23 npm
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 2 years 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 7 months ago (2026-03-26 03:14 UTC)
18
151 PyPI
390
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
23 npm
MIT

Alpha Vantage ストック MCP サーバー

特徴

前提条件

インストール

構築と実行

Claude for Desktop と併用

利用可能なツール

株価データ取得

毎日の株価データを取得する

株価アラートを取得する

利用可能なリソース

株価データ

ライセンス

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches