Remote MCP · Endpoint

PickShade color tools MCP server

No. PickShade color tools answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://pickshade.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.pickshade/pickshade
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
665 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
18 color tools: OKLCH, WCAG and APCA contrast fixes, palettes, gradients, color blindness, tokens.
Listing
From the official MCP registry (active).
Recent checks of PickShade color tools
CheckedResultHandshake
10 hours agoHandshake completed665 ms
3 days agoHandshake completed579 ms
12 days agoHandshake completed588 ms
13 days agoHandshake completed610 ms
14 days agoHandshake completed600 ms
15 days agoHandshake completed742 ms
16 days agoHandshake completed634 ms
17 days agoHandshake completed683 ms
18 days agoHandshake completed606 ms
20 days agoHandshake completed578 ms
22 days agoHandshake completed576 ms
25 days agoHandshake completed591 ms
27 days agoHandshake completed517 ms
30 days agoHandshake completed641 ms

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

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