Remote MCP · Endpoint

esyURL MCP server

No. esyURL answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://esyurl.fyi/mcp

The last check completed an MCP handshake.

Registry name
io.github.esyurl/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
301 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Short links and trackable QR codes: editable after printing, device routing, scan stats.
Listing
From the official MCP registry (active).
Recent checks of esyURL
CheckedResultHandshake
1 hour agoHandshake completed301 ms
13 hours agoHandshake completed289 ms
2 days agoHandshake completed543 ms
4 days agoHandshake completed293 ms
6 days agoHandshake completed629 ms
9 days agoHandshake completed478 ms
11 days agoHandshake completed425 ms
13 days agoHandshake completed377 ms
15 days agoHandshake completed266 ms
17 days agoHandshake completed231 ms
19 days agoHandshake completed226 ms
21 days agoHandshake completed208 ms
23 days agoHandshake completed56 ms
24 days agoCredentials required—

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