Ext Ops Panel
Open dashboard
Comparison

io.github.CSOAI-ORG/fix-bridge-mcp vs canary ibkr MCP

io.github.CSOAI-ORG/fix-bridge-mcp is an MCP server published by CSOAI-ORG. Marketplaces we read that list it: 1 (Official MCP Registry). canary ibkr MCP is an MCP server published by osauer. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.CSOAI-ORG/fix-bridge-mcpcanary ibkr MCP
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (PyPI): 105
Downloads/week (PyPI): 28
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed, marked deprecated
Version: 2.3.1
Forks (GitHub): 2
Stars (GitHub): 8
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.CSOAI-ORG/fix-bridge-mcp vs canary ibkr MCP
Factio.github.CSOAI-ORG/fix-bridge-mcpcanary ibkr MCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)8 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (fix-bridge-mcp)On your machine (https://github.com/osauer/ibkr/releases/download/v2.3.1/ibkr-v2.3.1.mcpb)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/csoai-org/fix-bridge-mcpgithub.com/osauer/ibkr
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.CSOAI-ORG/fix-bridge-mcp

In its own words, on Official MCP Registry:

FIX trading-protocol bridge — parse, map, govern (MiFID II / MAR).

canary ibkr MCP

In its own words, on Official MCP Registry:

Local IBKR MCP server for agentic trading desks: market data, portfolio context, risk checks.

How to run each

io.github.CSOAI-ORG/fix-bridge-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio fix-bridge-mcp -- uvx fix-bridge-mcp

canary ibkr MCP

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.CSOAI-ORG/fix-bridge-mcp · What it can do: canary ibkr MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built