Remote MCP · Endpoint

Notify Sound MCP server

No. Notify Sound answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://notifysound.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.botmonster/notify-sound
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
145 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Design notification sounds from layered tones and get an editor link to play and download.
Listing
From the official MCP registry (active).
Recent checks of Notify Sound
CheckedResultHandshake
33 minutes agoHandshake completed145 ms
3 days agoHandshake completed145 ms
13 days agoHandshake completed70 ms
13 days agoHandshake completed96 ms
15 days agoHandshake completed80 ms
16 days agoHandshake completed119 ms
17 days agoHandshake completed92 ms
18 days agoHandshake completed115 ms
18 days agoHandshake completed81 ms
20 days agoHandshake completed107 ms
22 days agoHandshake completed129 ms
25 days agoHandshake completed68 ms
27 days agoHandshake completed149 ms

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

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