Skip to content
MCP server

FIXSIM

Hosted FIX test endpoint and MCP server for trying FIX sessions from AI clients

Answered our latest tool-list check 3 hours ago with 21 tools. It will be marked verified after 3 successful checks in 7 days.

Install
Pricing
Freemium
Platforms
Web, API, CLI
Runs
Remotely
Version
0.1.2
Listing updated
today

Similar MCP servers

About FIXSIM

FIXSIM is a freemium MCP server for finance and payments. It runs as a hosted remote server, so there is nothing to install locally.

The README describes FIXSIM as a hosted FIX protocol simulator that works as a counterparty for testing order flow. Its free Developer Sandbox gives you a live FIX acceptor on the public internet, so you can test connectivity over a real network path instead of only on localhost. You create a session, point your engine at the assigned host, port and CompIDs, and then act as the exchange by filling, partially filling, rejecting or cancelling incoming orders from a blotter.

The MCP server, per the README, lets Claude, Cursor, VS Code or ChatGPT create sandbox sessions, poll messages and drive order responses from a conversation. Paid FIXSIM plans, which the pricing page lists from $500 per month, add persistent sessions, your own CompIDs, automated rules, replay and a REST API for CI use.

The sandbox suits developers and QA engineers validating FIX connectivity and order handling before going to production. Trading firms and OMS/EMS vendors are the audience for the paid tiers.

Install

Run in a terminal

claude mcp add --transport http fixsim https://mcp.fixsim.com/mcp

Add to Settings → Connectors → Add custom connector

https://mcp.fixsim.com/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "fixsim": {
      "url": "https://mcp.fixsim.com/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "fixsim": {
      "type": "http",
      "url": "https://mcp.fixsim.com/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "fixsim": {
      "serverUrl": "https://mcp.fixsim.com/mcp"
    }
  }
}

Add to Grok Bot desktop app → Connect apps → Add a custom connector

https://mcp.fixsim.com/mcp

