Remote MCP · Endpoint

StockDrifts MCP server

No. StockDrifts answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

https://mcp.stockdrifts.io/mcp/

The last check completed an MCP handshake.

Registry name
io.stockdrifts/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
324 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Rated 13F funds with average buy prices, company KPIs, Japan investor ratings, Korea insider buys.
Listing
From the official MCP registry (active).
Recent checks of StockDrifts
CheckedResultHandshake
55 minutes agoHandshake completed324 ms
1 day agoHandshake completed320 ms
4 days agoHandshake completed318 ms
7 days agoHandshake completed319 ms
9 days agoHandshake completed324 ms
11 days agoHandshake completed341 ms
13 days agoHandshake completed319 ms
15 days agoHandshake completed314 ms
17 days agoHandshake completed328 ms
19 days agoHandshake completed364 ms
21 days agoHandshake completed314 ms
22 days agoHandshake completed349 ms
23 days agoHandshake completed312 ms
24 days agoHandshake completed316 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 StockDrifts and makes no claim about it beyond what these checks measured.