# onikora FIX Parser [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/onikora/mcp-registry  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/onikora-fix-parser

## Description
Remote MCP server for parsing FIX messages into UFO, FFE, and sequence outputs.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "onikora-fix-parser": {
    "command": "npx",
    "args": ["-y","onikora-fix-parser"]
  }
}
```

## Documentation & 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