Remote MCP · Endpoint

SVG Lab MCP server

No. SVG Lab answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://svglab.app/mcp/agents

The last check completed an MCP handshake.

Registry name
app.svglab/svglab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.24 s
Tools exposed
90 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
SVG Lab MCP: the Design Engine for AI. App screens, icons, illustrations and charts as SVG.
Listing
From the official MCP registry (active).
Recent checks of SVG Lab
CheckedResultHandshake
3 hours agoHandshake completed1.24 s
9 days agoHandshake completed1.25 s
10 days agoHandshake completed1.46 s
11 days agoHandshake completed1.10 s
12 days agoHandshake completed764 ms
14 days agoHandshake completed1.73 s
14 days agoHandshake completed828 ms
15 days agoHandshake completed1.21 s
17 days agoHandshake completed930 ms
19 days agoHandshake completed798 ms
21 days agoHandshake completed937 ms
24 days agoHandshake completed933 ms
26 days agoHandshake completed743 ms
28 days agoHandshake completed1.14 s

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