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

알파 밴티지 스톡 MCP 서버

Alpha Vantage API에서 주식 시장 데이터를 제공하는 모델 컨텍스트 프로토콜(MCP) 서버입니다. Claude를 비롯한 MCP 클라이언트는 이를 통해 실시간 및 과거 주식 데이터에 접근할 수 있습니다.

특징

사용자 정의 가능한 간격으로 일중 주식 데이터를 얻으세요
매일 주식 데이터를 받으세요
가격 변동에 따라 주식 알림 생성
주식 데이터를 리소스로 접근하세요

Related MCP server: Stock Market MCP Server

필수 조건

Node.js 16 이상
Alpha Vantage API 키( Alpha Vantage 에서 무료로 받으세요)

설치

이 저장소를 복제하세요
종속성 설치:
지엑스피1
루트 디렉토리에 .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와 함께 데스크톱 사용

Claude for Desktop과 함께 이 MCP 서버를 사용하려면:

데스크톱용 Open 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 (선택 사항): 반환할 데이터 양(compact: 최근 100개 데이터 포인트, full: 최대 20년 분의 데이터). 기본값: compact

매일 주식 데이터 가져오기

특정 종목에 대한 일일 주가 데이터를 가져옵니다.

매개변수:

symbol (필수): 주식 기호(예: IBM, AAPL)
outputsize (선택 사항): 반환할 데이터 양(compact: 최근 100개 데이터 포인트, full: 최대 20년 분의 데이터). 기본값: compact

주식 알림 받기

가격 변동에 따라 알림을 생성하기 위해 주식 데이터를 분석합니다.

매개변수:

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

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

알파 밴티지 스톡 MCP 서버

특징

필수 조건

설치

건물과 운영

Claude와 함께 데스크톱 사용

사용 가능한 도구

주식 데이터 가져오기

매일 주식 데이터 가져오기

주식 알림 받기

사용 가능한 리소스

주식 데이터

특허

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches