# com.insidercable/feeds (remote · insidercable.com)

Congress trades, BTC ETF flows, SEC Form 4 insiders — every record says when we first saw it

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `insidercable.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-insidercable-feeds/insidercable.md), [page](https://verifymcp.io/servers/com-insidercable-feeds/insidercable)

## Channel facts

- Endpoint: `https://insidercable.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-insidercable-feeds 'https://insidercable.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-insidercable-feeds": {
      "url": "https://insidercable.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-insidercable-feeds": {
      "type": "http",
      "url": "https://insidercable.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-insidercable-feeds]
url = "https://insidercable.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-insidercable-feeds": {
      "type": "remote",
      "url": "https://insidercable.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-insidercable-feeds --url 'https://insidercable.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-insidercable-feeds:
    url: "https://insidercable.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-insidercable-feeds": {
      "Transport": "http",
      "Url": "https://insidercable.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-insidercable-feeds -t streamable-http -u 'https://insidercable.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 63, +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.

### 2026-09-16 (score 62, +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.

### 2026-09-14 (score 61, +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.

### 2026-09-12 (score 60, +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.

### 2026-09-10 (score 59, +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.

### 2026-09-08 (score 58, +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.

### 2026-09-07 (score 57, 0)

- [security] 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
- [functional regression] Schema quality: 127 → 186
- [functional improvement] Tool coverage: 75% → 88%
- [functional] New tool “launch_ledger”
- [functional] New tool “launch_wallets”
- [cosmetic] “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”

### 2026-09-05 (score 57, +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.

## MCP tools (6)

### `congress_trades` (~146 tokens)

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.

Input parameters:

- `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

### `etf_flows` (~111 tokens)

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.

Input parameters:

- `since` (string): Only rows on/after this YYYY-MM-DD
- `ticker` (string): Fund ticker, e.g. IBIT

### `insider_buys` (~215 tokens)

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.

Input parameters:

- `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)

### `insider_sells` (~196 tokens)

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.

Input parameters:

- `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)

### `launch_ledger` (~262 tokens)

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.

Input parameters:

- `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

### `launch_wallets` (~191 tokens)

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.

Input parameters:

- `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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-insidercable-feeds/insidercable#diagnostics

## Score history

- 2026-09-20: 63
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 61
- 2026-09-14: 61
- 2026-09-13: 60
- 2026-09-12: 60
- 2026-09-11: 59
- 2026-09-10: 59
- 2026-09-09: 58
- 2026-09-08: 58
- 2026-09-07: 57
- 2026-09-06: 57
- 2026-09-05: 57
- 2026-09-04: 56
- 2026-09-03: 56
- 2026-09-02: 55
- 2026-09-01: 55

## Common questions

### 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.

## Links

- Remote endpoint: https://insidercable.com/mcp
- Website: https://insidercable.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-insidercable-feeds/insidercable.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-insidercable-feeds/insidercable.json
- HTML version of this page: https://verifymcp.io/servers/com-insidercable-feeds/insidercable