Diagnose signal timing leakage

Use this when a signal looks good but you suspect leakage or look-ahead and want to know WHY it fails, not just that it fails -- a diagnostic audit, it does not

liveverifiedunknown~5s typical

mcpprobedmcp

$0.0020

per call

plus $0.001 platform fee per run

Open MCP server; Cracked bills routing only

Provider Upstream docs

$Set up https://cracked-ai-pearl.vercel.app/SKILL.md, then use Cracked to run mcp-com-alphaassay-mcp /assay_forensics for me.

Input

Field	Type	Description
signal_events*	array	Signal decisions with the schema-accepted fields {decision_time, symbol, direction, confid
ohlcv_by_symbol*	object	Candles per symbol the events are scored against for the look-ahead / front-loading forens
primary_horizon	integer	Forward horizon in bars the signal claims to predict, for the leakage attribution. default 3
api_key	string	API key for a paid MCP check. Hosted Streamable HTTP clients should send it in the Authori default ""
request_id	string	Optional idempotency key for this paid execution. Retry the same request_id with the same

Call it

curl

curl https://cracked-ai-pearl.vercel.app/v1/run \
  -H "Authorization: Bearer ck_live_..." -H "content-type: application/json" \
  -d '{"provider":"mcp-com-alphaassay-mcp","endpoint":"/assay_forensics","input":{"signal_events":[],"ohlcv_by_symbol":{},"primary_horizon":3,"api_key":""}}'

cli

npx cracked-ai run -p mcp-com-alphaassay-mcp -e /assay_forensics -i '{"signal_events":[],"ohlcv_by_symbol":{},"primary_horizon":3,"api_key":""}'

mcp

run_tool({ provider: "mcp-com-alphaassay-mcp", endpoint: "/assay_forensics", input: {"signal_events":[],"ohlcv_by_symbol":{},"primary_horizon":3,"api_key":""} })

Try it

Runs against your signed-in workspace balance. Sign in if you have not.