
Fix Bridge Mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv0.1.2Updated Oct 30, 2026
FIX trading-protocol bridge — parse, map, govern (MiFID II / MAR).
Overview
Local Python MCP server that bridges FIX trading messages, letting an assistant parse FIX, map them to a modern format, and apply trade governance checks.
- What you can do
- Parse FIX trading-protocol messages
- Map parsed FIX messages to a modern representation
- Apply trade governance checks tied to MiFID II, best execution and MAR
- Bridge FIX traffic into the provider's ONE OS layer
- When to use it
- Useful when an assistant needs to inspect or interpret raw FIX trading messages, convert them into a modern format, or run regulatory-style governance checks on trades. It suits teams working with FIX order and execution flows rather than general-purpose use.
- Requirements
- Runs as a local process over stdio, installed from the PyPI package fix-bridge-mcp and started with Python. No authentication, environment variables or headers are declared. Desktop only; not web executable.
Installation
In SourceWeft
- Open Fix Bridge Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
fix-bridge-mcp
mcp-name: io.github.CSOAI-ORG/fix-bridge-mcp
Part of the CSOAI Layer-0 legacy-bridge family. Bridge FIX trading messages to ONE OS — parse, map, govern (MiFID II / best execution / MAR).
Tools: parse_fix · map_to_modern · govern_trade
Source: README.md at commit 72511a1
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.