Remote MCP · Endpoint

Tideline MCP server

No. Tideline answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://tideline.jbpscapital.com/mcp

The last check completed an MCP handshake.

Registry name
com.jbpscapital.tideline/tideline
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
96 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Published end-of-day state of a rules-based SPY/QQQ index model. Read-only. Free tier: 30-day delay.
Listing
From the official MCP registry (active).
Recent checks of Tideline
CheckedResultHandshake
2 hours agoHandshake completed96 ms
2 days agoHandshake completed203 ms
4 days agoHandshake completed67 ms
5 days agoHandshake completed63 ms
7 days agoHandshake completed120 ms
8 days agoHandshake completed344 ms
9 days agoHandshake completed51 ms
12 days agoHandshake completed47 ms
14 days agoHandshake completed45 ms
15 days agoHandshake completed64 ms
17 days agoHandshake completed70 ms
18 days agoHandshake completed31 ms
19 days agoHandshake completed54 ms
20 days agoHandshake completed58 ms
20 days agoHandshake completed52 ms
21 days agoHandshake completed77 ms

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

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