Plug your AI into the real sky

Vigi-Sky MCP gives AIs factual access to the sky: ISS, satellites, auroras, celestial objects, sourced archives and identification methods — without ever confusing unexplained with extraterrestrial.

MCP 2025-11-25 29 tools · 30 resources · 6 prompts No account Privacy-first Hatch = 1900–2002 archive fr.vigi-sky/vigisky

Add to Claude Try in ChatGPT Use with Codex server.json Changelog Official registry Smithery MCP.so

Public consented Vigi-Sky dossiers = 0. An internal inbox is not a public corpus. Official reporting in France is GEIPAN. Never “UFO detected”.

Demo — Nant, Aveyron

Real sky over the Causses near Nant, Aveyron

The sky over Nant. Not a “UFO night” — a measurable sky: ISS, Kp, cultural objects.

1. “What can I observe tonight above Nant, Aveyron?” → tonight_sky
2. “I saw a very bright point moving with no blinking.” → what_did_i_see (planets, Moon, ISS, Tiangong and ~160 bright satellites at that time; at best “compatible”, never proof)

No account Sources cited Never “UFO detected”

Three ready prompts

What can I observe tonight above Nant, Aveyron?

I saw a very bright point moving with no blinking.

How do the Diné read the Pleiades, and who published that? Name the nation. Separate attested / interpretation.

What data is sent?

Every tool reads or computes, except the sighting report, which stores nothing without the witness’s consent (draft_sighting_report, then submit_sighting_report; cancel_sighting_report cancels; position rounded to about 1 km before publication). A call only sends the JSON-RPC your client builds: tool name + arguments (e.g. latitude, search text).

No photo, no video, no file.
No account, no cookie, no access token.
The Origin header is checked (hostile origins get 403).
Web logs may see IP and User-Agent, like any website.
Apart from a sighting report, nothing is stored or published. Third-party calls are only the documented sky APIs (NOAA/Kp, Celestrak via Vigi-Sky, NASA APOD page).

Photos and cameras stay on the local sentinel-mcp (stdio / 127.0.0.1), never here.

Connect

Endpoint: https://vigi-sky.fr/mcp — Streamable HTTP, protocol 2025-11-25.

[mcp_servers.vigisky]
url = "https://vigi-sky.fr/mcp"

Discovery · AI Catalog · MCP Server Card

Claude: Settings → Connectors → Add custom connector. Registry: server.json (fr.vigi-sky/vigisky). Liveness: /mcp/health; dependencies: /mcp/ready.