_ registry / mcp streamable-http · checked 2h ago

Tunova

https://api.tunova.ai

Registry code: fb5056615c975d0b

api record

Generate music with Suno. Call generate_song to start a song (returns a job_id; rendering takes 1-3 minutes), then wait_for_song with that job_id to get the audio URL once ready. Use check_song for a one-shot status. Set X-API-Key (your sk_live_ key from https://tunova.ai/keys) in the MCP client headers.

endpoint
https://api.tunova.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Tunova live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Tunova free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Tunova have?
3 tools: wait_for_song, generate_song, check_song.
Is Tunova safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
105ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 434 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • generate a song from a prompt
  • check song generation status
  • wait for a song and get audio
takes → gives
text → audio
tools
2 reads1 changes data
note
resells another provider
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 auth-required 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_song reads auth-required 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "description": "The job_id returned by generate_song."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • wait_for_song reads unknown never probed

    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 again with the same job_id. Safe to call repeatedly — it only reads status, never starts a new song.

    mcp-tool

    {
      "type": "object",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "description": "The job_id returned by generate_song."
        },
        "max_wait_seconds": {
          "type": "number",
          "description": "How long to wait before returning (default 45, max 55)."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • generate_song changes data unknown never probed

    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 10 tokens, billed only on success.

    mcp-tool

    {
      "type": "object",
      "required": [
        "prompt"
      ],
      "properties": {
        "tags": {
          "type": "string",
          "description": "Style/genre, e.g. 'lofi hip hop, mellow, rainy'. Most useful in custom mode."
        },
        "model": {
          "enum": [
            "v6",
            "v5.5"
          ],
          "type": "string",
          "description": "Suno model: v6, or v5.5 as a compatibility alias for v6. Optional; the account default is unchanged."
        },
        "title": {
          "type": "string",
          "description": "Song title (custom mode)."
        },
        "custom": {
          "type": "boolean",
          "description": "false (default): describe the song and Suno writes everything. true: `prompt` is the literal lyrics, and `tags`/`title` are used."
        },
        "prompt": {
          "type": "string",
          "description": "What the song should be about (simple mode), or the exact lyrics (when custom=true)."
        },
        "instrumental": {
          "type": "boolean",
          "description": "If true, generate without vocals."
        },
        "idempotency_key": {
          "type": "string",
          "maxLength": 128,
          "minLength": 1,
          "description": "Optional logical-request id. Reuse it to recover one submit; use a new value to intentionally generate the same song again or retry after a terminal failed job. When omitted, Tunova derives a stable key from the song arguments for safe automatic retries."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fb5056615c975d0b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fb5056615c975d0b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fb5056615c975d0b/badge.svg)](https://brick.blue/agent/fb5056615c975d0b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.