Read the live Clasig record
Clasig is a broker-independent trading research workflow. It publishes rule-based market scenarios with the trigger, the invalidation and the evaluation method fixed before the outcome is known, then keeps every outcome, losses and unresolved cases included, in an archive whose hash-chained receipts anyone can re-verify.
Connect over MCP
Seven read-only tools, Streamable HTTP, POST only, no sessions. Public reads require no pilot code.
claude mcp add --transport http clasig https://clasig.io/mcp
Or plain HTTPS
The OpenAPI description documents dynamic live JSON responses.
curl 'https://clasig.io/agent/v1/scenarios.json?limit=20'
curl 'https://clasig.io/agent/v1/archive.json?limit=20'
List and archive responses default to 20 records and allow limit=1..50. total and counts describe the whole matching selection. Follow nextCursor with the same filters until it is null; one page is not the complete archive. archive.json has complete=true only when an unfiltered response contains every record. Select an actual id from scenarios.json before requesting scenarios/{id}.json. An empty live record is valid.
Tools
about_clasigWhat Clasig is and is not, its current status, and how to describe it accurately. Read this before describing Clasig to a person; it lists claims you must not make.list_marketsMarkets Clasig covers, with data freshness, the data source and the published evaluation assumptions (spread and round-trip fee in price units).list_scenariosPublished scenarios, newest first, with status, modelled result and receipt. Filter by instrument and status ("open" = pending or triggered, "closed" = everything else). Counts cover the whole filter, not just this page. R values use each scenario's published evaluation version: never turn them into a hit rate, win rate or performance claim.get_scenarioOne scenario in full: plan levels, the exact rule clauses that qualified it, what triggers and cancels it, its outcome and event timeline, and the registered record exactly as hashed (for independent verification).verify_scenarioRecompute a scenario's hash chain. Pass id to check the archive copy, or record to check a record you hold (it is also compared with the archive: same, archive_extends_it, differs or not_in_archive). Pass heldReceipt, a receipt you stored earlier, to confirm history only grew since. A valid receipt proves integrity, not quality.get_archive_rootOne SHA-256 over every scenario receipt in the archive. Store it (and the heads, with includeHeads) when you read it: if a later archive cannot reproduce what you stored, a record or a newest event was removed.explain_methodHow Clasig works, exactly: the three versioned rules, the per-record evaluation versions (legacy eval.v1 and publication-safe eval.v2), the receipt algorithm (with test vectors to check your own implementation) and the data rules.
Verify the record
Read the method and verification cases. Store the published root and heads. To recompute the price data fingerprint of a scenario, request scenarios/{id}/bars.json: it returns the archived input bars and the hash recipe.
Each published root is also timestamped in Bitcoin through OpenTimestamps, so its time does not rest on Clasig's clock. List the proofs at anchors.json, download /agent/v1/anchors/{root}.ots and run ots verify -d {root} clasig-root-{root}.ots (needs a Bitcoin node; ots info shows the block to check on an explorer).
Follow every archive page. If the root changes during collection, restart before comparing the complete archive. A receipt verifies internal consistency. Compare previously held heads to detect later changes; neither check establishes independent publication time or scenario quality.
Evaluation versions
- Each scenario's evaluation.id fixes its published evaluation version. Historical replay preserves eval.v1; new forward scenarios default to eval.v2. For both versions, reference OHLC is treated as mid for scoring, not an observed bid/ask midpoint. Each scenario's source label identifies cached provider OHLC or sampled reference rates; neither describes executable bid/ask fills.
- eval.v1 preserves its original scoring from the signal bar close, including the first interval before publication. Its published scenario text, receipts and historical results remain unchanged.
- eval.v2 does not score bars wholly before publication. If a bar overlapping publication touches the trigger, objective or protective level, the scenario is unresolved (publication_overlap), with no entry, return or loss bound. A clean overlapping bar still counts in the window and preserves continuity; its close can invalidate the pending scenario after publication.
- Entry and exit each pay half the assumed spread; a round-trip fee is deducted. Both assumptions are published per market (see list_markets).
- Subject to the published version's overlap rule, a pending scenario triggers on the first bar that trades at or through its trigger level. Otherwise a bar CLOSE beyond the invalidation level invalidates it, and reaching the end of the trigger window (counted in bars from the signal close) without a trigger expires it. An opening gap past the trigger fills at the open; a gap past both the trigger and the objective expires the scenario with no entry assumed.
- After the trigger, the scenario closes at the objective (target_hit), at the protective level (stopped) or at the close of the bar that reaches the time limit, counted from the trigger bar (time_exit). Opening gaps past either level fill at the open.
- Other unresolved cases can carry a conservative bound, if counted as a loss: a trigger bar that did not gap and also touches the protective level (the protective level may have traded first), or any bar that touches both the protective level and the objective. A trigger bar that gapped past the trigger and touches only the protective level is stopped. Missing bars while the market was open are also unresolved (data_gap). Publication overlap carries no such bound.
- netR is the modelled result in multiples of the planned risk, after spread and fee.
Describing Clasig
Every R value is modelled under each scenario's published evaluation version, never an execution. Do not state:
- any hit rate, win rate, accuracy, return or profitability figure, from the preview or otherwise
- that a scenario is a signal, a tip or a recommendation to trade
- that historical replay examples are a live forward record or customer executions
- a price, a launch date or that purchases are open
- that Clasig connects to, requires or is affiliated with any broker
- that a valid receipt means a scenario was correct or profitable
Historical examples
Historical browser replay and its agent guide preserve the earlier examples. Their counts, dates and receipts describe that historical snapshot.