MCP add-on, Streamable HTTP, spec 2025-11-25

Space weather, turned into a go or no go.

A geomagnetic storm pushes satellite navigation off by centimetres, then metres. Orbita reads the live NOAA forecast and answers the question the person actually has: can I run this now, and if not, when. It answers the same way for a satellite team, a control room, a dispatcher, a drilling crew and a household.

Try it live Read the code

Kp right now: checking
Storm level: checking
NOAA data age: checking
Answer time: checking

Live from this server, not a recording.

Try it live

Every answer is computed here, from the NOAA feed this server polls in the background. Nothing on this page is scripted. Alexa is not in the loop: the page calls the same tools an Alexa+ add-on would call, and shows what comes back.

Ask Orbita

Ask anything, by voice or by typing.

Farmers, drone pilots, satellite teams, dispatchers, ships, grids and data centres, robots, or anyone who wants to see the aurora. A model picks the tool from this server's real tool list, as Alexa+ would.

When

Now is this moment. Another time checks the forecast up to three days ahead, or plays back a past day, for questions and examples alike. Start again clears the conversation and gives you a fresh farm.

Or tap an example

Farm examples ask about a field this page sets up for you.

Call any tool directly

Tool Arguments, JSON

Spoken answer

Ask above, or tap an example, and the answer comes from live data.

Raw response

What an Echo Show would display

MCP Apps, spec 2026-01-26

The same panel file the add-on serves, driven through the real handshake. It updates on the four tools that carry it. Verdict is never colour alone: bars carry the number, hatching and wording carry the refusal.

Recent calls

Nothing yet.

How it works

Three decisions shape everything else.

The forecast is polled, never fetched mid answer

NOAA is read on a background timer every fifteen minutes and held in memory, so an answer is a few milliseconds of arithmetic. A voice turn has roughly half a second in total, which a live call to an external service can eat on its own.

The verdict is drift against tolerance, not a Kp number

Expected error comes from the correction the machine runs, RTK, PPP, SBAS or none, the geomagnetic latitude of the site rather than its map latitude, and the distance to the RTK base. That is compared against what the job itself needs, which is why planting and tillage get different answers from the same sky.

Same storm, twelve different jobs

One forecast means planting waits, a satellite team defers a manoeuvre, a control room watches transformer heating, a dispatcher plans a lower latitude route and an aurora watcher goes outside. Each gets its own steps, timed to how far off the storm is.

What it will not do

The honest list, because a wrong go-ahead costs a season.

It will not guess. If NOAA is unreachable it says so and tells you where to look instead.
It cannot make Alexa speak first. An add-on answers when it is called, so warnings go out another way: an email the day before a storm that matters to you and again when the solar wind turns south about an hour out, for any of the jobs it covers, and a signed message to a fleet's own software for machines that cannot read one.
It stops at three days. That is how far the Kp forecast runs, and past it the answer is that it does not know.
It is not a base station. It tells you whether accuracy holds, it does not correct anything.
The farm on this page is yours alone, and only for a while. The field and machines it sets up belong to this browser, and are deleted after a week without use. Start again gives you a fresh one.

Where the numbers come from

Public sources, called live. No sample files.

NOAA SWPC planetary Kp forecastthree hour blocks, three days ahead
NOAA SWPC alerts and warningswhat is running right now
NOAA space weather scalesG, S and R levels, today and the outlook
Open-Meteothe timezone of each field, so times are said where the field is

Run it yourself

Node 20 or newer. No keys, no accounts, no paid services.

git clone https://github.com/nirbhay221/orbita
cd orbita
npm install
npm run build
node dist/server.js        # serves this page and the MCP endpoint on 8788

Or, with nothing installed but Docker: docker build -t orbita . && docker run -p 8788:8788 orbita

Call a tool the way a host would:

curl -s http://localhost:8788/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"storm_status","arguments":{}}}'