Remote MCP · Endpoint

Flood Design System MCP server

No. Flood Design System answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://flood.md/mcp

The last check completed an MCP handshake.

Registry name
io.github.tillwithered/flood
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
192 ms
Tools exposed
3 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Find Flood UI components, recipes, tokens, and design skills for coding agents.
Listing
From the official MCP registry (active).
Recent checks of Flood Design System
CheckedResultHandshake
36 minutes agoHandshake completed192 ms
4 days agoHandshake completed283 ms
7 days agoHandshake completed170 ms

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

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