Remote MCP · Endpoint

Kindle Music MCP server

No. Kindle Music answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://share.kindlemusic.cn/mcp

The last check completed an MCP handshake.

Registry name
cn.kindlemusic/kindlemusic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.10 s
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search 2M+ licensed production-music tracks, find similar ones by track or audio, share pick lists.
Listing
From the official MCP registry (active).
Recent checks of Kindle Music
CheckedResultHandshake
1 hour agoHandshake completed1.10 s
9 days agoHandshake completed651 ms
10 days agoHandshake completed2.95 s
11 days agoHandshake completed1.87 s
12 days agoHandshake completed716 ms
14 days agoHandshake completed678 ms
14 days agoHandshake completed706 ms
15 days agoHandshake completed1.84 s
17 days agoHandshake completed1.66 s
19 days agoHandshake completed1.65 s
21 days agoHandshake completed871 ms
24 days agoHandshake completed1.75 s
26 days agoHandshake completed721 ms
28 days agoHandshake completed732 ms

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

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