Orbitwren

Working · 770 ms

dev.workers.cybermax-tools.cybermax/orbitwrenv1.2.2 Domain verified

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

Research & Knowledge

Source Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry

x-api-key (optional)

Optional paid-plan key from orbitwren.cybermaxtools.com; leave out for 100 free calls a day.

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

compute_satellite_orbits Read-only

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

noradstring

NORAD catalog number(s), comma separated (empty = every tracked compute satellite)

projectstring

Tracker project id (part of it), e.g. starcloud

Tools (6)

compute_satellite_orbits

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

read-only

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

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "norad": {
      "type": "string",
      "description": "NORAD catalog number(s), comma separated (empty = every tracked compute satellite)"
    },
    "project": {
      "type": "string",
      "description": "Tracker project id (part of it), e.g. starcloud"
    }
  }
}

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

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {}
}

orbital_compute_alerts

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

read-only

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

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "description": "Alert types, comma separated: new_project, launch, date_change, status_change, update"
    },
    "limit": {
      "type": "integer",
      "default": 100,
      "description": "Rows (1-500)"
    },
    "since": {
      "type": "string",
      "format": "date",
      "description": "Only alerts on or after this date (YYYY-MM-DD)"
    },
    "company": {
      "type": "string",
      "description": "Company name (part of it)"
    }
  }
}

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.

read-only

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

Input schema (JSON)

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

tracker_changes

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

read-only

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

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "description": "Rows (1-200)"
    },
    "since": {
      "type": "string",
      "format": "date",
      "description": "Only changes on or after this date (YYYY-MM-DD)"
    }
  }
}

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.

read-only

Argument	Type	Description
q	string	Free text over launch name, mission and rocket
days	integer	Look ahead N days (1-730)
limit	integer	Rows (1-100)
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
provider	string	Launch provider (part of the name), e.g. SpaceX, Rocket Lab
rideshare	boolean	true = only rideshare missions (Transporter, Bandwagon ...), false = exclude them

Input schema (JSON)

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