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.
Listing
From the official MCP registry (active).
Recent checks of ai.tickerscout/ticker-scout
CheckedResultHandshake
1 hour agoHandshake completed264 ms
10 hours agoHandshake completed549 ms
1 day agoHandshake completed134 ms
2 days agoHandshake completed226 ms
4 days agoHandshake completed205 ms
4 days agoHandshake completed211 ms
5 days agoHandshake completed209 ms
6 days agoHandshake completed185 ms
8 days agoHandshake completed422 ms
11 days agoHandshake completed46 ms
13 days agoHandshake completed90 ms
16 days agoHandshake completed206 ms
18 days agoHandshake completed215 ms
20 days agoHandshake completed267 ms
22 days agoHandshake completed196 ms
24 days agoHandshake completed248 ms
26 days agoHandshake completed54 ms
27 days agoHandshake completed42 ms
29 days agoHandshake completed60 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.