Fixie MCP Server
REMOTE · WWW.ONIKORA.COM · SCANNED AUG 3
Parse FIX messages and help agents create Fixie initiators.
Available components
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 →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1081 tokens (~45/item across 24 items; 7 tools + 17 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.onikora.com
claude mcp add --transport http onikora-fix-parser 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 64
First indexed and scored.
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 3 Aug 2026 · Probed https://www.onikora.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| 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 |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.onikora.com/mcp | Verified | 200 | |
| 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.
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.