Remote MCP · Endpoint

Boots & Bassline MCP server

No. Boots & Bassline answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://bootsandbassline.com/mcp

The last check completed an MCP handshake.

Registry name
com.bootsandbassline/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Songs, lyrics, previews and listening links for Boots & Bassline, plus a song finder.
Listing
From the official MCP registry (active).
Recent checks of Boots & Bassline
CheckedResultHandshake
3 hours agoHandshake completed71 ms
3 days agoHandshake completed81 ms
13 days agoHandshake completed84 ms
14 days agoHandshake completed95 ms
15 days agoHandshake completed101 ms
16 days agoHandshake completed102 ms
18 days agoHandshake completed79 ms
18 days agoHandshake completed99 ms
19 days agoHandshake completed1.01 s
21 days agoHandshake completed826 ms
22 days agoHandshake completed95 ms
25 days agoHandshake completed78 ms
27 days agoHandshake completed103 ms
30 days agoHandshake completed77 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 Boots & Bassline and makes no claim about it beyond what these checks measured.