TradeStar Insider
ข้อมูล SEC EDGAR ที่ตรวจสอบกับเอกสารยื่นแล้วสำหรับผู้ช่วย AI: การซื้อหุ้นโดยผู้บริหารในแบบฟอร์ม 4, การถือหุ้นเชิงรุกใน 13D, การเปลี่ยนแปลงการถือครองกองทุนใน 13F, เหตุการณ์ใน 8-K และสัญญารัฐบาลกลาง ทุกรายการเชื่อมโยงไปยังเอกสารยื่นของตน; เครื่องมือตรวจสอบยืนยันข้อกล่าวอ้างเทียบกับเอกสารที่ยื่น ไม่มีคะแนน ไม่มีการคาดการณ์ ฟรี ไม่ต้องสมัครสมาชิก
เอกสาร
Connect the TradeStar Insider MCP server
A remote MCP server that gives an AI assistant filing-verified U.S. SEC signals — insider Form-4 buys, activist 13D stakes, 13F position changes, and federal contract awards — with every figure linked to its source filing. No sign-up, no API key.
Connector URL (Streamable HTTP):
https://mcp.tradestarinsider.com/mcp
Auth: none. Per-IP rate limited. Read-only public data.
Add it in Claude
Claude Code (CLI)
claude mcp add --transport http insider-signals https://mcp.tradestarinsider.com/mcp
Then start Claude and ask one of the prompts below. Verify it connected with claude mcp list.
Claude Desktop / claude.ai (Connectors)
- Open Settings → Connectors (Claude Desktop or claude.ai).
- Choose Add custom connector.
- Name it TradeStar Insider and paste the URL
https://mcp.tradestarinsider.com/mcp. - Save. No credentials are required — leave auth empty. No sign-in required. The 9 tools appear once it connects.
Other MCP clients
Any client that speaks Streamable HTTP MCP works — point it at the same URL. For clients that only run local (stdio) servers, a thin stdio proxy (insider-signals-mcp) is being published; until then, use the remote URL directly.
What you can ask — one example per tool family
Nine tools, grouped into five families. Each returns fields parsed straight from the filing, with the sec.gov (or USAspending) source link — never a guess; absence is reported as absence.
| Family | Tools | Example prompt |
|---|---|---|
| Insider Form-4 buys | insider_buys, insider_cluster_buys | "Show today's notable insider code P buys, and any clusters where several insiders at one company bought in the same window." |
| Activist 13D stakes | activist_stakes_recent | "What activist 13D stakes were disclosed in the last two weeks?" |
| 13F position changes | fund_position_changes | "What were the biggest 13F position changes filed in the latest quarter?" |
| Federal contract awards | federal_awards_recent | "List the largest recent federal contract awards." |
| Verify a claim against the filing | verify_insider_purchase, verify_activist_13d, verify_8k_event, verify_13f_change | "Verify that the CEO of $TICKER bought about $2M of stock last week — cite the Form 4." |
List controls
Every list route (today, clusters, by-ticker, by-range, amendments) takes the same optional query parameters. The response echoes the ones you set and always reports total_matched, so you page rather than hit a silent cap.
| Parameter | Meaning |
|---|---|
limit | Max rows returned (default 25, newest-first); limit<=0 removes the cap. |
offset | Rows to skip before this page (pagination). |
days | Keep only rows filed within the last N days (relative to today). |
ticker | Case-insensitive exact ticker filter. |
as_of | Publish-boundary replay. A UTC ISO-8601 instant (or a bare YYYY-MM-DD, read as end-of-day UTC). Returns only rows that had crossed our publish boundary at or before it — the exact feed a client would have seen at that past moment. |
Every listing row carries first_served_at — the UTC ISO-8601 instant that row first crossed our publish boundary (the atomic write that made it public). It is stamped once per ingest batch and never rewritten, so it anchors as_of replay and publish-latency measurement. On rows materialized before the field existed it is null, explained under partial_fields (and such rows are kept by an as_of query, since they were already public before the field). as_of is the companion to days: days bounds the filing date, as_of bounds when we served it.
Walk-through guides
- Verify an insider purchase against its SEC Form 4 filing
- Check insider purchases with an AI assistant
- Read 13F fund position changes
REST alternative
Prefer HTTP? The same data is available over a REST API described by an OpenAPI 3.0 contract. The /v1/health and /v1/openapi.json routes are open; data routes are served on the keyed tier via RapidAPI.