Tunova MCP server

• Addresshttps://api.tunova.ai/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on tunova.ai when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-28
• Tools3
• Server calls itselfTunova
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 197 ms.

• Its tools do Generate music tracks from text prompts via API, but not Integrate music generation into applications with webhooks.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• What an agent can do with it1 of 2 use cases
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer157 ms
• Space in an agent's context≈ 637 tokensthe definitions of all its tools (3), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 3 of 3

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• generate_song

  Start generating a song with Suno. Returns immediately with a job_id — a full render takes 1-3 minutes, so this does NOT return audio. After calling this, call wait_for_song with the returned job_id to get the audio URL when ready. Costs…

• wait_for_song

  Wait for a song job to finish and return the audio when ready. Polls server-side for up to ~45 seconds. If the song is ready, returns the clips with audio URLs. If it is still rendering, returns its status so you can call wait_for_song…

• check_song

  Get the current status of a song job by job_id — a single check with no waiting. Returns the audio URLs if complete, an error if it failed, or 'processing' if still rendering.