Remote MCP · Endpoint

Soundza MCP server

No. Soundza answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.soundza.com/mcp

The last check completed an MCP handshake.

Registry name
com.soundza/soundza
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free sound effects, music and ambience for games, videos and apps. Search, play and download.
Listing
From the official MCP registry (active).
Recent checks of Soundza
CheckedResultHandshake
5 hours agoHandshake completed80 ms
9 days agoHandshake completed268 ms
10 days agoHandshake completed149 ms
11 days agoHandshake completed185 ms
12 days agoHandshake completed68 ms
14 days agoHandshake completed117 ms
14 days agoHandshake completed98 ms
15 days agoHandshake completed84 ms
17 days agoHandshake completed74 ms
19 days agoHandshake completed189 ms
21 days agoHandshake completed112 ms
24 days agoHandshake completed71 ms
26 days agoHandshake completed72 ms
28 days agoHandshake completed111 ms

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

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