Remote MCP · Endpoint

Signal8 MCP server

No. Signal8 answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.signal8.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.signal8/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
167 ms
Tools exposed
108 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Signal8
CheckedResultHandshake
6 hours agoHandshake completed167 ms
2 days agoHandshake completed161 ms
4 days agoHandshake completed530 ms
5 days agoHandshake completed155 ms
7 days agoHandshake completed159 ms
8 days agoHandshake completed164 ms
9 days agoHandshake completed161 ms
12 days agoHandshake completed5.69 s
13 days agoHandshake completed150 ms
15 days agoHandshake completed544 ms
16 days agoHandshake completed146 ms
17 days agoHandshake completed144 ms
18 days agoHandshake completed156 ms
19 days agoHandshake completed373 ms
20 days agoHandshake completed162 ms
21 days agoHandshake completed518 ms
23 days agoHandshake completed491 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.

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