Remote MCP · Endpoint

Tailwind Shades MCP server

No. Tailwind Shades answered an MCP handshake 26 minutes ago.

UpLast checked 26 minutes ago

Server URL

https://tailwindshades.bourhaouta.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.bourhaouta/tailwindshades
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Tailwind CSS palettes (50-950) from any color, the closest Tailwind color, and Tailwind's defaults
Listing
From the official MCP registry (active).
Recent checks of Tailwind Shades
CheckedResultHandshake
26 minutes agoHandshake completed67 ms
10 days agoHandshake completed107 ms
11 days agoHandshake completed103 ms
12 days agoHandshake completed89 ms
13 days agoHandshake completed79 ms
14 days agoHandshake completed124 ms
15 days agoHandshake completed1.09 s
16 days agoHandshake completed1.14 s
17 days agoHandshake completed132 ms
19 days agoHandshake completed213 ms
22 days agoHandshake completed955 ms
24 days agoHandshake completed238 ms
26 days agoHandshake completed120 ms
29 days agoHandshake completed81 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 Tailwind Shades and makes no claim about it beyond what these checks measured.