Skip to content

feeds MCP server

com.insidercable/feedsinsidercable.comstreamable-httpv0.3.0Scanned

Point-in-time Congress, BTC-ETF-flow, insider, token-launch and options-IV feeds; free + x402

7 tools: 7 change things.

Tools: 0 delete, 0 irreversible, 7 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the feeds MCP server can do

The feeds MCP server is published by insidercable.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (7 tools: congress_trades, etf_flows, insider_buys, insider_sells and 3 more), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 7Claude Code: ask
  • congress_tradesUS Congress stock transactions from official Senate ePTR and House Clerk disclosures (public domain).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • etf_flowsSpot bitcoin ETF creation/redemption flows, computed as change in shares outstanding times NAV so price moves are removed and only genuine creations/redemptions remain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • insider_buysSEC Form 4 open-market insider BUYS (public domain).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • insider_sellsSEC Form 4 open-market insider SELLS (public domain).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • launch_ledgerRobinhood 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • launch_walletsWallet 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 fi…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • options_ivDaily US equity option-chain structure per ticker, recorded forward from 2026-06-27 (~230 names, weekday close).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Daily US equity option-chain structure per ticker, recorded forward from 2026-06-27 (~230 names, weekday close). Derived metrics only -- no quotes, strikes, greeks or spot are re-served: atm_iv_30d / atm_iv_90d (implied vol at the ~30d and ~90d expiries), iv_term (30d/90d; above 1 = backwardation/stress), skew_25d (25-delta put IV minus call IV; positive = put demand), iv_rank (percentile of today's 30d IV within THIS series' own history, with iv_hist_days saying how long that history is -- a rank over 10 days is not a rank), put/call ratios by open interest and by volume, net dealer gamma sign, max-OI call/put strikes as percent from spot, and an unusual-activity read (uoa_lean call/put/mixed from contracts with volume >= 3x open interest; EOD delayed data, no prints, so buyer vs seller is unknowable). happened_at is the trading day; observed_at is the day the chain was banked. Not backfilled; the source publishes only the current chain, so nobody can reconstruct these days.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://insidercable.com/mcp: tools/list returned 7 tools to an anonymous client, including congress_trades (write), etf_flows (write), insider_buys (write), insider_sells (write), launch_ledger (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__feeds__congress_trades",
      "mcp__feeds__etf_flows",
      "mcp__feeds__insider_buys",
      "mcp__feeds__insider_sells",
      "mcp__feeds__launch_ledger",
      "mcp__feeds__launch_wallets",
      "mcp__feeds__options_iv"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as feeds. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.insidercable/feeds/verify?hash=a33ed4ce3a27541bd36ee386c6e30909391aa82c96cf81b2deae4ec78630e4cc" | jq -e '.changed == false'

Pinned hash a33ed4ce3a27, from Nov 13, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.insidercable/feeds/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.insidercable/feeds
[![Anlyon Radar](https://radar.anlyon.com/badge/com.insidercable/feeds.svg)](https://radar.anlyon.com/servers/com.insidercable/feeds)

Source: MCP Registry. Synced Oct 21, 2026, 17:56 UTC.

feeds MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the feeds MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the feeds MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the feeds MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the feeds MCP server have?

7 tools: 7 write. congress_trades, etf_flows, insider_buys, insider_sells, launch_ledger, launch_wallets and options_iv.

Does the feeds MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the feeds MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the feeds MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.