Remote MCP · Endpoint

com.insidergraph/insidergraph MCP server

Yes, as of 1 hour ago: the connection was refused or dropped.

DownLast checked 1 hour ago

Server URL

https://api.insidergraph.com/mcp

The last check failed: the connection was refused or dropped.

Registry name
com.insidergraph/insidergraph
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
42.1% from 19 checks
Described by its publisher as
SEC insider intelligence: trades, 8-K events, planned sales, activist stakes - one entity graph.
Website
https://insidergraph.com/
Listing
From the official MCP registry (active).
Recent checks of com.insidergraph/insidergraph
CheckedResultHandshake
1 hour agoFailed - the connection was refused or dropped—
18 hours agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—
3 days agoFailed - the connection was refused or dropped—
4 days agoFailed - the connection was refused or dropped—
5 days agoFailed - the connection was refused or dropped—
6 days agoFailed - the connection was refused or dropped—
7 days agoFailed - the connection was refused or dropped—
10 days agoFailed - the connection was refused or dropped—
13 days agoFailed - the connection was refused or dropped—
15 days agoFailed - the connection was refused or dropped—
17 days agoHandshake completed44 ms
19 days agoHandshake completed38 ms
21 days agoHandshake completed36 ms
23 days agoHandshake completed39 ms
25 days agoHandshake completed43 ms
27 days agoHandshake completed137 ms
28 days agoHandshake completed65 ms
29 days agoHandshake completed35 ms

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

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.insidergraph/insidergraph and makes no claim about it beyond what these checks measured.