Remote MCP · Endpoint

Ryan Lindsey MCP server

No. Ryan Lindsey answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.ryanlindsey.me/mcp

The last check completed an MCP handshake.

Registry name
me.ryanlindsey/ryanlindsey-me
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
199 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Ryan Lindsey's professional corpus, exposed as MCP tools.
Listing
From the official MCP registry (active).
Recent checks of Ryan Lindsey
CheckedResultHandshake
1 hour agoHandshake completed199 ms
2 days agoHandshake completed137 ms
4 days agoHandshake completed133 ms
5 days agoHandshake completed168 ms
7 days agoHandshake completed181 ms
8 days agoHandshake completed247 ms
9 days agoHandshake completed190 ms
12 days agoHandshake completed188 ms
13 days agoHandshake completed178 ms
15 days agoHandshake completed185 ms
17 days agoHandshake completed167 ms
18 days agoHandshake completed134 ms
19 days agoHandshake completed150 ms
20 days agoHandshake completed59 ms
21 days agoHandshake completed239 ms
21 days agoHandshake completed201 ms
23 days agoHandshake completed146 ms

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

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