# Orbitwren (remote · orbitwren.cybermaxtools.com)

Orbital data center & space AI compute tracker MCP: projects, launches, orbits, alerts. 100 free/day

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `orbitwren.cybermaxtools.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-orbitwren/orbitwren-2.md), [page](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-orbitwren/orbitwren-2)

## Channel facts

- Endpoint: `https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.2`

## 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-10-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 816 tokens (~136/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Orbitwren MCP server?

Orbitwren is a hosted endpoint at https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry, 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 dev-workers-cybermax-tools-cybermax-orbitwren 'https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-cybermax-tools-cybermax-orbitwren": {
      "url": "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-cybermax-tools-cybermax-orbitwren": {
      "type": "http",
      "url": "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-cybermax-tools-cybermax-orbitwren]
url = "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-cybermax-tools-cybermax-orbitwren": {
      "type": "remote",
      "url": "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-cybermax-tools-cybermax-orbitwren --url 'https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-cybermax-tools-cybermax-orbitwren:
    url: "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-cybermax-tools-cybermax-orbitwren": {
      "Transport": "http",
      "Url": "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-cybermax-tools-cybermax-orbitwren -t streamable-http -u 'https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-cybermax-tools-cybermax-orbitwren": {
      "type": "http",
      "url": "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

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-10-21 (score 77, +1)

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

### 2026-10-19 (score 76, +1)

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

### 2026-10-16 (score 75, +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-10-14 (score 74, +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-10-12 (score 73, +1)

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

### 2026-10-10 (score 72)

First indexed and scored.

## MCP tools (6)

### `orbital_compute_projects` (~215 tokens)

Orbital compute projects

Orbital data centers and space AI compute projects (data centers in space, AI chips in orbit, FCC constellation filings): company, partners, hardware in orbit, launch date, vehicle, status, scale, publicly stated funding, NORAD IDs and source URLs. Use for questions like "who is building orbital data centers?" or "are there data centers in space?". Filter by company, status, category or text.

Input parameters:

- `category` (string): Text in the category, e.g. satellite, constellation filing, hardware platform
- `company` (string): Company or partner name (part of it), e.g. starcloud, google
- `inOrbit` (boolean): Only projects with hardware in orbit now
- `limit` (integer): Rows (1-100)
- `q` (string): Free text over company, project, hardware and summary, e.g. TPU or H100
- `status` (string): One of: scheduled, in orbit, deployed, flown, planned, filed, announced, development

### `next_compute_launch` (~46 tokens)

Next orbital-compute launch

The next launch carrying a tracked orbital data center / space AI compute project, with NET, window, status, seconds to launch and the projects on board (null when none is scheduled).

### `upcoming_launches` (~192 tokens)

Upcoming launches

Upcoming orbital launches from The Space Devs Launch Library 2 with rideshare and orbital-compute flags; filter by days ahead, rideshare, compute, provider, country or text.

Input parameters:

- `compute` (boolean): Only launches carrying a tracked orbital-compute project or mentioning data centres/TPUs/GPUs
- `country` (string): Pad country, ISO 3166 alpha-3, e.g. USA, CHN, NZL
- `days` (integer): Look ahead N days (1-730)
- `limit` (integer): Rows (1-100)
- `provider` (string): Launch provider (part of the name), e.g. SpaceX, Rocket Lab
- `q` (string): Free text over launch name, mission and rocket
- `rideshare` (boolean): true = only rideshare missions (Transporter, Bandwagon ...), false = exclude them

### `compute_satellite_orbits` (~83 tokens)

Compute satellite orbits

CelesTrak orbit elements with perigee/apogee and period for tracked orbital-compute satellites (by NORAD ID or project).

Input parameters:

- `norad` (string): NORAD catalog number(s), comma separated (empty = every tracked compute satellite)
- `project` (string): Tracker project id (part of it), e.g. starcloud

### `orbital_compute_alerts` (~125 tokens)

Orbital data center alerts (paid key)

Orbitwren Alerts: classified events for orbital data centers and space AI compute (new_project, launch, date_change, status_change) with companies and source URLs. Needs a paid Orbitwren key (Alerts plan $5/month).

Input parameters:

- `company` (string): Company name (part of it)
- `limit` (integer): Rows (1-500)
- `since` (string): Only alerts on or after this date (YYYY-MM-DD)
- `type` (string): Alert types, comma separated: new_project, launch, date_change, status_change, update

### `tracker_changes` (~58 tokens)

Tracker change log

Day-to-day changes: project status, launch dates, NORAD IDs, tracked launch NET/status.

Input parameters:

- `limit` (integer): Rows (1-200)
- `since` (string): Only changes on or after this date (YYYY-MM-DD)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-orbitwren/orbitwren-2#diagnostics

## Score history

- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 72

## Common questions

### What is the Orbitwren MCP server?

Orbitwren is an MCP server listed in the public MCP registry as dev.workers.cybermax-tools.cybermax/orbitwren. Orbital data center & space AI compute tracker MCP: projects, launches, orbits, alerts. 100 free/day. This page covers its hosted endpoint (https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry).

### Is the Orbitwren MCP server safe to use?

Orbitwren scores 77 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 Orbitwren MCP server expose?

Orbitwren exposes 6 tools: orbital_compute_projects, next_compute_launch, upcoming_launches, compute_satellite_orbits, orbital_compute_alerts, tracker_changes. Their descriptions and schemas cost roughly 719 tokens of context every time the server is loaded.

### Does the Orbitwren MCP server require authentication?

No. We connected to Orbitwren without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Orbitwren MCP server still maintained?

Orbitwren is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry
- Repository: https://gitlab.com/CyberMax.tools/agent-tools
- Website: https://cybermaxtools.com/apis/orbital-data-center-api/?s=mcp-registry-orbitwren
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-orbitwren/orbitwren-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-orbitwren/orbitwren-2.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-orbitwren/orbitwren-2