Remote MCP · Endpoint

Tonebook Palette MCP server

No. Tonebook Palette answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://tonebook-muse-mcp-staging.vercel.app/api/openai-mcp-v1

The last check completed an MCP handshake.

Registry name
app.tonebook/palette
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
110 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Choose a palette, compare digital colors and create portable outfit, event or packing boards.
Listing
From the official MCP registry (active).
Recent checks of Tonebook Palette
CheckedResultHandshake
40 minutes agoHandshake completed110 ms
3 days agoHandshake completed538 ms
12 days agoHandshake completed109 ms
12 days agoHandshake completed102 ms
14 days agoHandshake completed70 ms
15 days agoHandshake completed80 ms
16 days agoHandshake completed77 ms
17 days agoHandshake completed64 ms
18 days agoHandshake completed66 ms
19 days agoHandshake completed75 ms
22 days agoHandshake completed75 ms
25 days agoHandshake completed217 ms
27 days agoHandshake completed96 ms
29 days agoHandshake completed64 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 Tonebook Palette and makes no claim about it beyond what these checks measured.