_ registry / mcp streamable-http · checked 53m ago

songbrain

https://api.songbrain.ai

Registry code: 044901d70be5d58e

api record

Songbrain analyses songs for music-video and AI-video work. For any song it returns Song DNA (genre, tempo, key, mood, instruments), a song-wide beat grid and sections, the best moments (with start/peak/end seconds and why they work), word-timed lyrics, scores, the story/world/palette and a beat-synced shot plan whose scenes carry exact seconds and ready image/video prompts. To show a user what the output looks like, call list_example_songs, then get_example_analysis or get_example_shot_plan; no key is needed. To analyse the user's own song, call analyze_song with a public audio URL. That…

endpoint
https://api.songbrain.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 songbrain live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is songbrain free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does songbrain have?
7 tools: get_pricing, analyze_song, get_example_analysis, get_example_shot_plan, get_song, list_example_songs, get_account.
Is songbrain 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
100%

90 days 100%· all time 100%

latency
168ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 7 tools
1 open1 auth-required 5 never probed 2 of 7 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.

  • list_example_songs open 53m ago

    List real Songbrain analyses of Songbrain's own songs (no API key needed). Use one to show what the API returns before analysing a user's song.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_account auth-required 53m ago

    Free songs left this month, credit balance and price per song for the connected key.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_pricing unknown never probed

    Songbrain API prices (free songs per month, price per song) and limits.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • analyze_song unknown never probed

    Start the analysis of a song at a public audio URL (MP3, WAV, FLAC, M4A, AAC, OGG or AIFF; 30 s to 10 min). Needs an API key on the MCP connection. Returns a song_id; poll get_song until status is 'done' (typically 60–90 seconds, up to ~2 minutes when busy). Uses one free song or 25 credits.

    mcp-tool

    {
      "type": "object",
      "required": [
        "audio_url"
      ],
      "properties": {
        "title": {
          "type": "string"
        },
        "artist": {
          "type": "string"
        },
        "audio_url": {
          "type": "string",
          "description": "Public http(s) URL of the audio file"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_example_analysis unknown 53m ago

    Full analysis of an example song: Song DNA, beat grid and sections, best moments, lyrics, scores, story and shot plan. No API key needed. Summary view by default (no per-word timings or beat arrays); set view='full' for everything.

    mcp-tool

    {
      "type": "object",
      "required": [
        "example_id"
      ],
      "properties": {
        "view": {
          "enum": [
            "summary",
            "full"
          ],
          "type": "string",
          "default": "summary"
        },
        "sections": {
          "type": "array",
          "items": {
            "enum": [
              "song_dna",
              "timeline",
              "best_moments",
              "lyrics",
              "scores",
              "story",
              "shot_plan"
            ],
            "type": "string"
          },
          "description": "Only these sections (default: all)"
        },
        "example_id": {
          "type": "string",
          "description": "id from list_example_songs"
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • get_example_shot_plan unknown never probed

    The beat-synced shot plan of an example song: every scene with start and end seconds, its act (setup, turn or payoff), the image/video prompt, framing, motion and the lyric sung under it, plus the story, world and palette. No key needed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "example_id"
      ],
      "properties": {
        "example_id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • get_song unknown never probed

    Status of a song started with analyze_song, then its full analysis once done. Summary view by default; view='full' adds word timings and beat arrays.

    mcp-tool

    {
      "type": "object",
      "required": [
        "song_id"
      ],
      "properties": {
        "view": {
          "enum": [
            "summary",
            "full"
          ],
          "type": "string",
          "default": "summary"
        },
        "song_id": {
          "type": "string"
        },
        "sections": {
          "type": "array",
          "items": {
            "enum": [
              "song_dna",
              "timeline",
              "best_moments",
              "lyrics",
              "scores",
              "story",
              "shot_plan"
            ],
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    }
    arguments 35 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 044901d70be5d58e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/044901d70be5d58e/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/044901d70be5d58e/badge.svg)](https://brick.blue/agent/044901d70be5d58e?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
100%

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.