com.insidercable/feeds
REMOTE · INSIDERCABLE.COM · SCANNED SEP 20
Congress trades, BTC ETF flows, SEC Form 4 insiders — every record says when we first saw it
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1121 tokens (~186/item across 6 items; 6 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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.insidercable/feeds MCP server?
com.insidercable/feeds is a hosted endpoint at https://insidercable.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 · insidercable.com
claude mcp add --transport http com-insidercable-feeds 'https://insidercable.com/mcp'
{
"mcpServers": {
"com-insidercable-feeds": {
"url": "https://insidercable.com/mcp"
}
}
} {
"servers": {
"com-insidercable-feeds": {
"type": "http",
"url": "https://insidercable.com/mcp"
}
}
} [mcp_servers.com-insidercable-feeds] url = "https://insidercable.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-insidercable-feeds": {
"type": "remote",
"url": "https://insidercable.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-insidercable-feeds --url 'https://insidercable.com/mcp' --transport streamable-http
mcp_servers:
com-insidercable-feeds:
url: "https://insidercable.com/mcp" {
"McpServers": {
"com-insidercable-feeds": {
"Transport": "http",
"Url": "https://insidercable.com/mcp"
}
}
} assistant mcp add com-insidercable-feeds -t streamable-http -u 'https://insidercable.com/mcp'
{
"mcpServers": {
"com-insidercable-feeds": {
"type": "http",
"url": "https://insidercable.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 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.
- 14 Sept 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.
- 12 Sept 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.
- 10 Sept 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.
- 8 Sept 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.
- 7 Sept 26 0
- Tool “insider_buys” rewrote its description, which is the text the model reads security
- Tool “insider_sells” rewrote its description, which is the text the model reads security
- Schema quality: 127 → 186 ▼ functional
- Tool coverage: 75% → 88% ▲ functional
- New tool “launch_ledger” functional
- New tool “launch_wallets” functional
- “insider_buys” added an optional parameter “form” cosmetic
- “insider_sells” added an optional parameter “form” cosmetic
- “insider_buys” reworded the description of “min_value” cosmetic
- “insider_sells” reworded the description of “min_value” cosmetic
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://insidercable.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=insidercable.com | CN=WE1,O=Google Trust Services,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ae2bf13ed78dd5dc13cddd8f3a871b3c |
| SANs: insidercable.com, www.insidercable.com, *.www.insidercable.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 insidercable.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| insidercable.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://insidercable.com/mcp | Verified | 200 | |
| http (plaintext) | http://insidercable.com/mcp | Inconclusive | 405 |
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 →
congress_trades ~146
US Congress stock transactions from official Senate ePTR and House Clerk disclosures (public domain). Every record carries happened_at (transaction date), disclosed_at (filing date) and observed_at (when this pipeline first saw it). Because the STOCK Act permits ~45 days between trade and disclosure, disclosed_at is the field to use for point-in-time work. Senate data is parsed to ticker level; House filings are metadata only.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | – | – |
| name | string | – | Substring match on member name |
| since | string | – | Only transactions on/after this YYYY-MM-DD |
| ticker | string | – | Filter to one ticker, e.g. NVDA |
No output schema declared.
No examples provided.
etf_flows ~111
Spot bitcoin ETF creation/redemption flows, computed as change in shares outstanding times NAV so price moves are removed and only genuine creations/redemptions remain. This series cannot be backfilled -- the issuer publishes only a current snapshot -- so every row was banked on the day it existed. span_days above 1 marks a row that spans a gap.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Only rows on/after this YYYY-MM-DD |
| ticker | string | – | Fund ticker, e.g. IBIT |
No output schema declared.
No examples provided.
insider_buys ~215
SEC Form 4 open-market insider BUYS (public domain). Form-4 code P only: grants, option exercises, tax withholding and gifts are excluded because they are compensation events rather than conviction. An officer or director spending their own money is the signal this feed isolates. Carries observed_at (when recorded here) and happened_at (transaction date on the filing). For disposals use insider_sells. Since 2026-09-01 the feed also carries Schedule 13D/13G beneficial-ownership stakes (form=13D active intent, form=13G passive; direction=buy on an initial filing or a percent increase versus the last filing seen); filter with form=4 for Form 4 only.
| Name | Type | Req | Description |
|---|---|---|---|
| form | string | – | SEC form; omit for all |
| min_value | number | – | Minimum transaction value in USD (Form 4 rows only carry a value) |
| since | string | – | Only transactions on/after this YYYY-MM-DD |
| ticker | string | – | – |
No output schema declared.
No examples provided.
insider_sells ~196
SEC Form 4 open-market insider SELLS (public domain). Form-4 code S only. Read these with care: insiders sell for diversification, tax and pre-scheduled 10b5-1 plans, so a sale carries far less information than a purchase. Carries observed_at (when recorded here) and happened_at (transaction date on the filing). For acquisitions use insider_buys. Also carries Schedule 13D/13G stake DECREASES and exits below 5% (form=13D|13G, direction=sell versus the last filing seen); filter with form=4 for Form 4 only.
| Name | Type | Req | Description |
|---|---|---|---|
| form | string | – | SEC form; omit for all |
| min_value | number | – | Minimum transaction value in USD (Form 4 rows only carry a value) |
| since | string | – | Only transactions on/after this YYYY-MM-DD |
| ticker | string | – | – |
No output schema declared.
No examples provided.
launch_ledger ~262
Robinhood Chain (chain id 4663) token launches that cleared a first-hour activity floor, with the early-buyer cohort: the first ~25 distinct wallets that bought (transaction sender, never the router), each with block delta from launch and quote spent. Every launch is graded at 24h and 7d (price multiple vs first buy, liquidity, holders). Launchpad is identified from the Uniswap v4 hook. Recorded forward from 2026-09-03 straight from chain logs: happened_at is the launch block time, observed_at is when the cohort was banked. Not backfilled.
| Name | Type | Req | Description |
|---|---|---|---|
| launchpad | string | – | Substring match, e.g. doppler, launchhook, none |
| min_buyers | number | – | Minimum distinct early buyers captured |
| min_usd | number | – | Minimum first-hour buy volume, USD estimate |
| quote | string | – | Quote asset: ETH, WETH, USDG, or a stock token symbol |
| since | string | – | Only launches on/after this YYYY-MM-DD |
| ticker | string | – | Token symbol as the deployer named it (untrusted text) |
| wallet | string | – | Launches this address was early in, or deployed |
No output schema declared.
No examples provided.
launch_wallets ~191
Wallet book derived from launch_ledger: every address seen in an early-buyer cohort, with how many launches it was early in, its 24h hit rate (launch traded at 2x or more vs its first buy), dead rate (no trades or below 0.2x), average block delta, launchpads used, tokens, and whether it also deployed launches. Repeat early buyers with a high hit rate are the cohort worth watching; this feed ranks, it does not recommend. Recomputed at each publish from the forward-only ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| launchpad | string | – | Wallets active on this launchpad |
| min_launches | number | – | Minimum launches early in |
| since | string | – | Wallets last seen on/after this YYYY-MM-DD |
| ticker | string | – | Wallets that were early in this token symbol |
| wallet | string | – | One address |
No output schema declared.
No examples provided.
What is the com.insidercable/feeds MCP server?
com.insidercable/feeds is an MCP server listed in the public MCP registry as com.insidercable/feeds. Congress trades, BTC ETF flows, SEC Form 4 insiders, every record says when we first saw it. This page covers its hosted endpoint (https://insidercable.com/mcp).
Is the com.insidercable/feeds MCP server safe to use?
com.insidercable/feeds scores 63 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 com.insidercable/feeds MCP server expose?
com.insidercable/feeds exposes 6 tools: congress_trades, etf_flows, insider_buys, insider_sells, launch_ledger, launch_wallets. Their descriptions and schemas cost roughly 1,121 tokens of context every time the server is loaded.
Does the com.insidercable/feeds MCP server require authentication?
No. We connected to com.insidercable/feeds without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.insidercable/feeds MCP server still maintained?
com.insidercable/feeds is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.