Home / MCP registry index / fr.vigi-sky/vigisky

Vigi-Sky

fr.vigi-sky/vigisky in the official MCP registry. Endpoint https://vigi-sky.fr/mcp.

The registry describes it as: Factual sky for AIs: ISS, auroras, archives. Never confuses unexplained with extraterrestrial.

We read its 24 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

doctrine cite aurora iss_passes identify nearby_cases first_skies tonight_sky observation_conditions solar status hatch_stats hatch_search nasa_apod neo_watch starlink_trains nights_network object_lookup hypothesis_rank capabilities proposer_signalement confirmer_action annuler_action statut_actions

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/fr-vigi-sky-vigisky/badge.svg)](https://lazaretto.dev/mcp-registry/fr-vigi-sky-vigisky)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.