_ registry / mcp + a2a streamable-http · checked 4h ago

orbitwren

https://orbitwren.cybermax-tools.workers.dev

Registry code: 6b037b9178617699

api record

Orbitwren tracks orbital data centers and space AI compute: every public project putting AI chips or data center computing in orbit. orbital_compute_projects lists projects with hardware, launch, status, funding (if public) and sources; next_compute_launch gives the next launch carrying orbital compute with a countdown; upcoming_launches lists launches (rideshare/compute flags); compute_satellite_orbits gives CelesTrak elements; tracker_changes lists what changed. Unknown values are null.

endpoint
https://orbitwren.cybermax-tools.workers.dev/mcp?via=mcp-registry
door code
18af28eee30f1f17
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is orbitwren live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is orbitwren free to use?
Yes — the hub reached it with no key and no payment.
What tools does orbitwren have?
6 tools: orbital_compute_projects, next_compute_launch, compute_satellite_orbits, orbital_compute_alerts, upcoming_launches, tracker_changes.
Is orbitwren safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
179ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 203 checks · signed record
  • unknown → live
  • unknown → live
_ what it is for
topic
infrastructure & devops
used for
  • list orbital data center projects
  • get next launch carrying orbital compute
  • get orbit elements of compute satellites
  • track changes in space compute projects
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • upcoming_launches reads open 14h ago

    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.

    mcp-tool

    {
  "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"
    }
  }
}
    arguments 36 lines
  • tracker_changes reads open 14h ago

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

    mcp-tool

    {
  "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)"
    }
  }
}
    arguments 15 lines
  • orbital_compute_projects reads unknown never probed

    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.

    mcp-tool

    {
  "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"
    }
  }
}
    arguments 41 lines
  • next_compute_launch reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • compute_satellite_orbits reads unknown never probed

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

    mcp-tool

    {
  "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"
    }
  }
}
    arguments 13 lines
  • orbital_compute_alerts reads unknown never probed

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

    mcp-tool

    {
  "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)"
    }
  }
}
    arguments 23 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6b037b9178617699.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6b037b9178617699/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6b037b9178617699/badge.svg)](https://brick.blue/agent/6b037b9178617699?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
2
ok
0
failed
2
success rate
0%
median latency
93ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

2 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.