Remote MCP · Endpoint

Claycut MCP server

No. Claycut answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://claycut.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.vincentzhang15/claycut
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
51 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Custom transparent PNG icons in your project's style, added by your coding agent. Free starter set.
Website
https://claycut.dev/
Listing
From the official MCP registry (active).
Recent checks of Claycut
CheckedResultHandshake
5 hours agoHandshake completed51 ms
9 days agoHandshake completed99 ms
10 days agoHandshake completed42 ms
11 days agoHandshake completed80 ms
12 days agoHandshake completed64 ms
14 days agoHandshake completed69 ms
14 days agoHandshake completed85 ms
15 days agoHandshake completed158 ms
17 days agoHandshake completed92 ms
19 days agoHandshake completed66 ms
21 days agoHandshake completed71 ms
24 days agoHandshake completed115 ms
26 days agoHandshake completed97 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Claycut and makes no claim about it beyond what these checks measured.