Remote MCP · Endpoint

Tonebook Palette MCP server

No. Tonebook Palette answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
75 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
1 hour agoHandshake completed75 ms
2 days agoHandshake completed217 ms
5 days agoHandshake completed96 ms
7 days agoHandshake completed64 ms
9 days agoHandshake completed64 ms
11 days agoHandshake completed83 ms
13 days agoHandshake completed71 ms
15 days agoHandshake completed67 ms
16 days agoHandshake completed121 ms
18 days agoHandshake completed141 ms
19 days agoHandshake completed81 ms
20 days agoHandshake completed922 ms
23 days agoHandshake completed78 ms
24 days agoHandshake completed111 ms

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

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.