Insidewell
REMOTE · INSIDEWELL-API.CYBERMAXTOOLS.COM
Insider trading API + MCP: SEC Form 4 buys/sells, cluster buys. Keys $19/mo; 100 free/day.
Available components
Last scanned (3 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 25 Oct 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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 583 tokens (~194/item across 3 items; 3 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 71
First indexed and scored.
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 25 Oct 2026 · Probed https://insidewell-api.cybermaxtools.com/mcp?via=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cybermaxtools.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2981f99f560709fc0e9649b951b52242 |
| SANs: cybermaxtools.com, insidewell-api.cybermaxtools.com, *.insidewell-api.cybermaxtools.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 insidewell-api.cybermaxtools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cybermaxtools.com. | absent | 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://insidewell-api.cybermaxtools.com/mcp?via=mcp-registry | Verified | 200 | |
| http (plaintext) | http://insidewell-api.cybermaxtools.com/mcp?via=mcp-registry | HTTPS enforced | 301 | https://insidewell-api.cybermaxtools.com/mcp?via=mcp-registry |
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 →
cluster_buys Insider cluster buys ~152
Companies where 2+ different insiders bought the stock on the open market within 7 days (window, minimum insiders and minimum dollars adjustable), with each insider, total dollars and filing links.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back N days of filings (1-45) |
| limit | integer | – | Clusters (1-100) |
| minInsiders | integer | – | Distinct insiders buying (2-10) |
| minValue | number | – | Only clusters whose buys add up to at least this many US dollars |
| ticker | string | – | Only these tickers (comma separated) |
| window | integer | – | Buys must fall within this many days of each other (1-30) |
No output schema declared.
No examples provided.
data_status Data freshness ~28
When Insidewell last pulled new Form 4 filings from EDGAR and which filed dates it covers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
insider_trades Latest insider trades (SEC Form 4) ~323
Latest insider transactions from SEC Form 4 filings (EDGAR, refreshed about once a minute), newest filed first, up to 100 rows: ticker, insider, role, code (P buy, S sale, ...), shares, price, dollar value, dates and the filing link. Defaults to open-market buys and sales filed in the last 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Transaction codes: P = open-market buy, S = sale (default P,S); also A (grant), M (option exercise), F (tax withholding), G (gift) ... or all |
| days | integer | – | Filed in the last N days when no from date is given (1-45) |
| from | string | – | Trade date from (YYYY-MM-DD) |
| insider | string | – | Insider name (part of it, e.g. musk) or their SEC CIK number |
| limit | integer | – | Rows (1-100) |
| minValue | number | – | Only trades worth at least this many US dollars (shares × price) |
| offset | integer | – | Skip rows (paging, up to 2000) |
| plan | string | – | Rule 10b5-1 trading plans: exclude (only discretionary trades) or only |
| role | string | – | director, officer or ten_percent_owner |
| ticker | string | – | One ticker or up to 25, comma separated (e.g. NVDA,AAPL). Empty = every company |
| to | string | – | Trade date to (YYYY-MM-DD) |
No output schema declared.
No examples provided.
How do I install the Insidewell MCP server?
Insidewell is a hosted endpoint at https://insidewell-api.cybermaxtools.com/mcp?via=mcp-registry, 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 · insidewell-api.cybermaxtools.com
claude mcp add --transport http dev-workers-cybermax-tools-cybermax-insidewell-a 'https://insidewell-api.cybermaxtools.com/mcp?via=mcp-registry'
What is the Insidewell MCP server?
Insidewell is an MCP server listed in the public MCP registry as dev.workers.cybermax-tools.cybermax/insidewell-api. Insider trading API + MCP: SEC Form 4 buys/sells, cluster buys. Keys $19/mo; 100 free/day. This page covers its hosted endpoint (https://insidewell-api.cybermaxtools.com/mcp?via=mcp-registry).
Is the Insidewell MCP server safe to use?
Insidewell scores 78 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 Insidewell MCP server expose?
Insidewell exposes 3 tools: insider_trades, cluster_buys, data_status. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.
Does the Insidewell MCP server require authentication?
No. We connected to Insidewell without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Insidewell MCP server still maintained?
Insidewell is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.