Free · Triage tool
Trade Copier Incident Explainer
Paste a redacted leader/follower timeline. The explainer surfaces probable cause categories and a checklist of the data to inspect with CrossTrade MCP. Useful as a first triage before opening Claude or ChatGPT for a full diagnosis.
What counts as a copier incident
Five common shapes
- Leader filled, follower did not.
- Follower late or out of sync.
- Follower took the wrong quantity.
- Follower took the wrong side.
- Two accounts diverged over a long window without an obvious single event.
Paste the timeline
Input
- Redacted timeline or log snippets. Account names can be aliases.
- Leader account.
- Follower account(s).
- Instrument.
- Approximate time window.
- Intended behavior (what should have happened).
Explanation output
What you get
- Probable cause categories ranked by likelihood given the inputs.
- The MCP data the agent should inspect (per-account orders, executions, activity log, connections, copier settings).
- A short list of questions to ask Claude or ChatGPT to confirm.
- Recommended next steps.
When to use MCP
Pair with logged-in diagnostics
The explainer narrows the search space. The agent path (with mcp:read) confirms with the actual activity log. See the copier diagnostics page for prompts.
FAQ
Frequently asked questions
Does the explainer access my account?
No. It works on the redacted timeline you paste.
Can I run this without MCP?
Yes. The explainer is offline. MCP is for the confirmation step.
What if the issue is configuration?
The explainer flags configuration as a probable cause and points you to the copier settings. The fix happens in CrossTrade's UI.
Triage first, diagnose second
Use the explainer for the first pass. Use MCP for the confirmation.
