Fixie MCP Server
REMOTE · WWW.ONIKORA.COM · SCANNED SEP 1
Parse FIX messages and help agents create Fixie initiators.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security3
- TLS check failed: the certificate is expired or not yet valid (as of 2026-08-26). See how to fix → View diagnostics → Fail
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 400, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the TLS certificate failed verification. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Fixie MCP Server server?
Fixie MCP Server is a hosted endpoint at https://www.onikora.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.onikora.com
claude mcp add --transport http onikora-fix-parser 'https://www.onikora.com/mcp'
{
"mcpServers": {
"onikora-fix-parser": {
"url": "https://www.onikora.com/mcp"
}
}
} {
"servers": {
"onikora-fix-parser": {
"type": "http",
"url": "https://www.onikora.com/mcp"
}
}
} [mcp_servers.onikora-fix-parser] url = "https://www.onikora.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"onikora-fix-parser": {
"type": "remote",
"url": "https://www.onikora.com/mcp",
"enabled": true
}
}
} openclaw mcp add onikora-fix-parser --url 'https://www.onikora.com/mcp' --transport streamable-http
mcp_servers:
onikora-fix-parser:
url: "https://www.onikora.com/mcp" {
"McpServers": {
"onikora-fix-parser": {
"Transport": "http",
"Url": "https://www.onikora.com/mcp"
}
}
} assistant mcp add onikora-fix-parser -t streamable-http -u 'https://www.onikora.com/mcp'
{
"mcpServers": {
"onikora-fix-parser": {
"type": "http",
"url": "https://www.onikora.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 27 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 1 Sept 2026 · Probed https://www.onikora.com/mcp
TLS invalid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
Chain error: expired
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=charlottebadminton.org | CN=E7,O=Let's Encrypt,C=US | 28 May 2026 | 26 Aug 2026 | ECDSA 256 | ECDSA-SHA384 | 59c6ab01455f6853257521c599983477a79 |
| SANs: charlottebadminton.org, jdpumps.in, maharaniindiancuisine.com, onikora.com, www.charlottebadminton.org, www.jdpumps.in, www.maharaniindiancuisine.com, www.onikora.com | ||||||
| CN=E7,O=Let's Encrypt,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 Mar 2024 | 12 Mar 2027 | ECDSA 384 | SHA256-RSA | aa75f1e62b8f0a220966d38bbfd4baa1 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.onikora.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onikora.com. | present | 13760 | 8 | Verified |
| www.onikora.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.onikora.com/mcp | TLS failed | ||
| http (plaintext) | http://www.onikora.com/mcp | Inconclusive | 400 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_initiator_source Generate Fixie Initiator Source ~74
Generates generic Java source for a managed or standalone Fixie initiator.
| Name | Type | Req | Description |
|---|---|---|---|
| class_name | string | – | Java class name |
| package_name | string | – | Java package name |
| style | string | – | managed or standalone |
| use_case | string | – | market_data, order_entry, or quote_request |
No output schema declared.
No examples provided.
generate_runtime_config Generate Fixie Runtime Config ~109
Generates a runtime configuration entry for a Fixie initiator.
| Name | Type | Req | Description |
|---|---|---|---|
| class_name | string | – | Fully qualified Java class name |
| host | string | – | Acceptor host |
| name | string | – | Runtime entry name |
| port | string | – | Acceptor port |
| senderCompId | string | – | Initiator SenderCompID |
| targetCompId | string | – | Acceptor TargetCompID |
| use_case | string | – | market_data, order_entry, or quote_request |
No output schema declared.
No examples provided.
get_initiator_recipe Get Fixie Initiator Recipe ~79
Returns the recommended Fixie initiator pattern for market_data, order_entry, or quote_request.
| Name | Type | Req | Description |
|---|---|---|---|
| fix_version | string | – | FIX version, defaults to FIX.4.4 |
| style | string | – | managed or standalone; managed is recommended |
| use_case | string | – | market_data, order_entry, or quote_request |
No output schema declared.
No examples provided.
get_runtime_config_template Get Fixie Runtime Config Template ~88
Returns a JSON runtime configuration template for a Fixie initiator.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Acceptor host |
| port | string | – | Acceptor port |
| senderCompId | string | – | Initiator SenderCompID |
| targetCompId | string | – | Acceptor TargetCompID |
| use_case | string | – | market_data, order_entry, or quote_request |
No output schema declared.
No examples provided.
parse_fix_message Parse FIX Message ~128
Use this tool whenever you see one raw FIX message string, typically starting with 8=FIX. The input may use pipe (|) or SOH separators. By default it returns only the human-readable hierarchical output. Set type=tags to return only the hierarchical FIX field/tag view.
| Name | Type | Req | Description |
|---|---|---|---|
| raw_message | string | yes | The raw FIX message. The tool accepts either pipe separators or SOH separators. |
| type | string | – | Optional override for single-message parsing. Omit it to return the default human-readable output. Use "tags" to return the hierarchical FIX field/tag output only. |
No output schema declared.
No examples provided.
parse_fix_messages Parse FIX Messages ~130
Use this tool whenever you see multiple raw FIX messages that need to be parsed in order. Each message typically starts with 8=FIX and may use pipe (|) or SOH separators. Returns ordered Onikora UFO, FFO, and optional sequence output.
| Name | Type | Req | Description |
|---|---|---|---|
| messages | array | yes | Ordered list of raw FIX messages. |
| outputs | array | – | Optional outputs to include. Defaults to ["ufo", "ffo"]. "ufo" is the human-readable hierarchical output. "ffo" is the hierarchical FIX field/tag output. "sequence" is the ordered sequence-row view. |
No output schema declared.
No examples provided.
validate_initiator_spec Validate Fixie Initiator Spec ~92
Checks whether the initiator request has enough information to generate useful Fixie code.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Acceptor host |
| port | string | – | Acceptor port |
| senderCompId | string | – | Initiator SenderCompID |
| targetCompId | string | – | Acceptor TargetCompID |
| use_case | string | – | market_data, order_entry, or quote_request |
No output schema declared.
No examples provided.
What is the Fixie MCP Server server?
Fixie MCP Server is listed in the public MCP registry as io.github.onikora/fix-parser. Parse FIX messages and help agents create Fixie initiators. This page covers its hosted endpoint (https://www.onikora.com/mcp).
What tools does the Fixie MCP Server server expose?
Fixie MCP Server exposes 7 tools: parse_fix_message, parse_fix_messages, get_initiator_recipe, get_runtime_config_template, generate_initiator_source, and 2 more. Their descriptions and schemas cost roughly 700 tokens of context every time the server is loaded.
Does the Fixie MCP Server server require authentication?
Its publisher declares no required credentials for Fixie MCP Server. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Fixie MCP Server server still maintained?
Fixie MCP Server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 25 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.