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

lacuna

https://www.lacuna.fm

Registry code: b8c2069c856ca592

api record

Lacuna generates AI music. Call `generate_music` to submit a task — it returns immediately with a `pending` task id, because rendering takes roughly 30–120 seconds. Poll `get_generation` with that id until status becomes `ready` (audio URLs are attached) or `failed`. Do not busy-loop: wait ~10 seconds between polls. Each task spends credits from the authenticated account, so confirm with the user before generating repeatedly.

endpoint
https://www.lacuna.fm/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 lacuna live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is lacuna 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 lacuna have?
3 tools: list_models, get_generation, generate_music.
Is lacuna 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.7%

90 days 99.1%· all time 99.1%

latency
215ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 432 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
media generation audio & speech
used for
  • generate a song from lyrics and style
  • check a music generation task
  • list available music models
takes → gives
text → audio, data
tools
2 reads1 changes data
_ 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
3 auth-required 3 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.

  • list_models reads auth-required 21h ago

    List the music models available through the API, with their credit cost per task, tracks produced per task, and language coverage.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_generation reads auth-required 21h ago

    Retrieve the current state of a music generation task by id. Status is `pending`, `ready`, or `failed`; audio URLs appear on `ready`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Generation task id, returned by generate_music."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • generate_music changes data auth-required never probed

    Create an AI music generation task on Lacuna. Returns immediately with a `pending` task; poll `get_generation` to retrieve the finished tracks and their audio URLs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "style",
    "title"
  ],
  "properties": {
    "model": {
      "enum": [
        "aether",
        "echo"
      ],
      "type": "string",
      "description": "Generation model. Defaults to `aether`. Call `list_models` for what each one covers."
    },
    "style": {
      "type": "string",
      "maxLength": 1000,
      "description": "Style description, e.g. \"pop, female vocal, 120 bpm, energetic\"."
    },
    "title": {
      "type": "string",
      "maxLength": 200,
      "description": "Track title."
    },
    "lyrics": {
      "type": "string",
      "maxLength": 5000,
      "description": "Lyrics in plain text. Required unless `instrumental` is true."
    },
    "audio_weight": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Audio reference weight 0–1 (aether only)."
    },
    "instrumental": {
      "type": "boolean",
      "description": "Generate an instrumental track (no lyrics). Defaults to false."
    },
    "style_weight": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Style weight 0–1 (aether only)."
    },
    "vocal_gender": {
      "enum": [
        "m",
        "f"
      ],
      "type": "string",
      "description": "Lead vocal gender hint (aether only)."
    },
    "negative_tags": {
      "type": "string",
      "maxLength": 500,
      "description": "Negative style tags to avoid (aether only)."
    },
    "weirdness_constraint": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Weirdness constraint 0–1 (aether only)."
    }
  },
  "additionalProperties": false
}
    arguments 68 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 b8c2069c856ca592.

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