Remote MCP · Endpoint

Overflow Design MCP server

No. Overflow Design answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://www.overflow.design/api/mcp/

The last check completed an MCP handshake.

Registry name
design.overflow/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
740 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and fetch hand-drawn icons, illustrations and isometric drawings. The free set needs no key.
Listing
From the official MCP registry (active).
Recent checks of Overflow Design
CheckedResultHandshake
6 hours agoHandshake completed740 ms
9 days agoHandshake completed1.04 s
10 days agoHandshake completed1.76 s
11 days agoHandshake completed1.73 s
12 days agoHandshake completed83 ms
14 days agoHandshake completed115 ms
14 days agoHandshake completed1.71 s
15 days agoHandshake completed252 ms
17 days agoHandshake completed1.16 s
19 days agoHandshake completed1.71 s
22 days agoHandshake completed1.28 s
24 days agoHandshake completed159 ms
26 days agoHandshake completed857 ms
28 days agoHandshake completed792 ms

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

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