# OCEI v2.2 Orbital Compute & Arbitrage Oracle (remote · orbitcompute.ai)

Attested orbital AI compute physics, NOAA space-weather & $/MTok arbitrage oracle (OCEI v2.2).

- Trust score: 59/100 (low)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `orbitcompute.ai`: 59/100 (this document), [markdown](https://verifymcp.io/servers/mr-didi-mcp-ocei-oracle/orbitcompute.md), [page](https://verifymcp.io/servers/mr-didi-mcp-ocei-oracle/orbitcompute)

## Channel facts

- Endpoint: `https://orbitcompute.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1108 tokens (~277/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the OCEI v2.2 Orbital Compute & Arbitrage Oracle MCP server?

OCEI v2.2 Orbital Compute & Arbitrage Oracle is a hosted endpoint at https://orbitcompute.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http mr-didi-mcp-ocei-oracle 'https://orbitcompute.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mr-didi-mcp-ocei-oracle": {
      "url": "https://orbitcompute.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mr-didi-mcp-ocei-oracle": {
      "type": "http",
      "url": "https://orbitcompute.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mr-didi-mcp-ocei-oracle]
url = "https://orbitcompute.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mr-didi-mcp-ocei-oracle": {
      "type": "remote",
      "url": "https://orbitcompute.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mr-didi-mcp-ocei-oracle --url 'https://orbitcompute.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mr-didi-mcp-ocei-oracle:
    url: "https://orbitcompute.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mr-didi-mcp-ocei-oracle": {
      "Transport": "http",
      "Url": "https://orbitcompute.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mr-didi-mcp-ocei-oracle -t streamable-http -u 'https://orbitcompute.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mr-didi-mcp-ocei-oracle": {
      "type": "http",
      "url": "https://orbitcompute.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 59, +5)

- [security] Tool “compute_arbitrage_dispatch” rewrote its description, which is the text the model reads
- [security] Tool “evaluate_orbital_compute_regime” rewrote its description, which is the text the model reads
- [security] Tool “solve_optimal_workload_allocation” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional] Schema quality: fair → good
- [functional] Server version: 2.2.0 → 2.3.0
- [functional] New tool “get_ocei_history_and_live_grids”
- [cosmetic] “compute_arbitrage_dispatch” added an optional parameter “grid_hub”
- [cosmetic] “evaluate_orbital_compute_regime” added an optional parameter “annual_attrition_pct”
- [cosmetic] “evaluate_orbital_compute_regime” added an optional parameter “comm_intensity_bits_per_flop”
- [cosmetic] “evaluate_orbital_compute_regime” added an optional parameter “earth_capex_factor”
- [cosmetic] “evaluate_orbital_compute_regime” added an optional parameter “grid_hub”
- [cosmetic] “evaluate_orbital_compute_regime” added an optional parameter “launch_vehicle”
- [cosmetic] “solve_optimal_workload_allocation” added an optional parameter “comm_intensity_bits_per_flop”
- [cosmetic] “solve_optimal_workload_allocation” added an optional parameter “grid_hub”
- [cosmetic] “compute_arbitrage_dispatch” reworded the description of “grid_price_usd_mwh”
- [cosmetic] “compute_arbitrage_dispatch” reworded the description of “hw”
- [cosmetic] “compute_arbitrage_dispatch” reworded the description of “power_mw”
- [cosmetic] “compute_arbitrage_dispatch” reworded the description of “storm_mode”
- [cosmetic] “evaluate_orbital_compute_regime” reworded the description of “altitude_km”
- [cosmetic] “evaluate_orbital_compute_regime” reworded the description of “beta_deg”
- [cosmetic] “evaluate_orbital_compute_regime” reworded the description of “grid_price_usd_mwh”
- [cosmetic] “evaluate_orbital_compute_regime” reworded the description of “hw”
- [cosmetic] “evaluate_orbital_compute_regime” reworded the description of “loop_temp_c”
- [cosmetic] “evaluate_orbital_compute_regime” reworded the description of “power_mw”
- [cosmetic] “evaluate_orbital_compute_regime” reworded the description of “storm_mode”
- [cosmetic] “solve_optimal_workload_allocation” reworded the description of “grid_price_usd_mwh”
- [cosmetic] “solve_optimal_workload_allocation” reworded the description of “max_latency_ms”
- [cosmetic] “solve_optimal_workload_allocation” reworded the description of “storm_mode”
- [cosmetic] “solve_optimal_workload_allocation” reworded the description of “workload_type”
- [cosmetic] “compute_arbitrage_dispatch” made “grid_price_usd_mwh” optional

### 2026-11-20 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 51, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 51)

First indexed and scored.

## MCP tools (4)

### `evaluate_orbital_compute_regime` (~493 tokens)

Full physics, 5-year TCO, and credit-underwriting audit for an orbital AI cluster. Use this tool for deep thermodynamic, radiation, Turyshev communication-intensity (bits/J), attrition stress (3.5%/9.0%), $/W payback, and 4-pillar OCEI v2.3 scoring. Do NOT use for fast binary electricity dispatch (use compute_arbitrage_dispatch) or multi-shell percentage routing (use solve_optimal_workload_allocation).

Input parameters:

- `altitude_km` (number): Orbital altitude in km (320=VLEO, 650=Dawn-Dusk SSO, 1500=MEO).
- `annual_attrition_pct` (number): Annual unrepairable hardware attrition rate in percent (0=raw baseline, 3.5=burn-in screened, 9.0=unscreened stress).
- `beta_deg` (number): Solar beta angle in degrees (75-90 yields zero eclipse at 650 km).
- `comm_intensity_bits_per_flop` (number): Workload I/O intensity in bits/FLOP (1e-8=text/reasoning, 2e-6=rich multimodal) for Turyshev Gamma downlink checks.
- `earth_capex_factor` (number): Terrestrial civil/substation CapEx multiplier (1.0=Tier-IV utility, 0.6=vertically integrated self-build).
- `grid_hub` (string): Select live D1 wholesale electricity hub (ercot=Texas, pjm=Virginia, epex=Europe) or canonical $115/MWh baseline.
- `grid_price_usd_mwh` (number): Custom terrestrial grid tariff in USD/MWh (overrides grid_hub if provided).
- `hw` (string): Orbital AI hardware stack profile.
- `launch_vehicle` (string): Heavy-lift launch vehicle mass and price model.
- `loop_temp_c` (number): Radiator coolant loop temperature in Celsius (80C optimal for commercial silicon; 95C for Terafab 370K).
- `power_mw` (number): Target cluster electrical capacity in megawatts (1 to 100,000 MW).
- `storm_mode` (string): Space weather telemetry source: live NOAA/GOES streams or deterministic G0/G3/G5 stress profile.

### `compute_arbitrage_dispatch` (~242 tokens)

Fast binary go/no-go economic dispatch decision comparing a single terrestrial electricity price or live hub (ERCOT, PJM, EPEX) against the orbital breakeven threshold ($/MWh). Returns exact dispatch_signal (ORBIT_PRIMARY, HYBRID_SPLIT, TERRESTRIAL_PRIMARY), dispatch_directive, breakeven threshold, and $/MTok spread. Use ONLY for binary grid-vs-orbit switching; use solve_optimal_workload_allocation for 3-shell percentage splits.

Input parameters:

- `grid_hub` (string): Live wholesale electricity hub to evaluate when grid_price_usd_mwh is omitted.
- `grid_price_usd_mwh` (number): Explicit local spot electricity price in USD/MWh (supports negative wind/solar spot prices). If omitted, uses grid_hub.
- `hw` (string): Hardware stack profile determining $/MTok and breakeven $/MWh.
- `power_mw` (number): Cluster scale in MW used to size launch/bus overhead and breakeven threshold.
- `storm_mode` (string): Space-weather mode for pre-emptive storm failover triggers.

### `solve_optimal_workload_allocation` (~248 tokens)

Multi-shell percentage constraint solver for cluster schedulers (SkyPilot, Kubernetes, SOOS). Outputs exact percentage splits across 650 km Dawn-Dusk SSO, 320 km self-cleaning VLEO Edge, and Terrestrial Spot Grids based on workload latency SLA, Turyshev downlink intensity (bits/FLOP), space weather, and electricity price. Returns optimal_split_pct and blended $/1M token cost.

Input parameters:

- `comm_intensity_bits_per_flop` (number): Turyshev I/O intensity (bits/FLOP); automatically shifts downlink-bound multimodal workloads to Earth.
- `grid_hub` (string): Live wholesale electricity hub (ercot, pjm, epex) or $115/MWh baseline.
- `grid_price_usd_mwh` (number): Spot grid price in USD/MWh; if omitted, uses grid_hub.
- `max_latency_ms` (number): Maximum acceptable one-way network latency in ms (<=6 ms prioritizes 320 km VLEO).
- `storm_mode` (string): Space weather regime.
- `workload_type` (string): AI workload class controlling latency sensitivity and batchability.

### `get_ocei_history_and_live_grids` (~125 tokens)

Retrieves empirical Cloudflare D1 time-series snapshots of OCEI-Spot, true 60-minute settlement TWAP, rolling 30-day covenant availability, and all 3 live wholesale spot electricity hubs (ERCOT Texas, PJM Virginia, EPEX Europe). Use this tool for historical trend comparison, SLA/insurance covenant auditing, or live electricity price lookup.

Input parameters:

- `hours` (number): Lookback window in hours (1 to 720 hours / 30 days).
- `limit` (number): Maximum number of D1 snapshot rows to return.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mr-didi-mcp-ocei-oracle/orbitcompute#diagnostics

## Score history

- 2026-11-21: 59
- 2026-11-20: 54
- 2026-11-19: 53
- 2026-11-18: 53
- 2026-11-17: 52
- 2026-11-16: 52
- 2026-11-15: 52
- 2026-11-14: 51
- 2026-11-13: 51

## Common questions

### What is the OCEI v2.2 Orbital Compute & Arbitrage Oracle MCP server?

OCEI v2.2 Orbital Compute & Arbitrage Oracle is an MCP server listed in the public MCP registry as io.github.Mr-Didi/mcp-ocei-oracle. Attested orbital AI compute physics, NOAA space-weather & $/MTok arbitrage oracle (OCEI v2.2). This page covers its hosted endpoint (https://orbitcompute.ai/mcp).

### Is the OCEI v2.2 Orbital Compute & Arbitrage Oracle MCP server safe to use?

OCEI v2.2 Orbital Compute & Arbitrage Oracle scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the OCEI v2.2 Orbital Compute & Arbitrage Oracle MCP server expose?

OCEI v2.2 Orbital Compute & Arbitrage Oracle exposes 4 tools: evaluate_orbital_compute_regime, compute_arbitrage_dispatch, solve_optimal_workload_allocation, get_ocei_history_and_live_grids. Their descriptions and schemas cost roughly 1,108 tokens of context every time the server is loaded.

### Does the OCEI v2.2 Orbital Compute & Arbitrage Oracle MCP server require authentication?

No. We connected to OCEI v2.2 Orbital Compute & Arbitrage Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the OCEI v2.2 Orbital Compute & Arbitrage Oracle MCP server still maintained?

OCEI v2.2 Orbital Compute & Arbitrage Oracle is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the OCEI v2.2 Orbital Compute & Arbitrage Oracle MCP server?

VerifyMCP ran 12 checks on OCEI v2.2 Orbital Compute & Arbitrage Oracle, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about OCEI v2.2 Orbital Compute & Arbitrage Oracle: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://orbitcompute.ai/mcp
- Repository: https://github.com/Mr-Didi/mcp-ocei-oracle
- Changelog RSS feed: https://verifymcp.io/servers/mr-didi-mcp-ocei-oracle/orbitcompute.xml
- Changelog JSON feed: https://verifymcp.io/servers/mr-didi-mcp-ocei-oracle/orbitcompute/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mr-didi-mcp-ocei-oracle/orbitcompute.json
- HTML version of this page: https://verifymcp.io/servers/mr-didi-mcp-ocei-oracle/orbitcompute