Enter a Name (for example "FIXSIM"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "fixsim": {
      "type": "http",
      "url": "https://mcp.fixsim.com/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (21)

Read directly from the server.

13 of 21 tools say they're read-only. 1 of 21 tools says it can delete or change data. 7 tools don't say.

From the server's own tool annotations; not verified by us.

fixsim_list_orders_outSays read-only
Orders FIXSIM sent OUT on a session (created with fixsim_send_order). Pass clOrdId to fetch one.
sandbox_get_statusSays read-only
Is the user's FIX engine connected to the sandbox session? Returns state: connected, waiting (nobody logged on yet), disabled, or unknown.
fixsim_send_order
Have FIXSIM send a New Order Single (35=D) OUT on a session to the user's system, so they can test how their system handles inbound orders. Follow up with fixsim_list_orders_out and fixsim_list_executions_in to see what came back.
fixsim_list_orders_inSays read-only
Orders the user's trading system sent INTO FIXSIM on a session (FIXSIM is the counterparty). Includes ClOrdID, symbol, side, quantity, remaining quantity, order status and the raw FIX message. Optionally filter by FIX OrdStatus code (tag 39): 0 new, 1 partially filled, 2 filled, 4 canceled, 8 rejected.
fixsim_list_executions_inSays read-only
Execution reports the user's system sent INTO FIXSIM on a session (when FIXSIM is the order sender and the user's system is the executing side). Optionally filter by ExecID (tag 17).
fixsim_act_on_orders
Respond to orders the user's system sent into FIXSIM: acknowledge, fully or partially execute, reject, cancel remaining, expire, done-for-day, restate, or accept/reject a pending cancel/replace. FIXSIM emits the matching execution reports on the FIX session. Give one or more ClOrdIDs; for executions supply lastPx and, for a partial, lastQty.
sandbox_set_autofill
Turn automatic fills on or off for a sandbox session. On: every order the user sends is filled immediately at the security's last price. Off (default): orders are acknowledged and wait for sandbox_act_on_order.
fixsim_cancel_order_out
Have FIXSIM send an Order Cancel Request (35=F) for an order it previously sent out with fixsim_send_order.
fixsim_list_sessionsSays read-only
List the FIX sessions on an instance with their FIX version, CompIDs, acceptor/initiator role, host/port, enabled and logged-in state, and sequence numbers.
fixsim_list_executions_outSays read-only
Execution reports FIXSIM sent OUT on a session (acks, fills, partial fills, rejects, cancels). Pass clOrdId to see the full execution history of one order: ExecType, OrdStatus, LastPx/LastQty, CumQty, LeavesQty, AvgPx and the raw FIX.
fixsim_get_sessionSays read-only
Get one FIX session's settings and live state (logged in?, sequence numbers, connection details).
sandbox_act_on_order
Play the exchange for one order the user sent in: fill (full execution), partial (partial fill), reject, or cancel (cancel the remaining quantity). FIXSIM sends the matching execution report back to the user's engine.
fixsim_get_order_inSays read-only
Get one inbound order by ClOrdID (tag 11), including its raw FIX message and audit trail. Use this to explain why an order was rejected or what state it is in.
sandbox_get_ordersSays read-only
Working orders the user's engine has sent into the sandbox session: ClOrdID, symbol, side, qty, filled, leaves, price, status.
sandbox_get_messagesSays read-only
The FIX message log for a sandbox session, oldest first: logons, heartbeats, orders in, execution reports out, rejects. Each message has seq, timeUtc, inbound (true = user's engine sent it), msgType, raw FIX, and parsed tag/value fields. Pass afterSeq (the last seq you saw) to fetch only new messages. Use this to explain what happened on the wire.
sandbox_create_session
Create a free, anonymous FIX test session on the FIXSIM Developer Sandbox. No account or API key needed. Returns the connection card: host, port, the SenderCompID the user must put in tag 49, the TargetCompID for tag 56, BeginString, and the expiry (sessions last 4 hours, cap 100 application messages per day). The user's FIX engine connects as the initiator; FIXSIM is the acceptor and acknowledges
sandbox_end_sessionSays it can change data
End a sandbox session now instead of waiting for it to expire. Frees the slot for the user's IP.
fixsim_send_raw_fix
Send one or more raw FIX application messages OUT on a session as given (tag=value pairs separated by | or SOH). FIXSIM supplies the session header fields (BeginString, CompIDs, MsgSeqNum, SendingTime) and the checksum. Use for message types the other tools do not cover.
fixsim_list_instancesSays read-only
List the FIXSIM instances your API key can access. An instance is a hosted FIX engine; each holds one or more FIX sessions. Start here to learn the instance names other tools need.
fixsim_list_securitiesSays read-only
Securities (symbol, last price, CUSIP, ISIN) configured on an instance. FIXSIM prices fills from these.
sandbox_get_sessionSays read-only
Re-fetch a sandbox session's connection card by id, including whether auto-fill is on and when it expires.

What it does

Free hosted FIX sandbox
Create a session in one click and connect any FIX engine to a hosted acceptor with no account or install.
Multiple FIX versions
Supports FIX 4.0, 4.2, 4.4 and 5.0 SP2 over FIXT 1.1.
Live message viewer
Shows each message parsed into readable fields alongside the raw FIX.
Manual counterparty blotter
Fill, partially fill, reject or cancel incoming orders by hand.
AI assistant access via MCP
Sandbox tools can be called from Claude, Cursor, VS Code or ChatGPT through a hosted MCP endpoint.
Paid automation tiers
Paid plans add Rule Builder automation, replay, multiple sessions and a REST API for CI/CD.

Good for

  • Testing a FIX engine's logon and session recovery against a live counterparty
  • Practising order entry, fills and cancels before connecting to production venues
  • Letting an AI assistant create a FIX session and report on logons and orders
  • Running regression tests in CI with the paid REST API

Pricing

Freemium, from $500 a month

Free sandbox; Starter $500/mo, Pro from $1,500/mo, Enterprise custom; 7-day trial

Prices change. Check fixsim.com before you buy.

FIXSIM FAQ

Does the free sandbox require an account?

No. The sandbox requires no signup, email or login; you click to create a session and connect.

What are the sandbox limits?

One session at a time, 100 application messages per day, sessions expire after 4 hours, and nothing persists.

Which FIX versions are supported?

FIX 4.0, 4.2, 4.4 and 5.0 SP2 over FIXT 1.1.

How much do the paid plans cost?

Starter is $500 per month and Pro starts at $1,500 per month; Enterprise pricing is custom. All plans are month-to-month with a 7-day free trial.

Is FIXSIM free?

FIXSIM has a free plan, with paid plans for more usage or features. Paid plans start at $500 a month.

How do I add FIXSIM to Claude Code?

Run this command in your terminal: claude mcp add --transport http fixsim https://mcp.fixsim.com/mcp

What are the best alternatives to FIXSIM?

The closest alternatives to FIXSIM are Fortunest demo, Papertrade, Sdk, Acp Sandbox and FinzData.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Status and tools: checked automatically by AIPoweredBot on 19 November 2026.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers