Remote MCP · Endpoint

SongUp AI MCP server

No. SongUp AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.songupai.com/mcp/agents

The last check completed an MCP handshake.

Registry name
com.songupai/songup-ai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
951 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find AI songs in 24 languages, start a custom song on SongUp AI, and find browser audio tools.
Listing
From the official MCP registry (active).
Recent checks of SongUp AI
CheckedResultHandshake
1 hour agoHandshake completed951 ms
2 days agoHandshake completed179 ms
4 days agoHandshake completed1.12 s
7 days agoHandshake completed2.75 s
9 days agoHandshake completed989 ms
11 days agoHandshake completed777 ms
13 days agoHandshake completed795 ms
15 days agoHandshake completed1.10 s
17 days agoHandshake completed822 ms
19 days agoHandshake completed61 ms
20 days agoHandshake completed221 ms
22 days agoHandshake completed918 ms
23 days agoHandshake completed83 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 SongUp AI and makes no claim about it beyond what these checks measured.