This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Official Model Context Protocol (MCP) server and deterministic reference client for OrbitCompute.ai, publisher of the OCEI™ v2.2 (Orbital Compute Efficiency Index).
Provides cryptographically attested (RFC 8785 JSON Canonicalization + ECDSA P-256 ES256) real-time evaluations comparing orbital AI compute shells (650 km Dawn-Dusk SSO, 320 km VLEO Edge, 550 km LEO, 1,500 km MEO) against Terrestrial Tier-IV Utility Grids using 6 live NOAA SWPC & GOES satellite telemetry streams.
Interactive Control Room & Multi-Physics Simulator: https://orbitcompute.ai
Formal Mathematical Specification & CODATA Registry: https://orbitcompute.ai/ocei
Token-Optimized Markdown Spec (for LLMs): https://orbitcompute.ai/ocei.md
Live Attested JSON Feed: https://orbitcompute.ai/v1/index/ocei
Ultra-Compact M2M Feed (<160 Tokens): https://orbitcompute.ai/v1/index/ocei?format=compact
Global Verification Public Key (JWKS): https://orbitcompute.ai/.well-known/jwks.json
OpenAPI 3.1.0 Specification: https://orbitcompute.ai/v1/openapi.json
Related MCP server: omni-ai-routing-engine
evaluate_orbital_compute_regime: Computes live OCEI-Spot, OCEI-Structural, and 60m-TWAP scores, L1 solar-wind shockwave lead time (+25 to +62 min), solar beta-angle ($\beta$) eclipse battery mass, 2-sided Stefan-Boltzmann radiator area with Earth IR/albedo view-factor absorption, Silicon $T_j$ thermal throttling, 25-MW fault-domain Young-Daly SEU checkpoint intervals, and WACC-adjusted $/1M Token unit economics.
compute_arbitrage_dispatch: Evaluates real-time terrestrial electricity spot prices ($/MWh) against the orbital breakeven threshold to output an attested workload routing signal (ORBIT_PRIMARY, HYBRID_SPLIT, or TERRESTRIAL_PRIMARY).
solve_optimal_workload_allocation: Deterministic constraint solver returning the optimal percentage split across SSO-650, VLEO-320, and Terrestrial-Spot based on workload class and latency tolerance.
{
"mcpServers": {
"ocei-oracle": {
"url": "[https://orbitcompute.ai/mcp](https://orbitcompute.ai/mcp)"
}
}
}Evaluates real-time spot electricity price ($/MWh) against the orbital breakeven threshold to output a deterministic workload routing directive (ORBIT_PRIMARY, HYBRID_SPLIT, or TERRESTRIAL_PRIMARY).
Inputs: grid_price_usd_mwh (required), hw, power_mw, storm_mode.
Invoke before scheduling batch AI training/inference or evaluating orbital vs. terrestrial compute TCO. Computes OCEI v2.2 Spot/Structural/TWAP scores, L1 shockwave lead time, beta-angle eclipse battery mass, Earth IR/albedo radiator sizing, Silicon Tj throttling, Young-Daly SEU checkpointing, and $/MTok unit economics.
Inputs: hw, beta_deg, power_mw, storm_mode, +3 more.
Deterministic constraint solver returning the optimal percentage split across 650 km Dawn-Dusk SSO, 320 km VLEO Edge, and Terrestrial Spot Grids based on workload class, max latency tolerance (ms), and electricity spot price.
Inputs: storm_mode, workload_type, max_latency_ms, grid_price_usd_mwh.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
The three tools cover related but overlapping decisions: evaluate_orbital_compute_regime already assesses orbital vs. terrestrial viability, while compute_arbitrage_dispatch and solve_optimal_workload_allocation both output routing/allocation decisions (the former a coarse 3-way directive, the latter a percentage split). An agent could plausibly reach for either of the latter two, or start with the evaluator, without a clear rule for ordering. Descriptions help, but boundaries between 'dispatch' and 'allocate' remain fuzzy.
All three names are snake_case and verb-led (evaluate_, compute_, solve_), giving a predictable pattern. Minor deviation: compute_arbitrage_dispatch reads awkwardly (verb + noun-phrase 'arbitrage_dispatch') compared to the cleaner verb_object form of the other two, but the convention is still recognizably consistent.
Three tools is tightly scoped to a narrow analytical domain (orbital compute economics), and each maps to a distinct decision stage: evaluation, real-time arbitrage, and allocation optimization. It is on the lean side for the breadth of physics and economics mentioned, but nothing feels gratuitous.
The surface covers the core lifecycle — assess the regime, decide routing from spot prices, and solve for an optimal split — with no obvious dead ends for the stated purpose. Gaps are minor: there is no tool to inspect or override model constants/thresholds, nor a what-if/sensitivity or report-explanation operation, which an agent may want after getting scores.
Orbital data center & space AI compute tracker MCP: projects, launches, orbits, alerts. 100 free/day
Space weather: Kp index, solar flare flux, alerts. $0.01/query, free testnet funds.
PJM/MISO energy arbitrage. Intel TDX attested, on-chain every 60 min. MCP tools for AI agents.
Environmental intelligence for AI agents — climate, carbon, methane. Quote-first, prepaid.
