Overview
Volatility Scaling Lab estimates volatility, computes return and risk metrics, draws charts, and analyzes Monte Carlo results you supply. Despite the name, it does not scale a strategy to a volatility target for you, and it does not generate new simulations. For automated workflows, prefer the single-call EWMA series calculation over the stateful estimators.Connection
MCP URL:https://quantx-api.limex.pro/mcps/volatility-scaling-lab
Select Volatility Scaling Lab in the QuantX marketplace. Use its gateway connection and QuantX authorization; see Client Setup. Supplied-data calculations need no external provider key. Market-data loading depends on Yahoo availability.
Cursor configuration (.cursor/mcp.json):
Tools
Stateful estimator tools:
Use
types-list for constructor signatures. Domain input schemas differ; a table accepted by one tool is not automatically the input to every metric.
Examples
Calculate EWMA From Returns
Callcompute-ewma-volatility-series with synthetic decimal returns:
return_column explicitly; the default is r_risky.
Calculate Geometric Annualized Return
Callcompute-annualized-return:
Calculate Maximum Drawdown
Callcompute-maximum-drawdown with a cumulative wealth index, not period returns:
0.0667 is a 6.67% peak-to-trough decline). Passing period returns such as [0.01, -0.005, 0.002] still returns a number, but it is not a drawdown — compound the returns into a wealth index first.
Results and Limitations
Series, metric tables, and chart payloads may be returned throughresult_id. Retrieve the payload using result_get on this server.
Charts use an image payload with artifact_type: "image", mime: "image/png", and base64 image data. Decode the reported image data after resolving the result. For file export use the artifact tools described in Shared MCP Tools.
Successive -update calls on the same handle accumulate. Prefer compute-ewma-volatility-series when you already have the full series — one call, no sequential state to keep alive.
The estimator tools also accept a call with no handle, but that does not give you an estimator of your own: it falls back to a shared default instance, where -update and -reset from another session land on the same object. Create your own with -create and pass its handle on every call.
There are no volatility-targeting tools here. analyze-monte-carlo-results and compare-strategy-to-monte-carlo read simulation output that you pass in; generate the simulations elsewhere.
Record the return convention, frequency, halflife, sample window, and any missing observations. Pin the end date for reproducible provider requests.