Skip to main content
Glama
enesjakozh
twolven

OptionsFlow MCP Server

by twolven
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

OptionsFlow MCP 서버

Yahoo Finance를 통해 고급 옵션 분석 및 전략 평가를 제공하는 모델 컨텍스트 프로토콜(MCP) 서버입니다. LLM이 옵션 체인을 분석하고, 그리스어를 계산하고, 포괄적인 위험 지표를 사용하여 기본 옵션 전략을 평가할 수 있도록 지원합니다.

특징

옵션 분석

  • 완전한 옵션 체인 데이터 처리

  • 그리스인의 계산(델타, 감마, 세타, 베가, 로)

  • 내재 변동성 분석

  • 확률 계산

  • 위험/보상 지표

전략 분석

  • 신용 콜 스프레드(CCS)

  • 풋 신용 스프레드(PCS)

  • 현금 담보 풋(CSP)

  • 커버드 콜(CC)

  • 그리스인들의 위치 평가

  • 유동성 분석

  • 위험 지표 계산

위험 관리

  • 매수-매도 스프레드 분석

  • 볼륨 및 미결제약정 검증

  • 포지션 크기 권장 사항

  • 최대 손실 계산

  • 이익 추정의 확률

Related MCP server: MCP Yahoo Finance

설치

지엑스피1

용법

Claude 구성에 다음을 추가합니다. claude-desktop-config.json 에서 mcpServers 섹션에 다음을 추가합니다.

{
    "mcpServers": {
        "optionsflow": {
            "command": "python",
            "args": ["path/to/optionsflow.py"]
        }
    }
}

"path/to/optionsflow.py"를 optionsflow.py 파일을 저장한 전체 경로로 바꾸세요.

사용 가능한 도구

  1. analyze_basic_strategies

{
    "symbol": str,                    # Required: Stock symbol
    "strategy": str,                  # Required: "ccs", "pcs", "csp", or "cc"
    "expiration_date": str,          # Required: "YYYY-MM-DD"
    "delta_target": float,           # Optional: Target delta for CSP/CC (default: 0.3)
    "width_pct": float              # Optional: Width for spreads (default: 0.05)
}

전략 분석 응답 형식

{
    "symbol": str,
    "strategy": str,
    "current_price": float,
    "expiration": str,
    "days_to_expiration": int,
    "analysis": {
        # Credit Call Spread / Put Credit Spread
        "strikes": {
            "short_strike": float,
            "long_strike": float
        },
        "metrics": {
            "credit": float,
            "max_loss": float,
            "max_profit": float,
            "probability_of_profit": float,
            "risk_reward_ratio": float
        },
        "greeks": {
            "net_delta": float,
            "net_theta": float,
            "net_gamma": float
        }
        
        # Cash Secured Put
        "strike": float,
        "metrics": {
            "premium": float,
            "max_loss": float,
            "assigned_cost_basis": float,
            "return_if_otm": float,
            "downside_protection": float
        },
        "greeks": {
            "delta": float,
            "theta": float,
            "gamma": float
        }
        
        # Covered Call
        "strike": float,
        "metrics": {
            "premium": float,
            "max_profit": float,
            "max_profit_percent": float,
            "upside_cap": float,
            "premium_yield": float
        },
        "greeks": {
            "position_delta": float,
            "theta": float,
            "gamma": float
        }
    }
}

요구 사항

  • 파이썬 3.12+

  • 엠씨피

  • 와이파이낸스

  • 팬더

  • 넘파이

  • 사이피

제한 사항

  • Yahoo Finance에서 얻은 데이터로 지연 가능성이 있음

  • 옵션 데이터 가용성은 시장 시간에 따라 달라집니다.

  • Yahoo Finance API 제한에 따른 요금 제한

  • 그리스인의 계산은 이론적이며 Black-Scholes 모델을 기반으로 합니다.

  • 조기 배정 위험은 확률 계산에 반영되지 않음

기여하다

기여를 환영합니다! 풀 리퀘스트를 제출해 주세요.

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 라이선스 파일을 참조하세요.

