Lacuna Music
REMOTE · WWW.LACUNA.FM · 2 COMPONENTS · SCANNED SEP 27
Generate AI music via the Lacuna Music API from MCP clients like Claude Desktop & Code.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 410 tokens (~136/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Lacuna Music MCP server?
Lacuna Music is a hosted endpoint at https://www.lacuna.fm/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.lacuna.fm
claude mcp add --transport http joylink-ltd-lacuna-mcp 'https://www.lacuna.fm/mcp'
{
"mcpServers": {
"joylink-ltd-lacuna-mcp": {
"url": "https://www.lacuna.fm/mcp"
}
}
} {
"servers": {
"joylink-ltd-lacuna-mcp": {
"type": "http",
"url": "https://www.lacuna.fm/mcp"
}
}
} [mcp_servers.joylink-ltd-lacuna-mcp] url = "https://www.lacuna.fm/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joylink-ltd-lacuna-mcp": {
"type": "remote",
"url": "https://www.lacuna.fm/mcp",
"enabled": true
}
}
} openclaw mcp add joylink-ltd-lacuna-mcp --url 'https://www.lacuna.fm/mcp' --transport streamable-http
mcp_servers:
joylink-ltd-lacuna-mcp:
url: "https://www.lacuna.fm/mcp" {
"McpServers": {
"joylink-ltd-lacuna-mcp": {
"Transport": "http",
"Url": "https://www.lacuna.fm/mcp"
}
}
} assistant mcp add joylink-ltd-lacuna-mcp -t streamable-http -u 'https://www.lacuna.fm/mcp'
{
"mcpServers": {
"joylink-ltd-lacuna-mcp": {
"type": "http",
"url": "https://www.lacuna.fm/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://www.lacuna.fm/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lacuna.fm | CN=YE2,O=Let's Encrypt,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5eddea59085dccda8f05090bf16c8f6022f |
| SANs: *.lacuna.fm, lacuna.fm | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.lacuna.fm. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fm. | present | 26186, 60226 | 8, 8 | Verified |
| lacuna.fm. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="lacuna", resource_metadata="https://www.lacuna.fm/.well-known/oauth-protected-resource", error="invalid_token", error_description="Invalid API key"
Bearer realm="lacuna", resource_metadata="https://www.lacuna.fm/.well-known/oauth-protected-resource", error="invalid_token", error_description="Invalid API key"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Protected resource metadata
| Document | https://www.lacuna.fm/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.lacuna.fm |
| Authorisation server | https://www.lacuna.fm |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.lacuna.fm/mcp | Verified | 200 | |
| http (plaintext) | http://www.lacuna.fm/mcp | HTTPS enforced | 301 | https://www.lacuna.fm/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_music Generate music ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audio_weight | number | – | Audio reference weight 0–1 (aether only). |
| instrumental | boolean | – | Generate an instrumental track (no lyrics). Defaults to false. |
| lyrics | string | – | Lyrics in plain text. Required unless `instrumental` is true. |
| model | string | – | Generation model. Defaults to `aether`. Call `list_models` for what each one covers. |
| negative_tags | string | – | Negative style tags to avoid (aether only). |
| style | string | yes | Style description, e.g. "pop, female vocal, 120 bpm, energetic". |
| style_weight | number | – | Style weight 0–1 (aether only). |
| title | string | yes | Track title. |
| vocal_gender | string | – | Lead vocal gender hint (aether only). |
| weirdness_constraint | number | – | Weirdness constraint 0–1 (aether only). |
No output schema declared.
No examples provided.
get_generation Get generation ~54
Retrieve the current state of a music generation task by id. Status is `pending`, `ready`, or `failed`; audio URLs appear on `ready`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Generation task id, returned by generate_music. |
No output schema declared.
No examples provided.
list_models List models ~33
List the music models available through the API, with their credit cost per task, tracks produced per task, and language coverage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Lacuna Music MCP server?
Lacuna Music is an MCP server listed in the public MCP registry as io.github.JOYLINK-LTD/lacuna-mcp. Generate AI music via the Lacuna Music API from MCP clients like Claude Desktop & Code. This page covers its hosted endpoint (https://www.lacuna.fm/mcp).
Is the Lacuna Music MCP server safe to use?
Lacuna Music scores 94 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Lacuna Music MCP server expose?
Lacuna Music exposes 3 tools: generate_music, get_generation, list_models. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Does the Lacuna Music MCP server require authentication?
Yes. Lacuna Music asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Lacuna Music MCP server still maintained?
Lacuna Music is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.