Production checklist

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://bump.sh/tie-tech/hub/b2b-api/doc/broker-overview/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "Overview MCP server": {
    "url": "https://bump.sh/tie-tech/hub/b2b-api/doc/broker-overview/mcp"
  }
}

Close
  • [ ] Keys, account IDs, and production/sandbox URLs come from configuration.
  • [ ] Signatures cover the exact method, URI, timestamp, idempotency key, broker and access-key IDs, and body bytes.
  • [ ] Decimals remain {units, nanos} end to end; no binary floats are used.
  • [ ] Every logical command has one persisted Idempotency-Key, reused unchanged only for retries.
  • [ ] Command acceptance is not treated as final order state.
  • [ ] client_order_id is not reused.
  • [ ] /orders, /accounting, and /events persist independent last_applied values and matching filter sets.
  • [ ] Resumable-stream seq gaps are accepted; only duplicates and regressions are dropped.
  • [ ] Reconnects use since within the one-hour replay window.
  • [ ] An accounting resume_too_old stops automatic processing and triggers operational reconciliation.
  • [ ] Market data rebuilds from a snapshot on an md_seq gap.
  • [ ] Regular broker orders are sent only while the market is active.
  • [ ] Position logic supports simultaneous YES and NO holdings when required by the business model.