sima
Related Servers
Alternatives to sima
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables time series analysis following Box-Jenkins-Treadway methodology, supporting guided or autonomous modes for model identification, estimation, and diagnosis via an LLM.35GPL 2.0
- FlicenseNot gradedqualityCmaintenanceEnables LLM agents to run iterative volatility analytics, from pre-flight statistical gates through GARCH-family model fitting, VaR/ES risk metrics, and Basel backtesting, with a feedback loop guiding each step.-
- AlicenseAqualityBmaintenanceEnables analysts and agents to specify macroeconomic scenarios and portfolio positions, then run Bayesian VAR stress tests and retrieve loss percentiles, expected shortfall, and scenario severity through MCP tools.10144 PyPI5MIT
- AlicenseNot gradedqualityDmaintenanceEnables time-series analysis and forecasting through a structured tool catalogue, including data loading, quality repair, diagnostics, and forecasting with ARIMA, exponential smoothing, Chronos-2, Toto 2.0, and AutoML.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables algorithmic stock trading analysis by combining ARIMA, ARIMA-GARCH, and XGBoost models to generate buy/sell/hold signals with risk management, portfolio comparison, and volatility analysis for various market sectors.1-
- AlicenseNot gradedqualityDmaintenanceMCP server that drives EViews econometrics software from Python or LLM clients via COM automation, enabling workfile creation, model estimation, diagnostics, and data exchange with pandas.1MIT
TDQS
Scored across 44 tools
The staged workflow gives most tools distinct roles, but several near-parallel tools are easy to confuse: load_data/load_pre/split_inp for entry, estimate/estimate_vec for model class, identify_cross/matrices/echelon for identification, and evaluate/forecast_uncertainty for comparison. The long, high-context descriptions help, but selection still depends on knowing the analyst's current route and model state.
Names are consistently snake_case with recognizable prefixes such as load_, plot_, identify_, and job_. The grammar varies between verb-only, noun-only, and verb_noun forms, but the convention remains readable and predictable overall.
Forty-four tools is very heavy for a single MCP server, even one modeling a full econometric workflow. Many tools map to legitimate stages, but the surface is large enough to overwhelm selection and orchestration without a higher-level workflow wrapper.
The surface covers the major lifecycle: raw/univariate entry, gating, identification, estimation, VEC analysis, forecasting, diagnostics, plotting, jobs, decisions, and export. Minor gaps remain around explicit session/model-state inspection and standalone handling of some implicitly parameterized actions such as set/adopt.