TickerRisk MCP Server

Check options trades for hidden catalysts (earnings, FDA, legal, SEC) before you sell premium.

Local serverstdioGo

What is the TickerRisk MCP server?

TickerRisk MCP server exists for a simple reason — assistants are far more useful when they can act on TickerRisk directly instead of describing what you should do. Check options trades for hidden catalysts (earnings, FDA, legal, SEC) before you sell premium.

What you get

An MCP server that lets an AI assistant answer questions like "is it safe to sell a 30-day put on HPE?" with real event data instead of a guess.

What the assistant can call

Once TickerRisk is connected, these are the calls the assistant has available:

  • scan_ticker — "How risky is selling an option on X over the next N weeks?"
  • find_wheel_candidates — "What cash-secured puts can I sell this week without an earnings trap?"
  • find_covered_calls — "What calls can I sell against shares I already own?"
  • compare_tickers — "Which of these stocks is safest to sell premium on right now?"
  • Cursor — The Cursor tool exposed by this server

Configuration and credentials

You will need 2 environment variables: TICKERRISK_TOKEN, TICKERRISK_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at tickerrisk-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. TickerRisk's toolset — scan_ticker, find_wheel_candidates, find_covered_calls and 2 more — is a fair guide to whether it matches your workflow. It is maintained by PasiutusVovere; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the tickerrisk mcp server does with a few real requests.

Available tools

ToolWhat it does
scan_ticker"How risky is selling an option on X over the next N weeks?"
find_wheel_candidates"What cash-secured puts can I sell this week without an earnings trap?"
find_covered_calls"What calls can I sell against shares I already own?"
compare_tickers"Which of these stocks is safest to sell premium on right now?"
CursorThe Cursor tool exposed by this server.

How to install the TickerRisk MCP server

{
  "mcpServers": {
    "tickerrisk": {
      "command": "uvx",
      "args": ["tickerrisk-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
TICKERRISK_TOKENCredential the server authenticates with.Yes
TICKERRISK_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use TickerRisk to scan ticker.
  • Use TickerRisk to find wheel candidates.
  • Use TickerRisk to find covered calls.

Frequently asked questions

It connects TickerRisk to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (scan_ticker, find_wheel_candidates, find_covered_calls, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with TickerRisk directly.