Remote MCP · Endpoint
Boolsai Signals MCP server
Yes, as of 10 hours ago: the hostname does not resolve.
DownLast checked 10 hours ago
Server URL
https://signals.boolsai.ai/mcp
The last check failed: the hostname does not resolve.
- Registry name
- ai.boolsai/signals
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 29.4% from 17 checks
- Described by its publisher as
- Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools.
- Repository
- https://github.com/Boolsai-ai/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 10 hours ago | Failed - the hostname does not resolve | — |
| 2 days ago | Failed - the hostname does not resolve | — |
| 4 days ago | Failed - the hostname does not resolve | — |
| 5 days ago | Failed - the hostname does not resolve | — |
| 7 days ago | Failed - the hostname does not resolve | — |
| 8 days ago | Failed - the hostname does not resolve | — |
| 9 days ago | Failed - the hostname does not resolve | — |
| 12 days ago | Failed - the hostname does not resolve | — |
| 13 days ago | Failed - the hostname does not resolve | — |
| 15 days ago | Failed - the hostname does not resolve | — |
| 16 days ago | Failed - the hostname does not resolve | — |
| 17 days ago | Failed - the hostname does not resolve | — |
| 18 days ago | Handshake completed | 59 ms |
| 19 days ago | Handshake completed | 47 ms |
| 20 days ago | Handshake completed | 47 ms |
| 21 days ago | Handshake completed | 43 ms |
| 23 days ago | Handshake completed | 66 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 5 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 Boolsai Signals and makes no claim about it beyond what these checks measured.