io.github.roomi-fields/osc-bridge
osc-bridge
Is the osc-bridge MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.
needs auth probed 2026-11-15 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {"algorithm":"sha256","bits":8,"challenge":"1793706047.8.c1349ad7ee0aad53b1ef0b13.ec23e330bc3945d62e35666a9f9c- Endpoint
- https://mcp.synthhub.roomi-fields.com/mcp (streamable-http)
- Host
- mcp.synthhub.roomi-fields.com
- Package
- The publisher's package npm:@roomi-fields/osc-bridge did not list its tools in the container: crashed on start, MCP error -32000: Connection closed [osc-bridge] native binary not found at: /work/node_modules/@roomi-fields/osc-bridge/vendor/osc-bridge The postinstall dow.
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/roomi-fields/osc-bridge
- Website
- https://synthhub.roomi-fields.com/
- Registry
- active, updated 2026-10-31 · registry entry
- Changes
- 8 recorded, reachable in 7 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention bridge.
- B4 Index ai.benroberts/b4-index · alive
- ai.bridgeapp/bridgeapp · needs auth
- Kaiva Bridge ai.kaiv/bridge · not MCP
- Liquid Agent ai.liquidagent.api/liquid-agent · alive
- BridgeAI br.com.bridgeaibrasil/bridgeai · needs auth
- Bridge Town builders.bridgetown/bridge-town · needs auth
- Superforms co.superforms/superforms · alive
- aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI com.aex402/rpc · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-03 11:30 | needs auth | ||||
| 2026-10-28 10:12 | alive | 696 ms | 29 | 12k | 7.6k |
| 2026-10-27 09:29 | alive | 766 ms | 29 | 12k | 7.4k |
| 2026-10-25 21:32 | alive | 992 ms | 28 | 12k | 7.1k |
| 2026-10-25 08:49 | alive | 1.9 s | 28 | 7.1k | |
| 2026-10-24 08:37 | alive | 1.7 s | 26 | 6.3k | |
| 2026-10-23 09:55 | alive | 992 ms | 13 | 2.9k | |
| 2026-10-20 06:45 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.