Remote MCP · Endpoint

Audio Delivery Network MCP server

No — it is up, but it requires credentials. Audio Delivery Network answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://mcp.audiodelivery.net/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
net.audiodelivery/mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
AI-manageable audio CDN: upload, transcode, normalize, stream & deliver audio, plus grounded docs.
Listing
From the official MCP registry (active).
Recent checks of Audio Delivery Network
CheckedResultHandshake
1 hour agoCredentials required—
1 day agoCredentials required—
2 days agoHandshake completed394 ms
3 days agoHandshake completed160 ms
4 days agoHandshake completed264 ms
5 days agoHandshake completed265 ms
6 days agoHandshake completed171 ms
8 days agoHandshake completed266 ms
11 days agoHandshake completed303 ms
13 days agoHandshake completed191 ms
16 days agoHandshake completed243 ms
18 days agoHandshake completed266 ms
20 days agoHandshake completed169 ms
22 days agoHandshake completed178 ms
24 days agoHandshake completed173 ms
26 days agoHandshake completed245 ms
27 days agoHandshake completed277 ms
29 days agoHandshake completed216 ms
29 days agoHandshake completed207 ms

The last 19 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 Audio Delivery Network and makes no claim about it beyond what these checks measured.