Skip to content
MCPSTAMP
MCP server report

Wubble MCP server

ai.wubble/audio

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 92 of 100 (grade A), higher than 66.1% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, ChatGPT, Gemini and MCP Registry.

Measured facts

Score
92A
Sign-in
OAuth
Tools listed
33
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Ready No blocking check failed.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

4 checks to fix

  1. Fails

    Server instructions

    instructions

    Measured No instructions in the initialize result

    Add an "instructions" string to the initialize result: what the server covers, for whom, and its limits.

  2. Warning

    Client registration (DCR or Client ID Metadata Documents)

    auth_registration

    Measured No registration_endpoint and no client_id_metadata_document_supported

    Add a Dynamic Client Registration endpoint (RFC 7591) or set client_id_metadata_document_supported: true; otherwise every store needs a manually issued client id.

  3. Warning

    Tool descriptions

    tool_descriptions

    Measured 15 under 60 chars: wubble_upload_audio, wubble_upload_vocal, wubble_generate_song, wubble_extend_lyrics, wubble_extend_song and 10 more

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  4. Warning

    initialize latency

    latency

    Measured 1561 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

23 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, serverInfo name and version, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Wubble

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.wubble.ai%2Fmcp)](https://www.mcpstamp.com/r/ai-wubble-audio/)

HTML

<a href="https://www.mcpstamp.com/r/ai-wubble-audio/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.wubble.ai%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Create, inspect, and manage Wubble music, speech, voice, and sound-effect requests through MCP.
Registry name
ai.wubble/audio
Remote URL
https://mcp.wubble.ai/mcp
Version
0.1.0
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026