Skip to content

FIXSIM MCP server

io.github.GammaThreeTrading/fixsimGammaThreeTradingstreamable-httpv0.1.2Scanned

Test FIX from Claude, ChatGPT, or Cursor: free sandbox FIX sessions or your own FIXSIM instances.

21 tools: 2 can delete or cancel things, 2 do something that can't be undone, 4 change things and 13 only read.

Tools: 2 delete, 2 irreversible, 4 write, 13 read.
  • Reads private data · 2
  • Reads text others write · 2
  • Can send data out · 2
  • 1 finding

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 FIXSIM MCP server can do

The FIXSIM MCP server is published by the GitHub account GammaThreeTrading. It has 21 tools. It can delete or cancel things (2 tools: fixsim_cancel_order_out and sandbox_end_session), do things that cannot be undone, such as sending, paying or publishing (fixsim_send_order and fixsim_send_raw_fix) and create or change data (4 tools: fixsim_act_on_orders, sandbox_set_autofill, sandbox_act_on_order and sandbox_create_session). 13 tools only read.

2 tools read private data (fixsim_get_order_in and sandbox_get_messages); 2 tools bring in text other people can write (fixsim_get_order_in and sandbox_get_messages); 2 tools can send data out of your system (fixsim_send_order and fixsim_send_raw_fix). 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 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.1.2.

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.

21 tools

Deletes or cancels 2Claude Code: deny
  • fixsim_cancel_order_outHave FIXSIM send an Order Cancel Request (35=F) for an order it previously sent out with fixsim_send_order.1 finding

    Why it is in this group

    • The name "fixsim_cancel_order_out" says "cancel": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "fixsim_cancel_order_out" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"destructiveHint":false}; The name "fixsim_cancel_order_out" says "cancel": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Have FIXSIM send an Order Cancel Request (35=F) for an order it previously sent out with fixsim_send_order.

    Annotations the server declares

    • title: Send an Order Cancel Request
    • destructiveHint: false
  • sandbox_end_sessionEnd a sandbox session now instead of waiting for it to expire.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.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    End a sandbox session now instead of waiting for it to expire. Frees the slot for the user's IP.

    Annotations the server declares

    • title: End sandbox session
    • destructiveHint: true
Can't be undone 2Claude Code: ask
  • fixsim_send_orderHave 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.Can send data outNo findings

    Why it is in this group

    • The name "fixsim_send_order" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "fixsim_send_order" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send a New Order Single
    • destructiveHint: false
  • fixsim_send_raw_fixSend one or more raw FIX application messages OUT on a session as given (tag=value pairs separated by | or SOH).Can send data outNo findings

    Why it is in this group

    • The name "fixsim_send_raw_fix" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "fixsim_send_raw_fix" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send raw FIX messages
    • destructiveHint: false
Changes things 4Claude Code: ask
  • fixsim_act_on_ordersRespond 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 c…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
    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.

    Annotations the server declares

    • title: Act on inbound orders
    • destructiveHint: false
  • sandbox_act_on_orderPlay the exchange for one order the user sent in: fill (full execution), partial (partial fill), reject, or cancel (cancel the remaining quantity).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
    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.

    Annotations the server declares

    • title: Fill, reject, or cancel a sandbox order
    • destructiveHint: false
  • sandbox_create_sessionCreate a free, anonymous FIX test session on the FIXSIM Developer Sandbox.No findings

    Why it is in this group

    • The name "sandbox_create_session" says "create": a word for a change.
    Description, as the server wrote it
    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 every order. Keep the returned id; every other sandbox tool needs it.

    Annotations the server declares

    • title: Create sandbox FIX session
    • destructiveHint: false
  • sandbox_set_autofillTurn automatic fills on or off for a sandbox session.No findings

    Why it is in this group

    • The name "sandbox_set_autofill" says "set": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Set sandbox auto-fill
    • destructiveHint: false
