Remote MCP · Endpoint

Wubble MCP server

No. Wubble answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.wubble.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.wubble/audio
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
700 ms
Tools exposed
33 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Create, inspect, and manage Wubble music, speech, voice, and sound-effect requests through MCP.
Listing
From the official MCP registry (active).
Recent checks of Wubble
CheckedResultHandshake
5 hours agoHandshake completed700 ms
2 days agoHandshake completed708 ms
4 days agoHandshake completed686 ms
5 days agoHandshake completed690 ms
7 days agoHandshake completed713 ms
8 days agoHandshake completed695 ms
9 days agoHandshake completed707 ms
12 days agoHandshake completed712 ms
13 days agoHandshake completed698 ms
15 days agoHandshake completed692 ms
16 days agoHandshake completed736 ms
17 days agoHandshake completed725 ms
18 days agoHandshake completed721 ms
19 days agoHandshake completed722 ms
20 days agoHandshake completed771 ms
21 days agoHandshake completed773 ms
22 days agoHandshake completed715 ms

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

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