Remote MCP · Endpoint
ai.tickerscout/ticker-scout MCP server
No. ai.tickerscout/ticker-scout answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.tickerscout.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.tickerscout/ticker-scout
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 264 ms
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Agent-native SEC data, 20 tools: statements assembled, any line item, filings synthesized. No key.
- Website
- https://tickerscout.ai/mcp/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 264 ms |
| 10 hours ago | Handshake completed | 549 ms |
| 1 day ago | Handshake completed | 134 ms |
| 2 days ago | Handshake completed | 226 ms |
| 4 days ago | Handshake completed | 205 ms |
| 4 days ago | Handshake completed | 211 ms |
| 5 days ago | Handshake completed | 209 ms |
| 6 days ago | Handshake completed | 185 ms |
| 8 days ago | Handshake completed | 422 ms |
| 11 days ago | Handshake completed | 46 ms |
| 13 days ago | Handshake completed | 90 ms |
| 16 days ago | Handshake completed | 206 ms |
| 18 days ago | Handshake completed | 215 ms |
| 20 days ago | Handshake completed | 267 ms |
| 22 days ago | Handshake completed | 196 ms |
| 24 days ago | Handshake completed | 248 ms |
| 26 days ago | Handshake completed | 54 ms |
| 27 days ago | Handshake completed | 42 ms |
| 29 days ago | Handshake completed | 60 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 ai.tickerscout/ticker-scout and makes no claim about it beyond what these checks measured.