Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Orbitwren

REMOTE · ORBITWREN.CYBERMAXTOOLS.COM

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

+3 this week 77 Trust /100

Last scanned (17 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Oct 26 +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.

  • 19 Oct 26 +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.

  • 16 Oct 26 +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.

  • 14 Oct 26 +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.

  • 12 Oct 26 +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.

  • 10 Oct 26 72

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Oct 2026 · Probed https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cybermaxtools.com CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 308624ed6942b3d50e71ca721704e6da
SANs: cybermaxtools.com, orbitwren.cybermaxtools.com, *.orbitwren.cybermaxtools.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of orbitwren.cybermaxtools.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cybermaxtools.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry Verified 200
http (plaintext) http://orbitwren.cybermaxtools.com/mcp?via=mcp-registry HTTPS enforced 301 https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry
MCP tools · 6 exposed · ~719 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compute_satellite_orbits ~83

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

NameTypeReqDescription
noradstring–NORAD catalog number(s), comma separated (empty = every tracked compute satellite)
projectstring–Tracker project id (part of it), e.g. starcloud

No output schema declared.

No examples provided.

next_compute_launch ~46

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).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

orbital_compute_alerts ~125

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).

NameTypeReqDescription
companystring–Company name (part of it)
limitinteger–Rows (1-500)
sincestring–Only alerts on or after this date (YYYY-MM-DD)
typestring–Alert types, comma separated: new_project, launch, date_change, status_change, update

No output schema declared.

No examples provided.

orbital_compute_projects ~215

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.

NameTypeReqDescription
categorystring–Text in the category, e.g. satellite, constellation filing, hardware platform
companystring–Company or partner name (part of it), e.g. starcloud, google
inOrbitboolean–Only projects with hardware in orbit now
limitinteger–Rows (1-100)
qstring–Free text over company, project, hardware and summary, e.g. TPU or H100
statusstring–One of: scheduled, in orbit, deployed, flown, planned, filed, announced, development

No output schema declared.

No examples provided.

tracker_changes ~58

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

NameTypeReqDescription
limitinteger–Rows (1-200)
sincestring–Only changes on or after this date (YYYY-MM-DD)

No output schema declared.

No examples provided.

upcoming_launches ~192

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.

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

No output schema declared.

No examples provided.

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.

remote · orbitwren.cybermaxtools.com

# add to Claude Code
claude mcp add --transport http dev-workers-cybermax-tools-cybermax-orbitwren 'https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry'
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.