accueil / serveurs / Recherche & Web / com.sfxmint/sounds
com.sfxmint/sounds
serveur MCP (Model Context Protocol) · sfxmint 1.8.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.sfxmint/sounds est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.sfxmint/sounds » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 7 outils
- change_sound≈ 306 tokens
Change one take of a generation this account made, from the take itself: say what is off in the user's words (change, any language) or name the action. Three versions come back (a light, medium and strong change; for a loop, three seams) as CC0 WAV files. Free: no generation is used and no plan is needed. When the words ask for a different sound rather than a change to this one, it answers no_action with a description to pass to generate_sound. The user should listen and pick one.
Paramètres, retour & exemple (4)
Paramètrestake· number · requis
Which of its takes (index, 1-4), finishedaction· string · optionnel · crisper | heavier | shorter_tail | longer_tail | room | far | loop
crisper: too muddy; heavier: too light; shorter_tail: rings on too long; longer_tail: stops too abruptly; room: too dry; far: too close; loop: make it loopchange· string · optionnel
What is off, in the user's words: 'too muddy', 'make it loop', 'sounds too close'order_id· string · requis
The generation, from generate_sound or get_generation
Exemple d'appel{"name": "change_sound", "arguments": {"take": 1, "order_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - generate_sound≈ 467 tokens
Make a new sound effect from a description when the library has nothing suitable (search_sounds has no full match and its closest sounds do not suit; it then returns generate_available). Needs an SFXMint API key and uses the account's 3 free tries first, then a pass or plan on the account — a 24-hour pass ($3.90, 50 sounds) or a plan (from $9.90 for 30 days, 50 to 200 a day) — each up to 4 CC0 WAV takes of up to 10 s; one that makes no take does not count; with neither it answers payment_required with buy_url and website_url (the website's page where the user can make it and hear it first). Returns CC0 WAV files (signed links valid 15 minutes) with SHA-256 and seed; if they are not ready within about 25 seconds, it returns the order id for get_generation. AI-generated: the user should listen before use.
Paramètres, retour & exemple (4)
Paramètresprompt· string · requis
The sound the user needs, in plain words and any language: what it is for and what should be heard. With enhance (recommended), SFXMint writes the description the model gets. Leave out lengths (use duration_s).enhance· boolean · optionnel
Recommended: SFXMint writes the prompt into the description the model gets, as the website's AI Enhance does, and the result gives that description. Default false: the prompt goes to the model exactly as written.duration_s· number · optionnel · 0.2 | 0.5 | 1 | 1.5 | 2 | 2.5 | 3 | 4
Longest length in seconds. Leave it out and SFXMint chooses from the description; either way the silence before and after the sound is cut, so a take can be shortervariations· number · optionnel · 1 | 2 | 4
How many takes to make (default 4; one generation either way)
Exemple d'appel{"name": "generate_sound", "arguments": {"prompt": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_generation≈ 68 tokens
Check a generation started with generate_sound or change_sound: status, and fresh download links for the finished takes.
Paramètres, retour & exemple (1)
Paramètresorder_id· string · requis
Exemple d'appel{"name": "get_generation", "arguments": {"order_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_role_sound≈ 545 tokens
Choose this when the task calls for a sound for a named event or interaction — a button click, purchase success, error beep, level-up, dialogue blip, notification. Pass the role as plain words: role ids (click, success, purchase-success, dialogue-blip, notification…) and common aliases (button click, ka-ching, jump scare, text blip…) are all accepted. Returns a qualified candidate for that role when one satisfies the requested constraints, with MP3/WAV URLs, 2-3 alternates and the family page for browsing more. Five core game roles include content_check (verified/unverified/rejected), scoped to scene, role, format and exact file SHA256; unverified previews are not certified suitable. Download selected files locally and retain originals. Task-permitted processing requires a recipe, output SHA256, renewed file checks and a listening check; changed bytes do not inherit content review. Other task-permitted sources or local synthesis may be mixed in. Optional style: crisp (short, bright, dry), soft (darker, gentler), spacious (reverb, longer tail), balanced (default: most typical). For multiple events consider get_sound_set; use search_sounds for a description or a gap. These are task branches, not a fixed sequence. Unknown roles return not_found with the full role list; GET https://sfxmint.com/api/v1/roles lists roles with aliases.
Paramètres, retour & exemple (5)
Paramètresloop· boolean · optionnel
Require prepared loop metadata; seam evidence is returned separately.role· string · requis
Role id or alias, e.g. 'click', 'button click', 'purchase-success', 'ka-ching', 'error beep', 'level-up', 'dialogue blip', 'notification'style· string · optionnel · balanced | crisp | soft | spacious
Optional. balanced (default) = the family's most typical take; crisp = short, bright, dry; soft = darker, gentler; spacious = reverb, longer tailformat· string · optionnel · wav | mp3 | oggmax_duration_ms· number · optionnel
Hard maximum delivered duration in milliseconds.
Exemple d'appel{"name": "get_role_sound", "arguments": {"role": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_sound≈ 85 tokens
Get full metadata for one sound by slug, including download URLs, description and measured acoustics (attack/tail/brightness + character labels).
Paramètres, retour & exemple (1)
Paramètresslug· string · requis
Sound slug, e.g. 'impact-punch-01'
Exemple d'appel{"name": "get_sound", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_sound_set≈ 326 tokens
Get a coherent set of sounds for an app or game in one call — one sound per role, with format metadata, hashes and stable download URLs. Use it when the task needs a whole kit; use get_role_sound for one event. Check content_check: verified/unverified/rejected is bound to the exact role, format and file SHA256; unverified files still require listening in context. Sets include UI styles, game and app scenarios, acoustic-drum-kit, animal-calls (15 isolated calls), and dungeon-traps (6 isolated mechanisms).
Paramètres, retour & exemple (2)
Paramètresset· string · optionnel · ui-crisp | ui-soft | ui-spacious | retro-game | chat-app | saas-app | checkout | learning
Set id (default ui-crisp). Includes acoustic-drum-kit, animal-calls and dungeon-traps alongside the UI and scenario sets listed in the enum.format· string · optionnel · wav | mp3 | ogg
File format for selection and checks (default WAV; OGG only among sounds published before 2026-10-14). Legacy urls remains MP3; download_urls follows this format.
Exemple d'appel{"name": "get_sound_set", "arguments": {"set": "ui-crisp", "format": "wav"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_sounds≈ 582 tokens
Free-text search over the SFXMint library of free CC0 sound effects. Use it for sound descriptions, additional constraints or gaps left by another tool. Choose get_role_sound for a named event or get_sound_set for multiple events when that fits the task; these are task branches, not a fixed sequence. Hard constraints (duration, loop, format, excluded words) always apply. results hold sounds whose text has every word of the query. When there are none, closest lists the nearest sounds that meet every hard constraint, best first, each with missing_terms: judge them from title and description and let the user listen. library_fit says how well the library covers the request (full, close, weak, none); anything short of full also returns generation options. Returns direct, hotlinkable MP3/WAV URLs and verified OGG (Vorbis) URLs where available — no API key, no attribution required — plus measured acoustics (attack_ms, tail_ms, centroid_hz), character labels like 'bright · punchy · tight', loop/file-QC status, and score/match as ranking evidence only (role = known role default, exact = all words hit, partial = some words hit, semantic = nearest by meaning).
Paramètres, retour & exemple (6)
Paramètresloop· boolean · optionnel
Require (true) or exclude (false) a candidate marked with prepared loop metadata; seam evidence is returned separately.limit· number · optionnel
Max results (default 20, max 50)query· string · requis
Keywords or a natural-language description, e.g. 'door slam', 'soft UI confirmation chime', 'coin pickup'format· string · optionnel · wav | mp3 | ogg
Delivery format (ogg = Ogg Vorbis, only sounds published before 2026-10-14 have it); loop=true defaults to WAV when omitted.category· string · optionnel
Optional category slug: ui, retro-game, transition, impact, ambience, water, fire-electric, footsteps, door, mechanical, paper-fabric, glass, animal, crowd, cartoon, magic-scifi, horror, feedback, instrument, office, human, vehicle, householdmax_duration_ms· number · optionnel
Hard maximum delivered duration in milliseconds; format-specific measurement is required.
Exemple d'appel{"name": "search_sounds", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».