Fixie MCP Server

io.github.onikoraPublished by GitHub account onikorav1.1.0Updated Oct 24, 2026

Parse FIX messages and help agents create Fixie initiators.

The publisher's own server: Parser Club

VerifiedStreamable HTTPWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that parses FIX protocol messages and helps agents build Fixie initiators for market data, order entry and quote requests.

What you can do
  • Parse raw FIX messages for troubleshooting and inspection
  • Get Fixie initiator recipes for market data, order entry and quote request workflows
  • Generate generic Java initiator source and runtime configuration templates
  • Read human-readable documentation and examples exposed as MCP resources
When to use it
Useful when debugging FIX session traffic or when an assistant needs to scaffold a Fixie initiator, including Java source and runtime configuration, for trading connectivity work.
Requirements
A remote MCP endpoint at the provider's onikora.com host, reached over streamable HTTP; no package, environment variables or headers are declared. Network access to that endpoint is required.
Before you install
Raw FIX messages often contain order, account and counterparty details, so anything pasted for parsing is sent to a third-party server. Generated initiator templates and configuration should be reviewed before use in a live trading environment.

Installation

In SourceWeft

  1. Open Fixie MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.onikora%2Ffix-parser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fixie": {
      "type": "http",
      "url": "https://www.onikora.com/mcp"
    }
  }
}

README

Fixie MCP Registry Files

This directory holds the public MCP Registry metadata that can be pushed to:

  • https://github.com/onikora/mcp-registry

Files:

  • server.json - MCP Registry metadata for the deployed Fixie MCP server
  • USAGE.md - tool, resource, prompt, and usage examples
  • CHANGELOG.md - public metadata change history

Current remote endpoint:

  • https://www.onikora.com/mcp

Why this directory exists:

  • keep public MCP registration metadata separate from the private or broader webapp codebase
  • update the deployed MCP server and the published registry metadata in sync
  • give you a minimal payload to push to the public mcp-registry repository

Sync rule:

  • if the public MCP server URL, version, tool surface, resource surface, prompt surface, or title/description changes, update these files before publishing the new registry metadata

Current scope:

  • parse raw FIX messages for troubleshooting and inspection
  • provide Fixie initiator recipes for market data, order entry, and quote request workflows
  • generate generic Java initiator source and runtime configuration templates
  • expose human-readable docs and examples through MCP resources

Source: README.md at commit 2e2d7bb

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 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 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 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.

Other Parser integrations