Remote MCP · Endpoint
SCRIPTMASTERLABS — SML ticker-research MCP server
Yes, as of 1 hour ago: the request timed out.
DownLast checked 1 hour ago
Server URL
https://sml-ticker-research.onrender.com/mcp
The last check failed: the request timed out.
- Registry name
- com.scriptmasterlabs/ticker-research
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- One cheap, loopable answer per call for a US ticker: market regime, trend + strength, key levels, ne
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the request timed out | — |
| 13 hours ago | Handshake completed | 584 ms |
| 2 days ago | Handshake completed | 331 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 3.
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 SCRIPTMASTERLABS — SML ticker-research and makes no claim about it beyond what these checks measured.