Conformance

161 executable conformance checks validate that an implementation's MCP server meets the APEX specification — from core tool semantics through transport resilience and production readiness. The harness runs entirely against live HTTP/SSE endpoints. Four reference implementations pass all checks.

161 Executable Conformance Checks

Seven test suites validate progressive conformance: alpha smoke tests for tool presence and core semantics — including string-decimal wire format and the futures tools — production tests for schema validation and trading-state resilience, and transport tests for HTTP/SSE delivery, session replay, and reconnection.

Four Reference Implementations

TypeScript, Go, Rust, and Java — all four implementations are feature-complete and pass every test. The parity matrix documents executably-verified claims across tools, resources, notifications, and transport.

Production Readiness

Two production capability profiles — Realtime and Autonomous — define requirements beyond the core baseline. The production checklist maps each requirement to executable test coverage with clear gap documentation.

Test Categories

Core 60 checks

Alpha Suite

  • Session authentication and capability negotiation
  • 19 mandatory tool presence and input validation
  • Order lifecycle: place, fill, modify, cancel
  • Market data: quotes, candles, search, details
  • Pre-trade risk checks and kill switch
  • Position close lifecycle
  • String-decimal wire format on prices, money, and quantities
  • Futures: contract chains, margin schedules, root-order rejection
  • Input validation: missing fields, unknown instruments rejected with APEX_4010

Production Suite

  • Normative JSON schema validation (all resources)
  • M1/M5/H1 candle and fills resource verification
  • Stale quote and stale risk rejection
  • Sequence gap injection, detection, and rejection
  • Partial fill lifecycle and kill switch enforcement
Transport 101 checks

Transport Smoke

  • HTTP connection and session management
  • Tool calls over Streamable HTTP
  • SSE notification delivery and APEX envelope validation
  • Session rejection: bogus ID → 404, missing header → 400
  • Version negotiation (apex_version in initialize)

Transport Resilience

  • Last-Event-ID reconnect and replay
  • Event ordering and monotonicity verification
  • Buffer exhaustion via rapid order flood
  • replay_failed notification with last_available_id

Transport Market Data

  • Streaming quote updates over SSE
  • Deterministic candle close testing
  • candle_closed notification payload validation

How to Use the Test Suite

1

Implement

Build your APEX alpha-compatible MCP server using the reference implementations and spec as guides.

2

Run Tests

Point npm run verify:all at your live HTTP endpoint. 161 checks across core, production, and transport suites.

3

Iterate

Fix failures against the executable checks, then validate against the production checklist for capability claims.

4

Ship

Deploy your alpha-compatible APEX MCP server and keep validating it as the protocol evolves.

161 checks. 4 implementations. Open source.

Run the conformance harness locally against your implementation. Validates core tools, production resources, and transport resilience.

View the test suite