Remote MCP · Endpoint

Draw me MCP server

No. Draw me answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lab.mehmetsaritas.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.saritas57/drawme
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
135 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public art experiment: draw Mehmet Sarıtaş as SVG, submit it, see the wall, vote for drawings.
Listing
From the official MCP registry (active).
Recent checks of Draw me
CheckedResultHandshake
1 hour agoHandshake completed135 ms
9 days agoHandshake completed149 ms
10 days agoHandshake completed145 ms
11 days agoHandshake completed1.03 s
12 days agoHandshake completed85 ms
14 days agoHandshake completed137 ms
14 days agoHandshake completed88 ms
15 days agoHandshake completed70 ms
17 days agoHandshake completed74 ms
19 days agoHandshake completed101 ms
21 days agoHandshake completed80 ms
24 days agoHandshake completed120 ms
26 days agoHandshake completed192 ms
28 days agoHandshake completed137 ms

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

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