Remote MCP · Endpoint

com.insidercable/feeds MCP server

No. com.insidercable/feeds answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://insidercable.com/mcp

The last check completed an MCP handshake.

Registry name
com.insidercable/feeds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Point-in-time Congress, BTC-ETF-flow, insider, token-launch and options-IV feeds; free + x402
Website
https://insidercable.com/
Listing
From the official MCP registry (active).
Recent checks of com.insidercable/feeds
CheckedResultHandshake
1 hour agoHandshake completed59 ms
2 days agoHandshake completed78 ms
4 days agoHandshake completed64 ms
5 days agoHandshake completed79 ms
7 days agoHandshake completed65 ms
8 days agoHandshake completed294 ms
9 days agoHandshake completed75 ms
12 days agoHandshake completed54 ms
13 days agoHandshake completed95 ms
15 days agoHandshake completed134 ms
16 days agoHandshake completed57 ms
17 days agoHandshake completed41 ms
18 days agoHandshake completed52 ms
19 days agoHandshake completed56 ms
20 days agoHandshake completed54 ms
21 days agoHandshake completed88 ms
22 days agoHandshake completed48 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.insidercable/feeds and makes no claim about it beyond what these checks measured.