Remote MCP · Endpoint

Swatch Ledger MCP server

No. Swatch Ledger answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://swatch-ledger.pages.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Keith-CY/swatch-ledger-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
127 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Fabric shrinkage from a swatch wash test, and how much fabric to buy before washing.
Listing
From the official MCP registry (active).
Recent checks of Swatch Ledger
CheckedResultHandshake
37 minutes agoHandshake completed127 ms
4 days agoHandshake completed72 ms
7 days agoHandshake completed85 ms
16 days agoHandshake completed128 ms
16 days agoHandshake completed80 ms
18 days agoHandshake completed81 ms
19 days agoHandshake completed124 ms
20 days agoHandshake completed162 ms
21 days agoHandshake completed86 ms
22 days agoHandshake completed89 ms
23 days agoHandshake completed156 ms
26 days agoHandshake completed99 ms

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

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