Remote MCP · Endpoint

Yank MCP server

No. Yank answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://yank.info/api/mcp

The last check completed an MCP handshake.

Registry name
info.yank/yank
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
107 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Five sourced lines from a video, podcast, article or PDF, and a check that a quote is in its source
Listing
From the official MCP registry (active).
Recent checks of Yank
CheckedResultHandshake
3 hours agoHandshake completed107 ms
2 days agoHandshake completed89 ms
4 days agoHandshake completed208 ms
6 days agoHandshake completed65 ms
8 days agoHandshake completed67 ms
10 days agoHandshake completed57 ms
11 days agoHandshake completed74 ms
13 days agoHandshake completed66 ms
13 days agoHandshake completed76 ms
16 days agoHandshake completed92 ms
18 days agoHandshake completed99 ms
19 days agoHandshake completed130 ms
21 days agoHandshake completed112 ms
22 days agoHandshake completed66 ms
23 days agoHandshake completed131 ms

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

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