Only reads 13Show 13 read-only tools
  • fixsim_get_order_inGet one inbound order by ClOrdID (tag 11), including its raw FIX message and audit trail.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "get" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "get" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get inbound order
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_get_sessionGet one FIX session's settings and live state (logged in?, sequence numbers, connection details).No findings

    Why it is in this group

    • The name "fixsim_get_session" says "get": a word for reading.
    Description, as the server wrote it
    Get one FIX session's settings and live state (logged in?, sequence numbers, connection details).

    Annotations the server declares

    • title: Get FIX session
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_list_executions_inExecution 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).No findings

    Why it is in this group

    • The name "fixsim_list_executions_in" says "list": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: List inbound execution reports
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_list_executions_outExecution reports FIXSIM sent OUT on a session (acks, fills, partial fills, rejects, cancels).No findings

    Why it is in this group

    • The name "fixsim_list_executions_out" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List outbound execution reports
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_list_instancesList the FIXSIM instances your API key can access.No findings

    Why it is in this group

    • The name "fixsim_list_instances" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List FIXSIM instances
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_list_orders_inOrders the user's trading system sent INTO FIXSIM on a session (FIXSIM is the counterparty).No findings

    Why it is in this group

    • The name "fixsim_list_orders_in" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List inbound orders
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_list_orders_outOrders FIXSIM sent OUT on a session (created with fixsim_send_order).No findings

    Why it is in this group

    • The name "fixsim_list_orders_out" says "list": a word for reading.
    Description, as the server wrote it
    Orders FIXSIM sent OUT on a session (created with fixsim_send_order). Pass clOrdId to fetch one.

    Annotations the server declares

    • title: List outbound orders
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_list_securitiesSecurities (symbol, last price, CUSIP, ISIN) configured on an instance.No findings

    Why it is in this group

    • The name "fixsim_list_securities" says "list": a word for reading.
    Description, as the server wrote it
    Securities (symbol, last price, CUSIP, ISIN) configured on an instance. FIXSIM prices fills from these.

    Annotations the server declares

    • title: List securities
    • idempotentHint: true
    • readOnlyHint: true
  • fixsim_list_sessionsList the FIX sessions on an instance with their FIX version, CompIDs, acceptor/initiator role, host/port, enabled and logged-in state, and sequence numbers.No findings

    Why it is in this group

    • The name "fixsim_list_sessions" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List FIX sessions
    • idempotentHint: true
    • readOnlyHint: true
  • sandbox_get_messagesThe FIX message log for a sandbox session, oldest first: logons, heartbeats, orders in, execution reports out, rejects.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "sandbox_get_messages" says "get" and "message": it reads messages.
    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe name "sandbox_get_messages" says "get" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read sandbox FIX message log
    • idempotentHint: true
    • readOnlyHint: true
  • sandbox_get_ordersWorking orders the user's engine has sent into the sandbox session: ClOrdID, symbol, side, qty, filled, leaves, price, status.No findings

    Why it is in this group

    • The name "sandbox_get_orders" says "get": a word for reading.
    Description, as the server wrote it
    Working orders the user's engine has sent into the sandbox session: ClOrdID, symbol, side, qty, filled, leaves, price, status.

    Annotations the server declares

    • title: List sandbox orders
    • idempotentHint: true
    • readOnlyHint: true
  • sandbox_get_sessionRe-fetch a sandbox session's connection card by id, including whether auto-fill is on and when it expires.No findings

    Why it is in this group

    • The name "sandbox_get_session" says "get": a word for reading.
    Description, as the server wrote it
    Re-fetch a sandbox session's connection card by id, including whether auto-fill is on and when it expires.

    Annotations the server declares

    • title: Get sandbox session
    • idempotentHint: true
    • readOnlyHint: true
  • sandbox_get_statusIs the user's FIX engine connected to the sandbox session?No findings

    Why it is in this group

    • The name "sandbox_get_status" says "get": a word for reading.
    Description, as the server wrote it
    Is the user's FIX engine connected to the sandbox session? Returns state: connected, waiting (nobody logged on yet), disabled, or unknown.

    Annotations the server declares

    • title: Check sandbox connection status
    • idempotentHint: true
    • readOnlyHint: true

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.

