Skip to content

osc-bridge MCP server

io.github.roomi-fields/osc-bridgeroomi-fieldsstreamable-httpv0.23.1Scanned

OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.

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

Tools: 2 delete, 2 irreversible, 18 write, 7 read.
  • Reads private data · 3
  • Reads text others write · 17
  • Can send data out · 2
  • 5 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the osc-bridge MCP server can do

The osc-bridge MCP server is published by the GitHub account roomi-fields. It has 29 tools. It can delete or cancel things (2 tools: withdraw_preset and load_preset), do things that cannot be undone, such as sending, paying or publishing (update_preset and relay_send) and create or change data (18 tools: export_device, report_result, report_mapping, submit_driver and 14 more). 7 tools only read.

3 tools read private data (get_device_docs, list_routes and get_preset); 17 tools bring in text other people can write (list_routes, submit_driver, submit_fix and 14 more); 2 tools can send data out of your system (report_mapping and relay_send). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 5 findings (install-script and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.23.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

29 tools

Deletes or cancels 2Claude Code: deny
  • load_presetLoad a shared preset (find_presets, get_preset) into the user's device through a relay: its settings are sent through the driver, its patch data as SysEx — which replaces the sound…Reads text others writeNo findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Load a shared preset (find_presets, get_preset) into the user's device through a relay: its settings are sent through the driver, its patch data as SysEx — which replaces the sound the device holds, so the relay asks the user to accept it and this call waits for the answer (up to 2 minutes): tell the user first. Afterwards, tell SynthHub how it went with report_preset.

    Annotations the server declares

    • title: Load a preset through a relay
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • withdraw_presetWithdraw a preset this account shared: it is no longer listed nor served.No findings

    Why it is in this group

    • The name "withdraw_preset" says "withdraw": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Withdraw a preset this account shared: it is no longer listed nor served. Copies others already made stay under CC BY-SA.

    Annotations the server declares

    • title: Withdraw a preset
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 2Claude Code: ask
  • relay_sendPlay or set something on the user's hardware through a relay: give a driver (id or slug) and one of its OSC addresses from list_routes with its arguments (e.g.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "relay_send" says "send": a word for sending, and what is sent cannot be taken back.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "relay_send" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Play or set something on the user's hardware through a relay: give a driver (id or slug) and one of its OSC addresses from list_routes with its arguments (e.g. address '/filter/cutoff', args [64]; '/note/on', args [60, 100]) — the server turns it into the right CC, NRPN, note or SysEx message. Or give raw MIDI bytes as hex. Values are the device's own numbers, clamped to the parameter's range. Any SysEx but the Identity Request (patch dumps, stores, settings, preset restores) may overwrite the device's memory: the relay asks the user to accept it first and this call waits for the answer (up to 2 minutes), so tell the user what you are about to send.

    Annotations the server declares

    • title: Send through a relay
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • update_presetPublish a new version of a preset this account shared: new content (hex, file, settings or midi_file) makes a new version, kept with a change note — earlier versions stay available…Reads text others writeNo findings

    Why it is in this group

    • The name "update_preset" says "update": a word for a change.
    • The description's first verb is "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.
    Description, as the server wrote it
    Publish a new version of a preset this account shared: new content (hex, file, settings or midi_file) makes a new version, kept with a change note — earlier versions stay available; the description fields alone change it in place. Someone else's preset: share yours with derived_from instead.

    Annotations the server declares

    • title: Update a preset
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 18Claude Code: ask
  • claim_presetsClaim presets SynthHub imported from another site (their page says 'imported', with the author's name and page there) when the user is that author: give the id of one of them; the …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Claim presets SynthHub imported from another site (their page says 'imported', with the author's name and page there) when the user is that author: give the id of one of them; the server answers with a code for the user to add to their author page at that site (profile or bio). Once it is there, call again with verify: true: every preset imported from that author becomes the user's, to edit or withdraw.

    Annotations the server declares

    • title: Claim imported presets
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • comment_presetComment on a shared preset — how it sounds, how you used it, what you changed — optionally attaching your remix (a preset you shared with derived_from).Reads text others writeNo findings

    Why it is in this group

    • The name "comment_preset" says "comment": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Comment on a shared preset — how it sounds, how you used it, what you changed — optionally attaching your remix (a preset you shared with derived_from). Comments are public at once. Also: remove one of this account's comments (remove), or flag someone else's as abusive or off-topic (flag); comments several accounts flag are hidden until reviewed.

    Annotations the server declares

    • title: Comment on a preset
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • export_deviceWrite one driver in a format other tools read, any of the formats of osd-formats: 'oscquery' gives its OSC namespace as OSCQuery JSON (every route with type tags, ranges and access…1 finding

    Why it is in this group

    • The description's first verb is "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "export_device" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Write one driver in a format other tools read, any of the formats of osd-formats: 'oscquery' gives its OSC namespace as OSCQuery JSON (every route with type tags, ranges and access, for OSC controllers and browsers); 'midnam' gives its MIDI names as a MIDI Name Document (controllers incl. NRPN/RPN, named values, drum notes per channel, for DAWs such as Ardour or Logic); 'deluge' gives the definition file of a Deluge; and the others in the enum. Each carries the credit and licence of the driver's sources. The document is the text content; an OSCQuery namespace is large (every address, each CC 0-127 included). It only reads: to put an export on a device, use install_export.

    Annotations the server declares

    • title: Export a driver
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • follow_authorFollow an author of shared presets (by pseudonym), or stop (on: false); with author alone and on omitted, shows their page: profile, presets, followers.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.
    Description, as the server wrote it
    Follow an author of shared presets (by pseudonym), or stop (on: false); with author alone and on omitted, shows their page: profile, presets, followers. Without author, lists the newest presets of the authors this account follows.

    Annotations the server declares

    • title: Follow an author
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preset_collectionCollections of shared presets, public, made by one account (e.g.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.
    Description, as the server wrote it
    Collections of shared presets, public, made by one account (e.g. 'Dark basses for minilogue'). action: create (name, description), rename (collection, name, description), add or remove (collection, id), delete (collection), get (collection: its presets), list (this account's collections, or author: someone's).

    Annotations the server declares

    • title: Preset collections
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • relay_detectFind which devices are connected to the user's machine through a relay: sends the MIDI Identity Request (F0 7E 7F 06 01 F7, changes nothing on the device) to every output and match…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "relay_detect" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Find which devices are connected to the user's machine through a relay: sends the MIDI Identity Request (F0 7E 7F 06 01 F7, changes nothing on the device) to every output and matches the answers — manufacturer, model, firmware version — against the drivers' identity blocks. With maker_requests, also sends the makers' own identity requests the drivers name (they change nothing either, but the relay asks the user to accept them, once per output: tell the user first), which recognise devices that ignore the universal one. Returns the best driver ids (recognised_by and firmware when an identity block recognised the device) and identity_hex to pass to report_result. A device that does not answer is found by its knobs with listen_ms (by_controls), or by what people confirmed of its port name (learned); when several remain, ask names the control to have the user turn next (expect: what each candidate would send), then call again with listen_ms.

    Annotations the server declares

    • title: Detect devices through a relay
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • relay_listenListen to what the user's hardware sends through a relay for a few seconds: notes, CC, NRPN, SysEx, decoded.Reads text others write1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "relay_listen" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    Listen to what the user's hardware sends through a relay for a few seconds: notes, CC, NRPN, SysEx, decoded. With a device, each CC or NRPN that moved is matched to the driver's OSC addresses — ask the user to move one control on the device while listening to learn which address it is, or to check that the driver's map is right (then record what you saw with report_mapping, so the catalogue learns it).

    Annotations the server declares

    • title: Listen through a relay
    • readOnlyHint: true
    • idempotentHint: false
    • openWorldHint: true
  • relay_statusCheck a relay: the user opened https://synthhub.roomi-fields.com/connect/ (or ran osc-bridge connect) and gave you its pairing code.Reads text others write1 finding

    Why it is in this group

    • The name "relay_status" says "status": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "relay_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The name "relay_status" says "status": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Check a relay: the user opened https://synthhub.roomi-fields.com/connect/ (or ran osc-bridge connect) and gave you its pairing code. Returns the MIDI output and input ports of their machine, and devices: the driver the user confirmed for each port on the page (use it directly, no detection needed). Nothing is sent to the hardware.

    Annotations the server declares

    • title: Relay status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • report_mappingTeach the catalogue which MIDI message a control really sends: after the user moved one control on the device (see relay_listen), give the driver address it is (from list_routes) —…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a destination (input.cc): what the tool writes goes there.
    Description, as the server wrote it
    Teach the catalogue which MIDI message a control really sends: after the user moved one control on the device (see relay_listen), give the driver address it is (from list_routes) — or, for a control the driver lacks, its panel label — and the CC, NRPN or note it sent, with the firmware and the device's Identity Reply when you have them. When several accounts observe the same thing on one firmware the mapping is learned; get_trust shows learned mappings and where they differ from the driver.

    Annotations the server declares

    • title: Report what a control sends
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • report_presetTell SynthHub how a shared preset behaved once loaded on a real device: 'works' (it loaded and sounds as described), 'fails' (refused, wrong sound), or 'factory' (it is a factory p…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.
    Description, as the server wrote it
    Tell SynthHub how a shared preset behaved once loaded on a real device: 'works' (it loaded and sounds as described), 'fails' (refused, wrong sound), or 'factory' (it is a factory preset or someone else's sound: presets that several users flag are hidden until reviewed). Give the firmware.

    Annotations the server declares

    • title: Report on a preset
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • report_resultTell the catalogue how a driver behaved on a real device, after testing it: 'works', 'fails' or 'partial', for the whole driver or one OSC address (from list_routes).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.
    Description, as the server wrote it
    Tell the catalogue how a driver behaved on a real device, after testing it: 'works', 'fails' or 'partial', for the whole driver or one OSC address (from list_routes). Give the firmware version, and the device's reply to the MIDI Identity Request (F0 7E 7F 06 01 F7) as identity_hex when you can: trust is counted per firmware, so a failure on another firmware does not count against the driver, and a report of unknown firmware cannot be placed. Several accounts that agree on one firmware mark the driver usage-verified there; a report that several others contradict is rolled back and puts its account under review. Report only what was actually tested.

    Annotations the server declares

    • title: Report a test result
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • set_profileSet the public profile shown on this account's author page and with its shared presets and comments, instead of its pseudonym alone: display name, link (https), a few words, the pr…No findings

    Why it is in this group

    • The name "set_profile" says "set": a word for a change.
    Description, as the server wrote it
    Set the public profile shown on this account's author page and with its shared presets and comments, instead of its pseudonym alone: display name, link (https), a few words, the presets put first, where they are, more links, their instruments and a README. A field left out stays as it is; an empty one is cleared. Ask the user what they want shown; all of it is public.

    Annotations the server declares

    • title: Set the public profile
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • share_presetShare something the user made on a device with every SynthHub user, under CC BY-SA 4.0: a sound, a sequence or pattern, a kit, a project, a bank of their own sounds, or a MIDI clip…Reads text others writeNo findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Share something the user made on a device with every SynthHub user, under CC BY-SA 4.0: a sound, a sequence or pattern, a kit, a project, a bank of their own sounds, or a MIDI clip any device can play. Its content: the device's own data (SysEx, e.g. from backup_presets), settings by driver address (from list_routes, e.g. {'/filter/cutoff': [90]}, which also works for devices without dumps), and/or a standard MIDI file. Only what the user made: never factory presets, nor sounds or sequences bought or downloaded from others — set own_sound only after asking the user. Made from someone else's shared preset? Pass derived_from: it credits them, as the licence requires. Describe it well (category, genres, tags, tempo, key, tips): that is how people find it. The same content shared twice returns the existing id; the author publishes new versions with update_preset and can withdraw it (withdraw_preset). Through a relay, the device data can be captured from the device itself: pass code and start the dump from the device's menu during the call, or give request_hex (the device's dump-request message, which the user accepts at the relay). An audio preview is added by its author with PUT /u/<account>/v1/presets/<id>/audio (MP3, Ogg, M4A or WebM, 1 MB at most).

    Annotations the server declares

    • title: Share a preset
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • star_presetStar a shared preset for this account, as on GitHub (on: false takes the star back).No findings

    Why it is in this group

    • The name "star_preset" says "star": a word for a change.
    Description, as the server wrote it
    Star a shared preset for this account, as on GitHub (on: false takes the star back). Without id, lists the presets this account starred.

    Annotations the server declares

    • title: Star a preset
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • submit_driverContribute a driver for a device the catalogue lacks (or a better one): the full driver file as a JSON object, in the Open Synth Descriptors format (device.name, device.vendor, dev…Reads text others writeNo findings

    Why it is in this group

    • The name "submit_driver" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Contribute a driver for a device the catalogue lacks (or a better one): the full driver file as a JSON object, in the Open Synth Descriptors format (device.name, device.vendor, device.osc_prefix, and cc_params / params / commands / triggers — see https://synthhub.roomi-fields.com/osd/). It is checked, then merged into the SynthHub catalogue by the merge job if it parses, lints and passes the tests, as its own file of source 'agent-contributed'. Say where the data comes from (manual page, tested on the device).

    Annotations the server declares

    • title: Contribute a driver
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • submit_fixContribute a corrected variant of a driver from what the catalogue learned: where learned mappings (get_trust → mappings, differs: true) disagree with the driver on one firmware, b…Reads text others writeNo findings

    Why it is in this group

    • The name "submit_fix" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Contribute a corrected variant of a driver from what the catalogue learned: where learned mappings (get_trust → mappings, differs: true) disagree with the driver on one firmware, builds a copy of the driver with the learned CC / NRPN numbers, as a new file for that firmware, and queues it for the merge job.

    Annotations the server declares

    • title: Contribute a fix from learned mappings
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • take_soundTake the sound the user's synth is playing — or one of its stored programs — straight from the synth through a relay, with its name.Reads text others writeNo findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Take the sound the user's synth is playing — or one of its stored programs — straight from the synth through a relay, with its name. The synth is found among those SynthHub's librarian can talk to (the KnobKraft Orm adaptations, about 90 synths) by the identity and detect messages, then asked for its sound. The person accepts each step at the relay (finding the synth, asking it): tell them first. To share it: ask the user whether they made this sound themselves (never a factory preset, nor one bought or downloaded), then call share_preset with the device, name, hex, librarian and firmware returned here, and own_sound: true. When several synths answer, or none did, call again with port.

    Annotations the server declares

    • title: Take a synth's sound through a relay
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 7Show 7 read-only tools
  • find_presetsSearch what SynthHub users shared (CC BY-SA 4.0): sounds, sequences, kits, projects, banks, MIDI clips.Reads text others writeNo findings

    Why it is in this group

    • The name "find_presets" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search what SynthHub users shared (CC BY-SA 4.0): sounds, sequences, kits, projects, banks, MIDI clips. Filter by device, kind, category, genre, tag, author (pseudonym) or words; sort by newest, most stars, most loaded into a device or most trusted (confirmed on real devices). Returns, per preset, its id, name, kind, device, description, author, version, whether it has device data, settings, a MIDI file or an audio preview (URL), and its counts. Get one with get_preset.

    Annotations the server declares

    • title: Find presets
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_contributionWhere a contribution stands: pending (waiting for the merge job), merged (with its pull request), rejected (with the reason), or held (its account is under review).Reads text others writeNo findings

    Why it is in this group

    • The name "get_contribution" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "pull request": it reads issues, which other people can write.
    Description, as the server wrote it
    Where a contribution stands: pending (waiting for the merge job), merged (with its pull request), rejected (with the reason), or held (its account is under review).

    Annotations the server declares

    • title: Contribution status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_device_docsFetch the markdown companion documentation for one device, if present.Reads private dataNo findings

    Why it is in this group

    • The name "get_device_docs" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_device_docs" says "get" and "doc": it reads documents.
    Description, as the server wrote it
    Fetch the markdown companion documentation for one device, if present.

    Annotations the server declares

    • title: Get device docs
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_presetOne shared preset in full: its content (SysEx hex, settings by driver address, MIDI file), description and playing tips, versions with their change notes, what it was derived from …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_preset" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    One shared preset in full: its content (SysEx hex, settings by driver address, MIDI file), description and playing tips, versions with their change notes, what it was derived from and its derivatives (remixes), comments, preview URLs, author, licence and attribution line, trust and counts. Load it with load_preset; credit it as the attribution line says when you publish something made from it.

    Annotations the server declares

    • title: Get a preset
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_trustHow far a driver has been confirmed by people who used it, per firmware: status (unreported, unconfirmed, usage-verified, firmware-dependent, failing, disputed), how many users rep…No findings

    Why it is in this group

    • The name "get_trust" says "get": a word for reading.
    Description, as the server wrote it
    How far a driver has been confirmed by people who used it, per firmware: status (unreported, unconfirmed, usage-verified, firmware-dependent, failing, disputed), how many users report it works / fails / partly works, each firmware's own status, the device identities seen for each firmware, and the same per OSC address. needs_firmware: true means reports disagree and some have no firmware — identify the device before reporting (see learn). Check it before relying on a driver, together with its source_tier.

    Annotations the server declares

    • title: Get a driver's trust
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_devicesFind device drivers in the catalogue of synths, drum machines, controllers and DAWs.No findings

    Why it is in this group

    • The name "list_devices" says "list": a word for reading.
    Description, as the server wrote it
    Find device drivers in the catalogue of synths, drum machines, controllers and DAWs. Without arguments it lists them all; `query` keeps drivers whose vendor, name or slug contain every word (e.g. 'korg minilogue'). Returns name, vendor, OSC prefix (slug), kind, source tier and firmware version when the source states one. Pass the slug to list_routes for the full CC/NRPN/SysEx map.

    Annotations the server declares

    • title: List devices
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_routesReturn the OSC routes a device exposes: declarative commands (OSC paths it accepts), cc/nrpn params, sysex params, named note triggers (drum sounds), and reply patterns.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_routes" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "return" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    Return the OSC routes a device exposes: declarative commands (OSC paths it accepts), cc/nrpn params, sysex params, named note triggers (drum sounds), and reply patterns. Use this to discover what a device can do.

    Annotations the server declares

    • title: List device routes
    • readOnlyHint: true
    • 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.

102 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write17
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__osc-bridge__relay_send",
      "mcp__osc-bridge__report_mapping"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 21, 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
22
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
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 22 tools that change things (2 destructive, 2 irreversible, 18 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.synthhub.roomi-fields.com/mcp: tools/list returned 29 tools to an anonymous client, including withdraw_preset (destructive), load_preset (destructive), update_preset (irreversible), relay_send (irreversible), export_device (write) and 17 more

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 22
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed
  2. Nov 7, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 22 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to no
  3. Oct 30, 2026
    • Tools that change things, listed without credentials: 19 to 22

Findings

Matches of fixed checks, with the text they matched.

4 warn1 info
  • The server marks "export_device" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.

    What this check looks for
  • The server marks "relay_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The name "relay_status" says "status": a word for reading.

    What this check looks for
  • The server marks "relay_detect" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "find": a word for reading.

    What this check looks for
  • The server marks "relay_listen" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.

    What this check looks for
  • InfoThe whole server

    The package.json has a "postinstall" script, which npm runs on install.

    Matched text

    scripts.postinstall: "node scripts/postinstall.js"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 22 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 22
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed
  2. Tools1 changed.~1 changedView diff
  3. Tools3 changed.~3 changedView diff
  4. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 22 -> 0 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 22 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to no
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 19 -> 22.View diff
    • Tools that change things, listed without credentials: 19 to 22
  6. Tools4 added, 1 removed, 8 changed.+4 added−1 removed~8 changedView diff
  7. Tools13 added, 13 changed.+13 added~13 changedView diff
  8. Tools2 changed.~2 changedView diff

Install

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

claude mcp add --transport http osc-bridge https://mcp.synthhub.roomi-fields.com/mcp
claude mcp add --transport http osc-bridge https://mcp.synthhub.roomi-fields.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__osc-bridge__list_devices",
      "mcp__osc-bridge__get_device_docs",
      "mcp__osc-bridge__list_routes",
      "mcp__osc-bridge__get_trust",
      "mcp__osc-bridge__get_contribution",
      "mcp__osc-bridge__find_presets",
      "mcp__osc-bridge__get_preset"
    ],
    "ask": [
      "mcp__osc-bridge__export_device",
      "mcp__osc-bridge__report_result",
      "mcp__osc-bridge__report_mapping",
      "mcp__osc-bridge__submit_driver",
      "mcp__osc-bridge__submit_fix",
      "mcp__osc-bridge__share_preset",
      "mcp__osc-bridge__update_preset",
      "mcp__osc-bridge__report_preset",
      "mcp__osc-bridge__comment_preset",
      "mcp__osc-bridge__star_preset",
      "mcp__osc-bridge__preset_collection",
      "mcp__osc-bridge__follow_author",
      "mcp__osc-bridge__set_profile",
      "mcp__osc-bridge__relay_status",
      "mcp__osc-bridge__relay_detect",
      "mcp__osc-bridge__relay_send",
      "mcp__osc-bridge__relay_listen",
      "mcp__osc-bridge__take_sound",
      "mcp__osc-bridge__link_account",
      "mcp__osc-bridge__claim_presets"
    ],
    "deny": [
      "mcp__osc-bridge__withdraw_preset",
      "mcp__osc-bridge__load_preset"
    ]
  }
}

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 osc-bridge. Review it before you use it.

Capability tags behind 19 rules
  • mcp__osc-bridge__get_device_docs private-data
  • mcp__osc-bridge__list_routes private-data, untrusted-input
  • mcp__osc-bridge__report_mapping outbound
  • mcp__osc-bridge__submit_driver untrusted-input
  • mcp__osc-bridge__submit_fix untrusted-input
  • mcp__osc-bridge__get_contribution untrusted-input
  • mcp__osc-bridge__share_preset untrusted-input
  • mcp__osc-bridge__update_preset untrusted-input
  • mcp__osc-bridge__find_presets untrusted-input
  • mcp__osc-bridge__get_preset private-data, untrusted-input
  • mcp__osc-bridge__comment_preset untrusted-input
  • mcp__osc-bridge__relay_status untrusted-input
  • mcp__osc-bridge__relay_detect untrusted-input
  • mcp__osc-bridge__relay_send untrusted-input, outbound
  • mcp__osc-bridge__relay_listen untrusted-input
  • mcp__osc-bridge__take_sound untrusted-input
  • mcp__osc-bridge__load_preset untrusted-input
  • mcp__osc-bridge__link_account untrusted-input
  • mcp__osc-bridge__claim_presets untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.roomi-fields/osc-bridge/verify?hash=d99cfce89c026b8f7c3543f7c710edd4031b4db0edb86a675e98769dd585778c" | jq -e '.changed == false'

Pinned hash d99cfce89c02, from Nov 20, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.roomi-fields/osc-bridge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.roomi-fields/osc-bridge
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.roomi-fields/osc-bridge.svg)](https://radar.anlyon.com/servers/io.github.roomi-fields/osc-bridge)

Source: MCP Registry · repository. Synced Nov 20, 2026, 22:17 UTC.

osc-bridge MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the osc-bridge MCP server safe?

No scan can promise that. What its definitions show: 29 tools, 22 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the osc-bridge MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: withdraw_preset and load_preset.

Can the osc-bridge MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: update_preset and relay_send.

What tools does the osc-bridge MCP server have?

29 tools: 2 destructive, 2 irreversible, 18 write, 7 read. withdraw_preset, load_preset, update_preset, relay_send, export_device, report_result, report_mapping, submit_driver and 21 more.

Does the osc-bridge MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the osc-bridge MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): report_mapping and relay_send.

Has the osc-bridge MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.