Remote MCP · Endpoint

Versyka MCP server

No. Versyka answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://www.versyka.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.versyka/versyka
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find retiring AI models and outdated API SDKs in your code, with dates, replacements and guides.
Listing
From the official MCP registry (active).
Recent checks of Versyka
CheckedResultHandshake
53 minutes agoHandshake completed67 ms
3 days agoHandshake completed91 ms
12 days agoHandshake completed198 ms
13 days agoHandshake completed251 ms
15 days agoHandshake completed792 ms
15 days agoHandshake completed87 ms
17 days agoHandshake completed118 ms
18 days agoHandshake completed79 ms
18 days agoHandshake completed91 ms
20 days agoHandshake completed226 ms
22 days agoHandshake completed128 ms
25 days agoHandshake completed691 ms
27 days agoHandshake completed812 ms
29 days agoHandshake completed375 ms

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