TickerRisk MCP Server
Related Servers
Alternatives to TickerRisk MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables biopharma catalyst research by aggregating signals from ClinicalTrials.gov, PubMed, SEC EDGAR, openFDA, and Yahoo Finance, with a single tool to audit a ticker/drug combination and return a forensic verdict.1027 npm5ISC
- AlicenseNot gradedqualityDmaintenanceProvides macro-economic event data, earnings reports, and market overviews as MCP tools, enabling AI agents to query calendars, check event proximity, and assess trade safety.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying FlashAlpha options-exposure analytics, including gamma exposure, key options-derived levels, implied volatility summaries, and Black-Scholes greeks.234 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables risk analysis of US public companies by analyzing 8-K filings and insider activity using live SEC EDGAR data.-
- AlicenseAqualityAmaintenanceEnables users to look up public company earnings dates and reporting windows by providing identifiers like ticker, domain, or CIK. It returns fiscal year end, next reporting date, and an outreach window, helping plan investor communications.529 npmMIT
- AlicenseAqualityBmaintenanceEnables pre-trade risk screening for EVM and Solana tokens, returning a one-line verdict with detailed flags on liquidity, ownership, and other risk factors.1MIT
TDQS
Scored across 4 tools
Each tool targets a clearly distinct action: scan_ticker (single-ticker risk), compare_tickers (batch comparison), find_wheel_candidates (put screening), and find_covered_calls (call screening). The single-vs-batch and put-vs-call boundaries are explicit in the descriptions, leaving little room for misselection.
All four names follow a consistent verb_noun snake_case pattern (scan_ticker, compare_tickers, find_wheel_candidates, find_covered_calls). The plural 'tickers' in compare is minor and still readable.
Four tools is a lean but coherent surface where each earns its place, though it sits at the thin end of the ideal range. No obvious redundancy or bloat.
The workflow is well covered: single scan, multi-ticker comparison, and both screener directions (puts and calls), with missing tickers flagged for individual scanning. Minor gaps exist around analyzing existing positions or custom non-cached tickers, but agents can work around them.