작가

토드 울븐 - ( https://github.com/tolven )

감사의 말

  • Anthropic의 MCP(Model Context Protocol)로 구축됨

  • Yahoo Finance 에서 제공하는 데이터

  • Anthropic의 Claude와 함께 사용하도록 개발됨

Available Tools

1 tool
analyze_basic_strategiesB

Analyze one legacy options strategy using executable quotes and European Black-Scholes estimates.

ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYesYahoo Finance ticker symbol
strategyYesOptions strategy: call credit spread, put credit spread, cash-secured put, or covered call
width_pctNoTarget spread width as a fraction of the short strike
delta_targetNoAbsolute target delta for CSP/CC selection
expiration_dateYesExpiration date in YYYY-MM-DD format

Output Schema

ParametersJSON Schema
NameRequiredDescription
dataYes
successYes
providerYes
warningsYes
timestampYes

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does add useful context by specifying that the analysis uses executable quotes and European Black-Scholes estimates, implying a read-only estimation nature. However, it does not disclose limitations, what 'legacy' means, or any other behavioral traits such as data-source assumptions or scope constraints.

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

Conciseness5/5

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

The description is a single, tightly written sentence that communicates the core action and method without filler. It is front-loaded with the main purpose and wastes no words.

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

Completeness3/5

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

The input schema and output schema cover parameter details and return structure, so the description does not need to explain those. However, lack of usage guidance and limited behavioral disclosure leave the description only minimally complete for an agent deciding when and how to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 100% of parameters with descriptions, so the baseline is 3. The description does not add parameter-level meaning beyond the schema; it only frames the overall pricing/analysis methodology. No compensation is needed, but no extra value is provided either.

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

Purpose4/5

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

The description states a clear verb ('Analyze') and a specific resource ('one legacy options strategy'), and adds method context ('executable quotes and European Black-Scholes estimates'). However, 'legacy' is not explained, and with no sibling tools listed there is no explicit differentiation from alternatives.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives, nor any exclusions or prerequisites. The description only implies that the tool is for analyzing an options strategy, but it does not state conditions or compare to other possible approaches.

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

B3.4/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly articulated.

Naming Consistency5/5

The single tool name 'analyze_basic_strategies' follows a clear verb_noun pattern and is syntactically consistent. There are no other names to create inconsistency.

Tool Count3/5

One tool feels very thin for a server named 'OptionsFlow', which implies a broader range of options-related functionality. However, if the intended scope is strictly basic strategy analysis, the single tool is borderline acceptable.

Completeness2/5

The server only covers basic strategy analysis, leaving gaps for advanced strategies, other analytical features, or workflow operations. Agents needing additional options functionality will hit dead ends.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

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

Related MCP Connectors

Related MCP Servers

  • StockFlow MCP Server

    twolven
    A
    license
    B
    quality
    B
    maintenance
    A Model Context Protocol server providing real-time stock data and options analysis through Yahoo Finance, enabling LLMs to access market data, analyze stocks, and evaluate options strategies.
    3
    25
    MIT

  • MCP Yahoo Finance

    maxscheijen
    A
    license
    B
    quality
    B
    maintenance
    A Model Context Protocol server that enables interaction with Yahoo Finance to retrieve stock pricing, company information, and historical financial data through natural language queries.
    10
    29
    MIT

  • MCP Yahoo Finance

    marckwei
    A
    license
    C
    quality
    Not graded
    maintenance
    A Model Context Protocol server that provides tools for interacting with Yahoo Finance, allowing users to retrieve stock prices, company information, and perform financial data comparisons.
    11

  • Yahoo Finance MCP Server

    16Coffee
    A
    license
    C
    quality
    D
    maintenance
    A Model Context Protocol server providing comprehensive financial data from Yahoo Finance, allowing users to retrieve detailed stock information, financial statements, options data, and market news.
    34
    MIT

Appeared in Searches

Latest Blog Posts

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/twolven/mcp-optionsflow'

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