8 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 data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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__fixsim__fixsim_send_order",
      "mcp__fixsim__fixsim_send_raw_fix"
    ]
  }
}

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 20, 2026, 18:58 UTC, unchanged since Oct 22, 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
8
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 8 tools that change things (2 destructive, 2 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.fixsim.com/mcp: tools/list returned 21 tools to an anonymous client, including fixsim_cancel_order_out (destructive), sandbox_end_session (destructive), fixsim_send_order (irreversible), fixsim_send_raw_fix (irreversible), fixsim_act_on_orders (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "fixsim_cancel_order_out" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"destructiveHint":false}; The name "fixsim_cancel_order_out" says "cancel": a word for removing or ending something.

    What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http fixsim https://mcp.fixsim.com/mcp
claude mcp add --transport http fixsim https://mcp.fixsim.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__fixsim__fixsim_list_orders_out",
      "mcp__fixsim__sandbox_get_status",
      "mcp__fixsim__fixsim_list_orders_in",
      "mcp__fixsim__fixsim_list_executions_in",
      "mcp__fixsim__fixsim_list_sessions",
      "mcp__fixsim__fixsim_list_executions_out",
      "mcp__fixsim__fixsim_get_session",
      "mcp__fixsim__fixsim_get_order_in",
      "mcp__fixsim__sandbox_get_orders",
      "mcp__fixsim__sandbox_get_messages",
      "mcp__fixsim__fixsim_list_instances",
      "mcp__fixsim__fixsim_list_securities",
      "mcp__fixsim__sandbox_get_session"
    ],
    "ask": [
      "mcp__fixsim__fixsim_send_order",
      "mcp__fixsim__fixsim_act_on_orders",
      "mcp__fixsim__sandbox_set_autofill",
      "mcp__fixsim__sandbox_act_on_order",
      "mcp__fixsim__sandbox_create_session",
      "mcp__fixsim__fixsim_send_raw_fix"
    ],
    "deny": [
      "mcp__fixsim__fixsim_cancel_order_out",
      "mcp__fixsim__sandbox_end_session"
    ]
  }
}

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

Capability tags behind 4 rules
  • mcp__fixsim__fixsim_send_order outbound
  • mcp__fixsim__fixsim_get_order_in private-data, untrusted-input
  • mcp__fixsim__sandbox_get_messages private-data, untrusted-input
  • mcp__fixsim__fixsim_send_raw_fix outbound

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.GammaThreeTrading/fixsim/verify?hash=21ead2a1a7cd37441b60bab390f4931dbeff2d1124d5172d291be64696dd148a" | jq -e '.changed == false'

Pinned hash 21ead2a1a7cd, from Nov 15, 2026, 20: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.GammaThreeTrading/fixsim/changes.xml

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

Badge

Anlyon Radar badge for io.github.GammaThreeTrading/fixsim
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.GammaThreeTrading/fixsim.svg)](https://radar.anlyon.com/servers/io.github.GammaThreeTrading/fixsim)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.

FIXSIM MCP server: questions and answers

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

Is the FIXSIM MCP server safe?

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

Can the FIXSIM MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: fixsim_cancel_order_out and sandbox_end_session.

Can the FIXSIM MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: fixsim_send_order and fixsim_send_raw_fix.

What tools does the FIXSIM MCP server have?

21 tools: 2 destructive, 2 irreversible, 4 write, 13 read. fixsim_cancel_order_out, sandbox_end_session, fixsim_send_order, fixsim_send_raw_fix, fixsim_act_on_orders, sandbox_set_autofill, sandbox_act_on_order, sandbox_create_session and 13 more.

Does the FIXSIM MCP server need sign-in or OAuth?

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

Does the FIXSIM 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): fixsim_send_order and fixsim_send_raw_fix.

Has the FIXSIM MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.