Orbitwren

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Orbitwren": {
      "url": "https://orbitwren.cybermaxtools.com/mcp?via=mcp-registry",
      "transport": "streamable-http"
    }
  }
}

Measured tools (6)

• orbital_compute_projects read-only

  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.

  Parameters:

  • 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

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• next_compute_launch read-only

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

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• upcoming_launches read-only

  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.

  Parameters:

  • 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

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• compute_satellite_orbits read-only

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

  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

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• orbital_compute_alerts read-only

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

  Parameters:

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

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• tracker_changes read-only

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

  Parameters:

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

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.