Orbitwren
Orbital data center & space AI compute tracker MCP: projects, launches, orbits, alerts. 100 free/day
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"orbitwren": {
"url": "https://orbitwren.cybermax-tools.workers.dev/mcp?via=mcp-registry"
}
}
}Puntos de conexión remotos
https://orbitwren.cybermax-tools.workers.dev/mcp?via=mcp-registrystreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (6)
🟢orbital_compute_projects(company, status, category, q, inOrbit, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"company": {
"type": "string",
"description": "Company or partner name (part of it), e.g. starcloud, google"
},
"status": {
"type": "string",
"enum": [
"scheduled",
"in orbit",
"deployed",
"flown",
"planned",
"filed",
"announced",
"development"
],
"description": "One of: scheduled, in orbit, deployed, flown, planned, filed, announced, development"
},
"category": {
"type": "string",
"description": "Text in the category, e.g. satellite, constellation filing, hardware platform"
},
"q": {
"type": "string",
"description": "Free text over company, project, hardware and summary, e.g. TPU or H100"
},
"inOrbit": {
"type": "boolean",
"default": false,
"description": "Only projects with hardware in orbit now"
},
"limit": {
"type": "integer",
"default": 50,
"description": "Rows (1-100)"
}
}
}🟢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).
Esquema de entrada
{
"type": "object",
"properties": {}
}🟢upcoming_launches(days, rideshare, compute, provider, country, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"days": {
"type": "integer",
"default": 90,
"description": "Look ahead N days (1-730)"
},
"rideshare": {
"type": "boolean",
"description": "true = only rideshare missions (Transporter, Bandwagon ...), false = exclude them"
},
"compute": {
"type": "boolean",
"default": false,
"description": "Only launches carrying a tracked orbital-compute project or mentioning data centres/TPUs/GPUs"
},
"provider": {
"type": "string",
"description": "Launch provider (part of the name), e.g. SpaceX, Rocket Lab"
},
"country": {
"type": "string",
"description": "Pad country, ISO 3166 alpha-3, e.g. USA, CHN, NZL"
},
"q": {
"type": "string",
"description": "Free text over launch name, mission and rocket"
},
"limit": {
"type": "integer",
"default": 25,
"description": "Rows (1-100)"
}
}
}🟢compute_satellite_orbits(norad, project)
CelesTrak orbit elements with perigee/apogee and period for tracked orbital-compute satellites (by NORAD ID or project).
Esquema de entrada
{
"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"
}
}
}🟢orbital_compute_alerts(since, type, company, limit)
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).
Esquema de entrada
{
"type": "object",
"properties": {
"since": {
"type": "string",
"format": "date",
"description": "Only alerts on or after this date (YYYY-MM-DD)"
},
"type": {
"type": "string",
"description": "Alert types, comma separated: new_project, launch, date_change, status_change, update"
},
"company": {
"type": "string",
"description": "Company name (part of it)"
},
"limit": {
"type": "integer",
"default": 100,
"description": "Rows (1-500)"
}
}
}🟢tracker_changes(since, limit)
Day-to-day changes: project status, launch dates, NORAD IDs, tracked launch NET/status.
Esquema de entrada
{
"type": "object",
"properties": {
"since": {
"type": "string",
"format": "date",
"description": "Only changes on or after this date (YYYY-MM-DD)"
},
"limit": {
"type": "integer",
"default": 50,
"description": "Rows (1-200)"
}
}
}Comunidad
Evidencia