Is the Sfxmint Sounds MCP server down?

mcp-registry/com.sfxmint/sounds · v1.7.0

healthy
Last checked 2026-10-18 05:50 UTC · handshake 123ms

As of 2026-10-18 05:50 UTC, the Sfxmint Sounds MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,630
outages (90d)
0
tools
18

Free CC0 sound effects for agents: ask by role (button-click, coin), sets, or search 4,600+.

Install Sfxmint Sounds MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http sfxmint-sounds-mcp-server https://sfxmint.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "sfxmint-sounds-mcp-server": {
      "type": "http",
      "url": "https://sfxmint.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 4 warning(s) across 18 tool(s); ~4,573 tokens of tool definitions.
Scores higher than 12% of 15,352 MCP servers Glimind has audited.
Its tool list costs an agent ~4,573 tokens per session — more than 60% of servers.
no tool-poisoning patterns
Schemas100
Descriptions78
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability20

What to fix (5)

18 of 18 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: add_kit_sounds, change_kit_take, change_sound, export_game_kit, fill_kit_from_library and 13 more

4 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_generation, get_role_sound, pick_kit_take

Handshake + tools/list takes ~1,726 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 1 tool(s) removed and 22 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 11 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.sfxmint%2Fsounds/fixes

add_kit_sounds 1 change
{
  "name": "add_kit_sounds",
  "description": "Add the user's own list of sounds to a kit (an app's or a game's events: names, optional moments and lengths), or a ready set's events with its library sounds already in use. Names, keys, order and lengths stay the user's; SFXMint writes how each sounds. Without kit_id it starts a new kit for the list. Free (no generation). Then call fill_kit_from_library to use free library sounds first, and make only the gaps.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "set": {
        "type": "string",
        "description": "Instead of sounds: a ready set's id from get_sound_set (its events, with its library sounds in use)."
      },
      "name": {
        "type": "string",
        "description": "A new kit's name (optional)."
      },
      "kit_id": {
        "type": "string",
        "description": "Add to this kit (kit_…); leave out to start a new kit."
      },
      "sounds": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "name"
          ],
          "properties": {
            "key": {
              "type": "string",
              "description": "The user's own event key or file name, e.g. '01-lab-air' (optional)."
            },
            "name": {
              "type": "string",
              "description": "The event, e.g. 'Ride request' or 'Coin pickup'."
            },
            "when": {
              "type": "string",
              "description": "When it plays (optional)."
            },
            "scene": {
              "type": "string",
              "description": "The scene heading from the user's list or approved proposal (optional); matching existing scene names are reused."
            },
            "seconds": {
              "type": "number",
              "description": "Length in seconds, 0.2 to 10 (optional; rounded to the nearest a kit offers)."
            }
          }
        },
        "maxItems": 60,
        "description": "The sounds, in the user's order."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
export_game_kit 1 change
{
  "name": "export_game_kit",
  "description": "What to put in the project: every included sound's event key and the take in use (file link valid 15 minutes, SHA-256), the sounds not ready yet, and zip_url for one ZIP (download it with the same Authorization header) holding the files in the chosen format, sounds.json (event key → file) and a README. Wire the game's events to sounds.json and let the user check the sounds in the game.",
  "inputSchema": {
    "type": "object",
    "required": [
      "kit_id"
    ],
    "properties": {
      "format": {
        "enum": [
          "wav",
          "mp3"
        ],
        "type": "string",
        "description": "File type in the ZIP (default wav)."
      },
      "kit_id": {
        "type": "string",
        "description": "The kit id from start_game_kit or add_kit_sounds (kit_…)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
find_kit_sound_candidates 1 change
{
  "name": "find_kit_sound_candidates",
  "description": "Up to five free library sounds for one kit sound, by its name or your own words, with their length, character and a listening URL. Nothing changes until use_library_sound.",
  "inputSchema": {
    "type": "object",
    "required": [
      "kit_id",
      "sound_id"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Other words to search with (optional)."
      },
      "kit_id": {
        "type": "string",
        "description": "The kit id from start_game_kit or add_kit_sounds (kit_…)."
      },
      "sound_id": {
        "type": "string",
        "description": "A sound id from get_game_kit (ks_…)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.sfxmint/sounds"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.sfxmint/sounds"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.sfxmint%2Fsounds.svg)](https://glimind.com/server/mcp-registry%2Fcom.sfxmint%2Fsounds?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.sfxmint%2Fsounds?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.sfxmint%2Fsounds.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.sfxmint%2Fsounds.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.sfxmint%2Fsounds?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8b9cbca9e79c90cf…, first seen 2026-10-17, included at leaf 13319 of 20,527. Version history · verify what your client received.

Tools (18)

Compare: most reliable media servers · most reliable other servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Sfxmint Sounds MCP server down right now?

As of 2026-10-18 05:50 UTC, the Sfxmint Sounds MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Sfxmint Sounds MCP server provide?

Sfxmint Sounds MCP server advertises 18 tools, including add_kit_sounds, change_kit_take, change_sound, export_game_kit, fill_kit_from_library.

How do I install Sfxmint Sounds MCP server?

Point your MCP client at this streamable-http endpoint: https://sfxmint.com/mcp

Is the Sfxmint Sounds MCP server safe to connect to an AI agent?

Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Sfxmint Sounds MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.