TradeStar Insider
REMOTE · MCP.TRADESTARINSIDER.COM · 3 COMPONENTS
Filing-verified SEC EDGAR insider (Form 4), 13D, 13F & 8-K data, no sign-in. Verify any claim.
Last scanned (17 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3681 tokens (~368/item across 10 items; 10 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- “insider_buys” added an optional parameter “date” cosmetic
- 8 Nov 26 +1
- Stability: 0.97 → pass security
- 7 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 +5
- Stability: fail → 0.97 functional
- 16 Oct 26 0
- Schema quality: 3060 → 3627 ▼ functional
- New tool “insider_amendments_recent” functional
- “insider_buys” added an optional parameter “as_of” cosmetic
- “insider_cluster_buys” added an optional parameter “as_of” cosmetic
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 21 Nov 2026 · Probed https://mcp.tradestarinsider.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tradestarinsider.com | CN=WE1,O=Google Trust Services,C=US | 5 Nov 2026 | 3 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 97ad8bbd2e16f8831327122b4149e91f |
| SANs: tradestarinsider.com, *.tradestarinsider.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.tradestarinsider.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tradestarinsider.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tradestarinsider.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tradestarinsider.com/mcp | Served over HTTP | 200 |
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 →
activist_stakes_recent Recent activist hedge-fund stakes (SEC Schedule 13D) ~244
Use when the user asks about activist investors, hedge-fund stakes, or recent 13D filings on a company. Returns activist Schedule 13D/13D-A filings on US-listed companies, newest first then by stated-intent strength; `ticker`, `min_percent` and `days` narrow. Each row carries its source filing_url and `item4_excerpt` (the activist's own Item 4 intent sentence, quoted from the filing as data, capped at its current length of 600 chars). Caveat: passive 13G is not covered; filings without a source link are dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Only stakes filed within the last N days. |
| limit | integer | – | Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap. |
| min_percent | number | – | Only stakes at or above this percent-of-class |
| offset | integer | – | Rows to skip before this page (pagination). Default 0. |
| ticker | string | – | Filter to one subject ticker (case-insensitive), e.g. DH |
No output schema declared.
No examples provided.
federal_awards_recent Recent U.S. federal contract awards (USAspending.gov) ~172
Use when the user asks about recent federal contracts, government awards, or who won a U.S. federal contract. Returns newly signed federal awards, newest first; `min_amount` sets a USD floor, `days` a last-N-days window. Every award carries its source award_url. Caveat: awards without a source link are dropped and never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Only awards signed within the last N days. |
| limit | integer | – | Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap. |
| min_amount | number | – | Only awards at or above this USD amount |
| offset | integer | – | Rows to skip before this page (pagination). Default 0. |
No output schema declared.
No examples provided.
fund_position_changes Hedge-fund / institutional position changes (SEC 13F, quarter-over-quarter) ~292
Use when the user asks what a fund bought or sold, how a 13F filer changed its holdings, or which institutions opened/added/trimmed/exited a position. Returns quarter-over-quarter deltas, newest first; `filer`, `change_type`, `min_value_usd`, `days` narrow. Each row carries as_of_quarter_end, filed_date, lag_days, value_usd (whole dollars), cusip, issuer_name and its source filing_url; ticker is null (never guessed). Caveat: the delta is the product, not a trading edge — see the instructions and each response's `coverage` note for the universe and CIK scope.
| Name | Type | Req | Description |
|---|---|---|---|
| change_type | string | – | Only this kind of quarter-over-quarter change |
| days | integer | – | Only changes filed within the last N days. |
| filer | string | – | Filter to one fund by name substring (case-insensitive, e.g. 'Berkshire') or exact filer CIK |
| limit | integer | – | Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap. |
| min_value_usd | number | – | Only positions at or above this current value in WHOLE US dollars |
| offset | integer | – | Rows to skip before this page (pagination). Default 0. |
No output schema declared.
No examples provided.
insider_amendments_recent Recent Form 4/A amendments and what each corrected (SEC Form 4/A) ~397
Use when the user asks which insider filings were amended, corrected, or restated, or wants recent Form 4/A amendments. Returns 4/A amendments, newest-filed first; `ticker`, `issuer_name`, `person`, `start`/`end`, `days` narrow. Each row carries the amendment_accession, filed_date, issuer/insider, source filing_url, the original_accession it amends (when collected), and `changed_fields` (before/after). Caveat: when the original is not collected the amendment is still listed with original_in_corpus=false and before/after null (never guessed); linkage is by issuer/owner/period.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Publish-boundary replay: UTC ISO-8601 instant (or a bare YYYY-MM-DD, read as end-of-day UTC). Returns only rows that had crossed the publish boundary at or before it — the exact feed visible at that… |
| days | integer | – | Only amendments filed within the last N days. |
| end | string | – | Only amendments filed on/before this ISO date |
| issuer_name | string | – | Filter by issuer/company name substring (case-insensitive) |
| limit | integer | – | Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap. |
| offset | integer | – | Rows to skip before this page (pagination). Default 0. |
| person | string | – | Filter by insider name substring (case-insensitive) |
| start | string | – | Only amendments filed on/after this ISO date |
| ticker | string | – | Filter to one issuer ticker (case-insensitive substring), e.g. GLBZ |
No output schema declared.
No examples provided.
insider_buys Insider buys by ticker, today, or a date range (SEC Form 4) ~504
Use when the user asks which insiders bought a stock, whether a ticker has insider buying, or for Form 4 buys in a date range. Pass `ticker`, `start`+`end` for an inclusive ISO range, or neither for today's buys (SEC code P); `days` narrows, `include_unlisted` adds non-listed issuers. Each row carries filing_url, `offering_context`, `transaction_date`, `acceptance_datetime`, `aff10b5One` (10b5-1 flag), `is_amendment`/`original_accession` (4/A linkage), and `partial_fields` (reason for any null). Caveat: only purchases that pass the signal filter are returned; code P is not proof of a buy.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Publish-boundary replay: UTC ISO-8601 instant (or a bare YYYY-MM-DD, read as end-of-day UTC). Returns only rows that had crossed the publish boundary at or before it — the exact feed visible at that… |
| date | string | – | Single filing day, ISO YYYY-MM-DD. On a day with no filings the last filing day on or before it is returned (see `last_filing_day`). Ignored when a `start`/`end` range is given. |
| days | integer | – | Only rows filed within the last N days (relative to today). |
| end | string | – | Inclusive range end, ISO YYYY-MM-DD. Give with `start` for a date range. |
| include_unlisted | boolean | – | Include unlisted issuers (blank/NONE/N/A tickers and 5-letter mutual-fund classes). Default false = exchange-listed common stock only. Every row carries a `listed_equity` boolean. |
| limit | integer | – | Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap. |
| offset | integer | – | Rows to skip before this page (pagination). Default 0. |
| start | string | – | Inclusive range start, ISO YYYY-MM-DD. Give with `end` for a date range. |
| ticker | string | – | Case-insensitive exact ticker filter, e.g. DKS. |
No output schema declared.
No examples provided.
insider_cluster_buys Insider cluster buys — multiple insiders buying the same stock (SEC Form 4) ~384
Use when the user asks about cluster buying or several insiders buying the same company. Returns only clusters, two or more insiders buying one issuer in the window, newest first; days and ticker narrow. Each row carries filing_url, offering_context, uniform_price_cluster (true when 3+ insiders bought at one price on one day), `transaction_date`, `acceptance_datetime`, `aff10b5One` (10b5-1 flag), `is_amendment`/`original_accession` (4/A linkage), and `partial_fields` (reason for any null). Caveat: only purchases that pass the signal filter are returned; code P alone is not proof of a buy.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Publish-boundary replay: UTC ISO-8601 instant (or a bare YYYY-MM-DD, read as end-of-day UTC). Returns only rows that had crossed the publish boundary at or before it — the exact feed visible at that… |
| days | integer | – | Only rows filed within the last N days (relative to today). |
| include_unlisted | boolean | – | Include unlisted issuers (blank/NONE/N/A tickers and 5-letter mutual-fund classes). Default false = exchange-listed common stock only. Every row carries a `listed_equity` boolean. |
| limit | integer | – | Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap. |
| offset | integer | – | Rows to skip before this page (pagination). Default 0. |
| ticker | string | – | Case-insensitive exact ticker filter, e.g. DKS. |
No output schema declared.
No examples provided.
verify_13f_change Fact-check a 13F position-change claim against SEC Form 13F-HR ~298
Use when the user wants to verify or fact-check whether a fund (filer name/CIK) reported a CHANGE in a position in an issuer (issuer_name or cusip) in a quarter. Returns held (reported a change — opened/added/trimmed, with source filing + link), not_held (reported the position exited), not_found (no reported change — does NOT mean the fund didn't hold it), or out_of_coverage. Caveat: filing-verified; CANNOT confirm an unchanged holding (13F deltas only) — a 'held, unchanged' position produces no row.
| Name | Type | Req | Description |
|---|---|---|---|
| cusip | string | – | 9-char CUSIP of the held security — give this or issuer_name. (ticker is never accepted: 13F carries no authoritative ticker) |
| end | string | – | Quarter-window end (ISO) if the claim spans quarters |
| filer | string | – | Fund/institution name substring (case-insensitive, e.g. 'Berkshire') or exact filer CIK — REQUIRED |
| issuer_name | string | – | Held company/issuer name (e.g. 'Apple') — give this or cusip |
| quarter | string | – | As-of quarter-end the claim is about, ISO YYYY-MM-DD (e.g. '2026-06-30') |
| start | string | – | Quarter-window start (ISO) if the claim spans quarters |
No output schema declared.
No examples provided.
verify_8k_event Fact-check an 8-K disclosure claim against SEC Form 8-K ~296
Use when the user wants to verify or fact-check that a company filed an 8-K carrying specific SEC item code(s) in a timeframe. Pass registrant (cik/company/accession), item code(s) and dates. Returns confirmed (with source filing + link), not_found, partial (itemised claimed-vs-filed), out_of_scope (claims about the filing's meaning aren't covered — it is never paraphrased), or out_of_coverage. Caveat: filing-verified — item codes are the SEC controlled vocabulary parsed from the filing, never inferred.
| Name | Type | Req | Description |
|---|---|---|---|
| accession | string | – | SEC filing accession, e.g. 0001193125-26-389400 |
| cik | string | – | Registrant CIK (leading zeros ignored), e.g. 320193 |
| company_name | string | – | Registrant name substring (case-insensitive), e.g. 'Apple' |
| date | string | – | Claimed filing date, ISO YYYY-MM-DD (matched ±3 filing days) |
| end | string | – | Window end (ISO) if the claim is a range |
| items | string | – | Claimed SEC 8-K item code(s), comma-separated (e.g. '5.02' or '1.01,9.01') — checked against the filing |
| start | string | – | Window start (ISO) if the claim is a range |
No output schema declared.
No examples provided.
verify_activist_13d Fact-check an activist 13D claim against SEC Schedule 13D/13D-A ~320
Use when the user wants to verify or fact-check a claim about an activist stake or 13D filing (ticker/subject, filer, percent-of-class, stated intent, timeframe). Returns confirmed (with source filing + link), not_found, partial (itemised claimed-vs-filed), out_of_scope (passive 13G isn't covered), or out_of_coverage. Every response states the coverage window checked. Caveat: filing-verified — absence is reported as absence, never guessed.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Claimed filed date, ISO YYYY-MM-DD (matched ±3 filing days) |
| end | string | – | Window end (ISO) if the claim is a range |
| filer_name | string | – | Activist filer name in any order, e.g. 'Elliott Management' |
| form_type | string | – | Optional; only activist 13D/13D-A is covered — a passive 13G returns out_of_scope |
| intent | string | – | Optional pre-registered intent: I1 control/take-private, I2 board/proxy, I3 strategic/value |
| percent_of_class | number | – | Claimed percent-of-class owned (matched ±0.5 percentage points) |
| start | string | – | Window start (ISO) if the claim is a range |
| subject_name | string | – | Subject/target company name (use if you don't have the ticker) |
| ticker | string | – | Subject-company ticker (case-insensitive), e.g. DH |
No output schema declared.
No examples provided.
verify_insider_purchase Fact-check an insider-buying claim against SEC Form 4 ~392
Use when the user wants to verify a claim that an insider bought a stock, or to pull the purchases in one filing by accession. Pass the claim (ticker/issuer, person, amount, timeframe), or `accession` alone for that filing's gated purchase records. Returns confirmed, not_found, partial, out_of_scope (sales/options/grants), or out_of_coverage. Each matched filing carries `transaction_date`, `acceptance_datetime`, `aff10b5One` (10b5-1 flag), `is_amendment`/`original_accession` (4/A linkage), and `partial_fields` (reason for any null). Caveat: filing-verified — absence is reported, not guessed.
| Name | Type | Req | Description |
|---|---|---|---|
| accession | string | – | SEC filing accession, e.g. 0001493152-26-040454. If you already have the exact filing, pass this to pull its gated purchase records directly — it is used alone and ignores the claim fields above. |
| amount_usd | number | – | Claimed purchase value in USD (matched ±5% or ±$1) |
| date | string | – | Claimed date, ISO YYYY-MM-DD (matched ±3 filing days) |
| end | string | – | Window end (ISO) if the claim is a range |
| issuer_name | string | – | Issuer/company name (use if you don't have the ticker) |
| person | string | – | Insider name in any order, e.g. 'Alfonso de Angoitia' |
| shares | number | – | Claimed share count |
| start | string | – | Window start (ISO) if the claim is a range |
| ticker | string | – | Issuer ticker (case-insensitive), e.g. CAVA |
| txn_type | string | – | Optional; only code P purchases are covered — sale/option/grant returns out_of_scope |
No output schema declared.
No examples provided.
How do I install the TradeStar Insider MCP server?
TradeStar Insider is a hosted endpoint at https://mcp.tradestarinsider.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.tradestarinsider.com
claude mcp add --transport http com-tradestarinsider-edgar-insider-signals 'https://mcp.tradestarinsider.com/mcp'
What is the TradeStar Insider MCP server?
TradeStar Insider is an MCP server listed in the public MCP registry as com.tradestarinsider/edgar-insider-signals. Filing-verified SEC EDGAR insider (Form 4), 13D, 13F & 8-K data, no sign-in. Verify any claim. This page covers its hosted endpoint (https://mcp.tradestarinsider.com/mcp).
Is the TradeStar Insider MCP server safe to use?
TradeStar Insider scores 79 out of 100 on VerifyMCP. 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 TradeStar Insider MCP server expose?
TradeStar Insider exposes 10 tools: insider_buys, insider_cluster_buys, federal_awards_recent, activist_stakes_recent, fund_position_changes, and 5 more. Their descriptions and schemas cost roughly 3,299 tokens of context every time the server is loaded.
Does the TradeStar Insider MCP server require authentication?
No. We connected to TradeStar Insider without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TradeStar Insider MCP server still maintained?
TradeStar Insider is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TradeStar Insider MCP server?
VerifyMCP ran 13 checks on TradeStar Insider, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.