Skip to main content
Glama
Ephemeris MCP server

Ephemeris MCP server

Official

Related Servers

Alternatives to Ephemeris MCP server

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to run TimesFM-3 forecasting workflows locally, including joint multivariate forecasting with known future drivers, backtesting against a baseline, what-if scenario comparison, and historical anomaly detection. It exposes the studio's tools and bundled public and synthetic demo datasets over MCP.
    Apache 2.0

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables zero-shot time-series forecasting locally on CPU by turning numeric series into median and quantile forecasts. It exposes forecast and health tools, with the local forecasting service started on demand.
    Apache 2.0
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables statistical forecasting and anomaly detection over numerical time-series data using Holt linear smoothing, multi-step projections, and variance-based confidence bands.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables agents to inspect time-series data and run typed, budgeted, permissioned forecasts, ensembles, backtests, and guarded SQL using pretrained foundation models and classical baselines. It records every tool call in traces, supports byte-identical replay, and produces stakeholder-readable rationales with inline citations.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables 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.
    1
    MIT

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: forecasting, checking balance, viewing usage, and discovering models. No overlap or ambiguity between them.

Naming Consistency4/5

get_balance, get_usage, and list_models follow a consistent verb_noun pattern, while forecast is a verb-only outlier. Still readable and predictable overall.

Tool Count5/5

Four tools are well-scoped for a forecasting service: one core action plus supporting introspection for credits, usage, and model metadata. Each tool earns its place.

Completeness4/5

Core forecast lifecycle is covered, but there is no way to retrieve a past forecast by request id or cancel an in-progress forecast, which the balance tool hints can exist. Minor gaps an agent can mostly work around.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues