Remote MCP · Endpoint

sysketch MCP server

No. sysketch answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://sysketch.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.Tonys-Coding/sysketch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.86 s
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Polished system design diagrams (SVG/PNG) from a tiny YAML spec, ~18x fewer tokens than raw SVG.
Listing
From the official MCP registry (active).
Recent checks of sysketch
CheckedResultHandshake
4 days agoHandshake completed1.86 s
4 days agoHandshake completed308 ms
5 days agoHandshake completed98 ms
6 days agoHandshake completed1.85 s
8 days agoHandshake completed79 ms
8 days agoHandshake completed1.89 s
9 days agoHandshake completed2.15 s
10 days agoHandshake completed100 ms
12 days agoHandshake completed126 ms
15 days agoHandshake completed64 ms
17 days agoHandshake completed1.38 s
20 days agoHandshake completed67 ms
22 days agoHandshake completed1.20 s
24 days agoHandshake completed206 ms

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