Skip to content

Keyboardia

by adewale · remote · no sign-in to list tools · v1.1.0 · published by GitHub user adewale

Create, co-edit, analyze, publish, and export collaborative step-sequencer sessions through MCP.

Deletes · 1Final · 1Changes · 3

7 tools: 1 can delete or cancel things, 1 do something that can't be undone, 3 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http keyboardia https://keyboardia.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Deletes or cancels 1Claude Code: deny
  • edit_sessionMake one narrow, retry-safe edit to an existing collaborative session.No findings

    Why it is in this group

    • The name "edit_session" says "edit": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Make one narrow, retry-safe edit to an existing collaborative session. After every attempt, the next Keyboardia call must be get_session for the same session. A successful call includes a backwards-compatible compact snapshot plus an acknowledgement. That snapshot is not authoritative verification; do not make another edit or finish from it. Read with get_session next. Supported operations: add_track, set_track_instrument, set_track_pan, set_steps, and set_tempo. set_steps changes only the named steps; it never replaces a track or session. set_track_instrument replaces only a track's sound source, keeping its pattern, mix, timing, and custom name.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • publish_sessionFreeze the current music into a new immutable session and return its URL.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "publish_session" says "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_session" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Freeze the current music into a new immutable session and return its URL. The source session stays editable at its own URL. Only call this when someone explicitly asks to publish; it is never a side effect of editing or exporting.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • create_sessionCreate a new editable Keyboardia session with the normal defaults and return its shareable URL.No findings

    Why it is in this group

    • The name "create_session" says "create": a word for a change.
    Description, as the server wrote it
    Create a new editable Keyboardia session with the normal defaults and return its shareable URL. The session starts with no tracks; use edit_session to add them. Pass the same idempotency_key when retrying so an uncertain attempt cannot leave duplicate sessions behind.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • export_midiExport the session as a base64-encoded Standard MIDI File, matching what Keyboardia's own Export MIDI produces for the same music.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Export the session as a base64-encoded Standard MIDI File, matching what Keyboardia's own Export MIDI produces for the same music. The session is not modified. The result lists any session features a MIDI file cannot carry rather than approximating them silently.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • remix_sessionCopy an existing session — published or editable — into a new editable session that records the original as its source.No findings

    Why it is in this group

    • The description's first verb is "copy": a word for a change.
    Description, as the server wrote it
    Copy an existing session — published or editable — into a new editable session that records the original as its source. The source is never modified, so this is how to continue from published work.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Claude Code: allow
  • analyze_sessionDescribe what is happening musically in a session — rhythm, pitch content, inferred key, and chords — without changing anything.No findings

    Why it is in this group

    • The name "analyze_session" says "analyze": a word for reading.
    Description, as the server wrote it
    Describe what is happening musically in a session — rhythm, pitch content, inferred key, and chords — without changing anything. Use this to explain music rather than to edit it. Results come from the same music-theory module the browser's Key Assistant and Chromatic Grid use, and report where the analysis is uncertain instead of guessing.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_sessionRead the current tempo and compact track patterns from an existing Keyboardia session.No findings

    Why it is in this group

    • The name "get_session" says "get": a word for reading.
    Description, as the server wrote it
    Read the current tempo and compact track patterns from an existing Keyboardia session.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Looked at Oct 22, 2026, 14:55 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
none
RFC 9728 protected resource metadata
none
Authorization servers
none
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://keyboardia.dev/mcp: tools/list returned 7 tools to an anonymous client, including edit_session (destructive), publish_session (irreversible), create_session (write), remix_session (write), export_midi (write)

    What this check looks for

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http keyboardia https://keyboardia.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__keyboardia__get_session",
      "mcp__keyboardia__analyze_session"
    ],
    "ask": [
      "mcp__keyboardia__create_session",
      "mcp__keyboardia__remix_session",
      "mcp__keyboardia__publish_session",
      "mcp__keyboardia__export_midi"
    ],
    "deny": [
      "mcp__keyboardia__edit_session"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as keyboardia. Review it before you use it.

Capability tags behind 1 rule
  • mcp__keyboardia__publish_session untrusted-input, outbound