Remote MCP · Endpoint

Discogs MCP server

No. Discogs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/discogs/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/discogs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
105 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Discogs MCP — music release / artist / label database
Listing
From the official MCP registry (active).
Recent checks of Discogs
CheckedResultHandshake
1 hour agoHandshake completed105 ms
1 day agoHandshake completed153 ms
2 days agoHandshake completed129 ms
3 days agoHandshake completed100 ms
4 days agoHandshake completed58 ms
5 days agoHandshake completed84 ms
6 days agoHandshake completed95 ms
8 days agoHandshake completed65 ms
11 days agoHandshake completed59 ms
13 days agoHandshake completed1.15 s
16 days agoHandshake completed131 ms
18 days agoHandshake completed63 ms
20 days agoHandshake completed60 ms
22 days agoHandshake completed58 ms
24 days agoHandshake completed57 ms
26 days agoHandshake completed69 ms
27 days agoHandshake completed79 ms
29 days agoHandshake completed40 ms

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

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