← All engines

RUST ENGINE / kepler_stability

Kepler orbital sensitivity map

Survey a bounded grid of initial orbits in a planar Sun–Jupiter model, with finite-window sensitivity, integrated durations and numerical diagnostics.

Open the kepler_stability demonstration ↗Try the live calculation ↗Connect an AI assistant →

What does a real call return?

All 8 requested cells completed with 8 in the low-sensitivity band, using 38,400 integration steps. This describes a 150-year window, not long-term stability.

Recorded on 2 November 2026 through the public MCP endpoint, service release 0.17.1. Inputs and full responses, response SHA-256 ace09f733ad5…. Verdict values are the literal values the tool returns. Run the same inputs yourself to compare; elapsed times vary, and a new release may change the figures.

Checked against

Recorded on release 0.16.1. These checks cover the listed cases, not every input. Evidence cards.

How it works

A fourth-order Yoshida composition of Wisdom–Holman splitting advances two nearby trajectories using a universal-variable Kepler drift. Renormalized phase-space separation gives a finite-window sensitivity indicator. A sampled Jacobi invariant diagnostic and close-encounter guards identify unresolved numerical cases.

Inputs and units

Choose semi-major axes in AU within 1.5–5.6, eccentricities 0–0.7, a 2–64 by 2–64 grid limited to 512 cells, a 50–5000 year window and 8–128 steps per year. Declare the initial perihelion phase, Jupiter mass ratio and orbital radius. The global budget reserves at most four million integration steps.

What the result contains

One entry per requested cell: heuristic low/moderate/high sensitivity or explicit encounter, numerical-warning, failure and uncomputed statuses. Results include actual integrated years, stopping reason, eccentricity maximum, phase-space growth, sampled relative Jacobi drift and osculating radial overlap when available. Reserved and completed work are separate counters.

Example MCP call

{
  "name": "kepler_stability",
  "arguments": {
    "a_min_au": 2.6,
    "a_max_au": 2.8,
    "e_min": 0,
    "e_max": 0.05,
    "n_a": 4,
    "n_e": 2,
    "duration_yr": 150,
    "steps_per_year": 32,
    "initial_phase_deg": 0,
    "max_work_units": 200000
  }
}

Send this tool name and arguments through a connected MCP client. Discover the authoritative input schema with tools/list.

Call this engine in one command

Node.js 20+ and npm. This downloads a small remote MCP client; it does not install the engine locally.

npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call kepler_stability --arguments '{"a_min_au":2.6,"a_max_au":2.8,"e_min":0,"e_max":0.05,"n_a":4,"n_e":2,"duration_yr":150,"steps_per_year":32,"initial_phase_deg":0,"max_work_units":200000}'

Client download, PowerShell input and verification →

Direct MCP access

kepler_stability is independently callable. It is deliberately not connected to the automatic planner, so nothing passes its results to another engine for you. Two tools returning similar JSON fields does not mean their results are compatible.

Cite this engine

Version 0.2.0, source SHA-256 eb4e3a0ad16d…. Evidence recorded on release 0.16.1; the public service currently runs 0.17.1. Replace the access date when you cite it.

ScoreCompute. Kepler orbital sensitivity map (kepler_stability), version 0.2.0, source SHA-256 eb4e3a0ad16db9767578512de36d5e5f38110d8881c20465a8c7ca46dc0b2841. Evidence release 0.16.1, service release 0.17.1. https://scorecompute.com/engines/kepler-stability/ (accessed YYYY-MM-DD).

All engine citations · Evidence card

Execution and availability

ScoreCompute exposes this tool through MCP Streamable HTTP. Rust computation runs on a connected worker; the public website and MCP gateway run separately. Among these 22 scientific tools, CUDA is implemented for simulate_pi; the other scientific engines run on CPU. The separate contributor network runs two compiled public workloads: a π estimate and fixed synthetic schedule probes. Requests are bounded and concurrent work may be refused when capacity is occupied.

Record inputs, assumptions and returned provenance when sharing a result. The public observatory displays software client names and tool activity, without publishing calculation arguments or results.

Explore another engine →Agent-readable overview ↗

Sources

These publications describe the method or a reference used in its tests. Citing them does not certify this implementation.

First published 1 October 2026 · Last updated 2 November 2026