Skip to content

Notify Sound

by botmonster · remote · no sign-in to list tools · v1.0.0 · published by GitHub user botmonster

Design notification sounds from layered tones and get an editor link to play and download.

Changes · 1
CompareRegistry entry

5 tools: 1 change things and 4 only read.

Scanned Oct 22, 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 notify-sound https://notifysound.com/mcp

Tools

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

5 tools

Changes things 1Claude Code: ask
  • create_soundBuild a notification sound from your own layer design and get an editor link for it.No findings

    Why it is in this group

    • The name "create_sound" says "create": a word for a change.
    Description, as the server wrote it
    Build a notification sound from your own layer design and get an editor link for it. The link opens the sound in the editor, where the user plays, tweaks and downloads it. Returns the link, the stored sound and warnings for any value that was out of range, rounded or ignored. Read get_sound_guide first.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 4Claude Code: allow
  • get_library_soundGet the full design of a built-in sound and its editor link, to use as a starting point for create_sound.No findings

    Why it is in this group

    • The name "get_library_sound" says "get": a word for reading.
    Description, as the server wrote it
    Get the full design of a built-in sound and its editor link, to use as a starting point for create_sound.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_sound_guideHow sounds are built: layers, envelope, pitch, timing, noise, levels and effects, with example designs.No findings

    Why it is in this group

    • The name "get_sound_guide" says "get": a word for reading.
    Description, as the server wrote it
    How sounds are built: layers, envelope, pitch, timing, noise, levels and effects, with example designs. Read it once before designing.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_library_soundsList the built-in sounds by group, or search them by name.No findings

    Why it is in this group

    • The name "list_library_sounds" says "list": a word for reading.
    Description, as the server wrote it
    List the built-in sounds by group, or search them by name. Without arguments it lists every group with its sound names. Use a close built-in sound as a starting point.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_soundTurn a share link (or the code after #s=) back into the sound design, to change it and call create_sound again.No findings

    Why it is in this group

    • The name "read_sound" says "read": a word for reading.
    Description, as the server wrote it
    Turn a share link (or the code after #s=) back into the sound design, to change it and call create_sound again.

    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 or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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.

Install

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

claude mcp add --transport http notify-sound https://notifysound.com/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__notify-sound__read_sound",
      "mcp__notify-sound__list_library_sounds",
      "mcp__notify-sound__get_library_sound",
      "mcp__notify-sound__get_sound_guide"
    ],
    "ask": [
      "mcp__notify-sound__create_sound"
    ],
    "deny": []
  }
}

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 notify-sound. Review it before you use it.