Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TickerRisk

PYPI · TICKERRISK-MCP

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

Available components

−19 this week 61 Trust /100

Last scanned (14 hours ago)

Scores higher than 58% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1251 tokens (~312/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 −5
    • Stability: pass → 0.60 functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed pypi/tickerrisk-mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,076 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_tickers ~164

Compare catalyst risk across several stocks at once, over the same expiry window. Use this when someone is choosing between tickers to sell options on, or asks which of several stocks is the safest bet for a given expiry. Faster than scanning one at a time. Only returns tickers already in the cache (all S&P 500 names are); anything missing is listed so it can be scanned individually with scan_ticker. Args: tickers: Comma-separated symbols, e.g. "AAPL, MSFT, NVDA". Up to 25. expiry_weeks: Expiry horizon in weeks (1-52), applied to every ticker.

NameTypeReqDescription
expiry_weeksinteger––
tickersstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

find_covered_calls ~267

Find covered-call candidates that have no hidden catalyst in the expiry window. Use this when someone asks what calls to sell against shares they own, for covered-call income ideas, or how to generate yield on a stock position. Same catalyst gating as the wheel scanner. Income is computed from TIME VALUE only, so in-the-money strikes do not show inflated yields. Args: week: Expiry bucket — "this", "next", "two", "three", "month", or "all". risk: "conservative" (further out of the money, more likely to keep the shares), "balanced", or "aggressive" (nearer the money, more premium, more likely to be called away). max_risk: Maximum catalyst-risk score to allow, 0-100. min_call_oi: Minimum call open interest, for tradeable results. sector: Optional GICS sector filter. Empty means all sectors. limit: How many candidates to return (1-25).

NameTypeReqDescription
limitinteger––
max_risknumber––
min_call_oiinteger––
riskstring––
sectorstring––
weekstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

find_wheel_candidates ~399

Find cash-secured put candidates (the wheel strategy) that have no hidden catalyst in the expiry window. Use this when someone asks what puts to sell this week, for wheel or cash-secured-put ideas, for "safe premium" to collect, or which stocks pay well without an earnings report coming up. Scans the whole S&P 500 and returns only names whose catalyst-risk score over the option's own expiry window is under max_risk — so candidates with earnings, FDA decisions or legal events inside the window are filtered out rather than surfaced as fake high-yield opportunities. Args: week: Expiry bucket — "this" (1-7 days), "next" (8-14), "two", "three", "month" (1-35), or "all" (up to 45 days). "all" returns the most results. risk: How close to the money to sell — "conservative" (~0.20 delta, further out, safer), "balanced" (~0.30), or "aggressive" (~0.40, more premium, more assignment risk). max_risk: Maximum catalyst-risk score to allow, 0-100. 55 is a sensible default; lower it to 40 for a stricter list. min_put_oi: Minimum put open interest, to keep results actually tradeable. Keep at 100 during market hours. sector: Optional GICS sector filter, e.g. "Technology", "Health Care", "Financials". Empty means all sectors. limit: How many candidates to return (1-25).

NameTypeReqDescription
limitinteger––
max_risknumber––
min_put_oiinteger––
riskstring––
sectorstring––
weekstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

scan_ticker ~246

Check how risky it is to sell or buy an option on a stock, over a specific expiry window. Use this whenever someone asks whether it is safe to sell a put or a covered call on a ticker, whether a premium is "too good", what could gap a stock before expiry, or what catalysts are coming up for a company. Returns a 0-100 catalyst-risk score (higher = riskier) plus the specific events driving it: earnings dates, FDA decisions, legal filings, SEC events, and the implied-volatility expected move. The key idea is that risk depends on the expiry window — a stock can be LOW risk for a 1-week option and HIGH risk for a 6-week option that spans an earnings report. Args: ticker: Stock symbol, e.g. "AAPL", "HPE", "KO". expiry_weeks: How many weeks until the option expires (1-52). Match this to the actual trade being considered. Defaults to 4 (~30 DTE, the typical premium-selling horizon).

NameTypeReqDescription
expiry_weeksinteger––
tickerstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the TickerRisk MCP server?

TickerRisk runs locally as a PyPI package, launched with uvx tickerrisk-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · tickerrisk-mcp

# add to Claude Code
claude mcp add pasiutusvovere-tickerrisk-mcp -- uvx tickerrisk-mcp
Common questions

What is the TickerRisk MCP server?

TickerRisk is an MCP server listed in the public MCP registry as io.github.PasiutusVovere/tickerrisk-mcp. Check options trades for hidden catalysts (earnings, FDA, legal, SEC) before you sell premium. This page covers its PyPI package (tickerrisk-mcp).

Is the TickerRisk MCP server safe to use?

TickerRisk scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TickerRisk MCP server expose?

TickerRisk exposes 4 tools: scan_ticker, find_wheel_candidates, find_covered_calls, compare_tickers. Their descriptions and schemas cost roughly 1,076 tokens of context every time the server is loaded.

Is the TickerRisk MCP server still maintained?

TickerRisk is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the TickerRisk MCP server under?

TickerRisk declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.