No user-submitted related servers found.
Scored across 36 tools
The tools are largely separated by resource type — company, insider, transaction, filing, congress, holdings, usage, and status — and descriptions explicitly cross-reference the closest alternatives, making most selections unambiguous. The only real ambiguity is within the status/freshness cluster (health_ingestion, get_data_quality, get_public_stats, get_status_history) and between get_recent_filings and list_filings, though the descriptions do enough to resolve those.
Most tools follow get_<resource> or list_<resource> snake_case conventions, which is a predictable overall pattern. Deviations like research_company, explain_signal, verify_setup, health_ingestion, and check_usage break the dominant pattern, and some collection-returning tools (get_company_insiders, get_insider_transactions) use get_ rather than list_ despite returning lists.
At 36 tools, this exceeds the 25+ threshold where an MCP tool surface becomes too heavy, especially for a single server. Many tools are narrow status, usage, and admin endpoints — check_usage, get_usage_history, get_key_activity, verify_setup, get_public_stats, get_status_history, health_ingestion, and get_data_quality — that could plausibly be consolidated or removed without harming core workflows.
Core Form 4 workflows are well covered: company and insider discovery, transaction search, filing detail, career summaries, scorecards, signals, congressional trades, and institutional holdings all connect without obvious dead ends. The main gaps are minor — no company-name-to-ticker search, no webhook create/delete/update lifecycle despite exposing list_webhooks and get_webhook_events, and no bulk export tool for large pulls.