form4api-mcp
Related Servers
Alternatives to form4api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceVerify insider-purchase, 13D, 8-K and 13F claims against the SEC filing itself (confirmed, partial, not found, out of coverage), plus Form 4, 13D, 13F and federal-award lookups. Every record links to sec.gov. Read-only, no key.92MIT
- AlicenseNot gradedqualityCmaintenanceSEC EDGAR for agents: Form 4 insider trades, cluster buys, filings, XBRL financials and full-text search. Free, no API key.MIT
- AlicenseAqualityDmaintenanceProvides actionable financial intelligence tools for AI agents including insider buying signals, earnings IV plays, market pulse, stock analysis, and options strategies via free public data sources.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to answer questions about what hedge funds, company insiders, activist investors and members of Congress are trading, drawing on 13F filings, Form 4 insider trades, 13D/13G stakes and STOCK Act disclosures. Also supports fund comparison, portfolio cloning backtests, politician performance analysis, and saved watchlists with plan/usage checks.MIT
- AlicenseNot gradedqualityBmaintenanceWall Street data feed for AI agents, providing access to 100M+ source-traced SEC records, institutional holdings, insider trades, congress trading, and more via MCP tools.MIT
- AlicenseAqualityBmaintenanceReal-time financial news for AI agents and trading bots — AI-enriched stories with per-ticker analysis, a 1–10 relevance score, SEC Form-4 insider transactions, plus trending and "actionable-now" feeds. Free tier, OAuth, no API key to paste.2113MIT
TDQS
Scored across 38 tools
There is real overlap risk (get_transactions vs get_insider_transactions vs get_recent_filings vs list_filings; search vs search_insiders vs get_insider_directory; get_signals vs explain_signal vs get_convergence_signals; check_usage vs get_usage_history vs get_key_activity), but the descriptions explicitly cross-reference each other and state when to prefer which tool, which largely resolves the ambiguity for an agent.
Almost all tools use a consistent snake_case verb_noun pattern (get_*, list_*, search_*), with only minor deviations like the bare `search`, `explain_signal`, and `verify_setup`. Nothing is chaotic or mixed-cased, so the pattern is predictable.
38 tools is heavy, though the server spans several distinct domains (Form 4, Form 144, 13F holdings, Schedule 13D/G, congressional trades, webhooks, key/usage, health). The breadth partly justifies the count, but it sits at the borderline-to-excessive end where consolidation (e.g. merged usage tools or a unified search) would help.
Coverage is broad and read-oriented: companies, insiders, transactions, filings, signals, congress, holdings, usage, and health are all represented, with sensible free-text resolution via `search`. The main gap is the webhook lifecycle — subscriptions can be listed and replayed but never created, edited, enabled, or deleted via tools despite the API supporting it.