com.cyclecalcs/astronomy

Est-ce que com.cyclecalcs/astronomy est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.cyclecalcs/astronomy » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 11 outils

• astro_dark_window≈ 1077 tokens

  The genuinely dark, moonless observing window for a night: astronomical night intersected with the Moon being down, ranked across up to 62 nights with a trend. The right tool for "when should I stargaze / photograph the Milky Way / observe deep-sky objects". Location required. For plain twilight times use astro_sun.

  Paramètres, retour & exemple (7)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    Night to start from. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • nights · integer · optionnel
    How many nights to evaluate and rank. Default 1.
  • moon_illumination_max · number · optionnel
    Treat the Moon as tolerable below this illuminated fraction (0..1) even when up.

  Exemple d'appel

  {"name": "astro_dark_window", "arguments": {"tz": "texte", "lat": 1, "lon": 1, "date": "texte", "place": "texte", "nights": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_eclipses≈ 1832 tokens

  Solar and lunar eclipses: the next or previous from a date, or all in a range, with type, magnitude, obscuration, Saros series and global geometry. A solar eclipse also carries a computed hybrid flag and, when central, the duration, path width and Sun altitude at greatest eclipse. With a location it adds local circumstances, contact times, and an explicit visible-from-here answer; set visible_only to true to keep only eclipses visible there. include adds the precomputed central path or the circumstances at greatest local eclipse. NOTE: count applies per type, so count=3 with type "both" can return six events.

  Paramètres, retour & exemple (13)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • end · string · optionnel
    Last day of an explicit window. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    Anchor date to search from. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • type · string · optionnel · solar | lunar | both
    Which kind of eclipse to report. Default "both".
  • count · integer · optionnel
    How many eclipses PER TYPE to return.
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • start · string · optionnel
    First day of an explicit window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • cursor · string · optionnel
    Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page.
  • include · array · optionnel
    Optional extras, added to the default blocks rather than replacing them. "path": the precomputed central path of a solar eclipse as inline GeoJSON (central line, northern and southern limits, and per-minute duration, width, phase and Sun altitude), for the central eclipses that have one; every other eclipse says why it has none. Large: about 65 to 90 KB of JSON per eclipse, returned as both text and structured content, so ask for one eclipse at a time (type "solar", a date just before it, count 1). "greatest": the circumstances at greatest eclipse from the supplied location, inside each solar eclipse's local block (requires a location).
  • direction · string · optionnel · next | previous
    Search direction from the anchor date. Default "next".
  • visible_only · boolean · optionnel
    true keeps only eclipses visible from the supplied location (requires a location).

  Exemple d'appel

  {"name": "astro_eclipses", "arguments": {"tz": "texte", "end": "texte", "lat": 1, "lon": 1, "date": "texte", "type": "solar"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_find_place≈ 834 tokens

  Resolve a place name to coordinates, region, country, IANA timezone and a stable place_id, or reverse-look-up the nearest places to a lat/lon. Results are GeoNames data (CC BY 4.0); the response carries the required credit in its attribution field, which must be preserved when results are shown. Note the other tools accept a place argument directly, so this is only needed to disambiguate a name, filter by country, or reverse-geocode.

  Paramètres, retour & exemple (6)

  Paramètres

  • id · string · optionnel
    A place_id from an earlier result, to fetch that exact place.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • limit · integer · optionnel
    Maximum matches to return. Default 5.
  • query · string · optionnel
    Place name to search for, e.g. "Springfield".
  • country · string · optionnel
    Two-letter ISO country code filter, e.g. "US".

  Exemple d'appel

  {"name": "astro_find_place", "arguments": {"id": "texte", "lat": 1, "lon": 1, "limit": 1, "query": "texte", "country": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_moon≈ 1628 tokens

  The Moon at an instant or as a daily series: phase name and angle, illuminated fraction, distance, apparent size, libration, bright limb, and the next quarter phases. A location adds rise/set and altitude. For a calendar of new and full moons use astro_moon_phases; for the Moon's exact coordinates use astro_positions.

  Paramètres, retour & exemple (9)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • end · string · optionnel
    Last day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • count · integer · optionnel
    Number of daily rows from start (alternative to end).
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • start · string · optionnel
    First day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • cursor · string · optionnel
    Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page.

  Exemple d'appel

  {"name": "astro_moon", "arguments": {"tz": "texte", "end": "texte", "lat": 1, "lon": 1, "date": "texte", "count": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_moon_phases≈ 1279 tokens

  Every new moon, quarter and full moon in a window (or the next few from a date): each with its exact instant, distance, apparent size, supermoon classification under both competing definitions, traditional full-moon name, and any eclipse falling on it. Use for "when is the next full moon" and phase calendars. For the Moon's state right now use astro_moon.

  Paramètres, retour & exemple (10)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • end · string · optionnel
    Last day of a window. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    Anchor date; the next phases follow it. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • count · integer · optionnel
    How many phase events to return from the anchor date.
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • start · string · optionnel
    First day of a window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • cursor · string · optionnel
    Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page.
  • phases · array · optionnel
    Optional filter of phase kinds. Omit for all four. Example: ["full_moon"] for full moons only.

  Exemple d'appel

  {"name": "astro_moon_phases", "arguments": {"tz": "texte", "end": "texte", "lat": 1, "lon": 1, "date": "texte", "count": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_planet_board≈ 1062 tokens

  All eight planets in one call for a date and optional location: constellation, magnitude, apparent size, elongation from the Sun, morning or evening sky, retrograde state with the next station, rise/set, and a worth-looking-tonight assessment. The right tool for "which planets are visible tonight". For exact coordinates of specific bodies use astro_positions.

  Paramètres, retour & exemple (7)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • sort · string · optionnel · distance_from_sun | magnitude | elongation | altitude
    Optional result ordering. Default is by distance from the Sun.
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • bodies · array · optionnel
    Optional subset of planets: mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto.

  Exemple d'appel

  {"name": "astro_planet_board", "arguments": {"tz": "texte", "lat": 1, "lon": 1, "date": "texte", "sort": "distance_from_sun", "place": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_planet_events≈ 1848 tokens

  Dated planet events. For Mercury and Venus, the apparition cycle: inferior and superior conjunctions, greatest eastern and western elongations, peak brightness (a Venus-only event: Mercury's brightness peaks behind the Sun where it cannot be seen), and the rare transits across the Sun; with no dates it also reports where each is in its cycle right now: morning star or evening star, the conjunctions bounding the current apparition, and the live elongation, phase, magnitude and apparent size. For Mars, Jupiter, Saturn, Uranus and Neptune: conjunction with the Sun, western quadrature, opposition and eastern quadrature, the instants the planet's apparent geocentric ecliptic longitude minus the Sun's reaches 0, 270, 180 and 90 deg, each with the planet's constellation, distance, magnitude and elongation. For any of the seven, constellation_entry, returned only when listed in kinds: each crossing of an IAU constellation boundary, with the two constellations and the direction of motion. The right tool for "when does Venus become the morning star", "when is Mars at opposition", or "when does Uranus cross from Taurus into Gemini". For tonight's visibility of all eight planets use astro_planet_board. Mercury and Venus conjunction instants use the classical heliocentric convention, named on each event.

  Paramètres, retour & exemple (10)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • end · string · optionnel
    Last day of an explicit window, exclusive. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    Anchor instant; with no start/end the response covers the next full synodic cycle from here. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • kinds · array · optionnel
    Optional filter of event kinds. Omit for each planet's own family: the seven apparition kinds for mercury and venus, the four Sun-relative kinds for mars to neptune. peak_magnitude only ever fires for venus; the transit kinds are body-specific and genuinely rare. constellation_entry applies to all seven and must be listed.
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • start · string · optionnel
    First day of an explicit window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • bodies · array · optionnel
    Which planets to report. Default mercury and venus.
  • cursor · string · optionnel
    Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page.

  Exemple d'appel

  {"name": "astro_planet_events", "arguments": {"tz": "texte", "end": "texte", "lat": 1, "lon": 1, "date": "texte", "kinds": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_positions≈ 1358 tokens

  Exact positions for up to 20 bodies at an instant or over a time grid: right ascension and declination in both J2000 and of-date frames, ecliptic longitude and latitude, distance, and, with a location, altitude and azimuth with refraction stated per field. With a location the position is topocentric, but tropical_sign and constellation stay geocentric, and meta.conventions.label_origin says so. Use for "where exactly is X". Do not pass earth. For rise and set TIMES use astro_rise_set; for a visibility overview of all planets use astro_planet_board.

  Paramètres, retour & exemple (10)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • end · string · optionnel
    Grid end. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • step · string · optionnel
    Grid stride, e.g. "1h", "10min", "1d".
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • start · string · optionnel
    Grid start (use with end and step). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • bodies · array · requis
    Bodies to report. Each entry: One of sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, or a fixed J2000 target as "radec:RA,DEC" with RA in hours (0-24) and DEC in degrees (-90..90), e.g. "radec:5.6,-5.4" for the Orion Nebula region.
  • cursor · string · optionnel
    Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page.

  Exemple d'appel

  {"name": "astro_positions", "arguments": {"bodies": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_rise_set≈ 1298 tokens

  Rise, upper transit, set and lower transit for one body at one location, with an explicit status at extreme latitudes (circumpolar, never rises) instead of missing values. Accepts fixed radec targets. For the Sun specifically, astro_sun returns richer twilight structure; for positions between events use astro_positions.

  Paramètres, retour & exemple (10)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • end · string · optionnel
    Last day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • body · string · requis
    One of sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, or a fixed J2000 target as "radec:RA,DEC" with RA in hours (0-24) and DEC in degrees (-90..90), e.g. "radec:5.6,-5.4" for the Orion Nebula region.
  • date · string · optionnel
    ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • start · string · optionnel
    First day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • cursor · string · optionnel
    Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page.
  • search_horizon_days · integer · optionnel
    How many days ahead to search when an event does not occur on the requested day (high latitudes).

  Exemple d'appel

  {"name": "astro_rise_set", "arguments": {"body": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_sky_today≈ 1010 tokens

  One-call snapshot of the whole sky for a place and moment: moon phase and illumination, which planets are up and worth looking at, the next eclipse, and (with a location) sun times. Reach for this first when the question is broad, like "what is in the sky tonight". For solar-day detail use astro_sun; for choosing an observing night use astro_dark_window; for one planet's exact position use astro_positions.

  Paramètres, retour & exemple (5)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.

  Exemple d'appel

  {"name": "astro_sky_today", "arguments": {"tz": "texte", "lat": 1, "lon": 1, "date": "texte", "place": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

• astro_sun≈ 1874 tokens

  The complete solar day for one location: sunrise, sunset, solar noon, day length, civil, nautical and astronomical twilight boundaries, and explicit polar day/night status at high latitudes. Location required. For a series, send start and end (step is whole days, e.g. "1d" or "7d"). For "is it dark enough to observe" prefer astro_dark_window; for a broad snapshot prefer astro_sky_today.

  Paramètres, retour & exemple (9)

  Paramètres

  • tz · string · optionnel
    IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone.
  • end · string · optionnel
    Last day of a range. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • lat · number · optionnel
    Latitude in decimal degrees, north positive. Send lat and lon together.
  • lon · number · optionnel
    Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
  • date · string · optionnel
    Single day to report, ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • step · string · optionnel
    Range stride in whole days, e.g. "1d", "7d", "30d". Default "1d".
  • place · string · optionnel
    Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attribution field, which must be preserved when shown.
  • start · string · optionnel
    First day of a range (use with end instead of date). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Or jd: followed by a Julian Day on the UT scale, e.g. "jd:2461000.5". On astro_positions, date may list up to 24 datetimes separated by commas, answered in the order sent. Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the ephemeris is not reliable there.
  • cursor · string · optionnel
    Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page.

  Exemple d'appel

  {"name": "astro_sun", "arguments": {"tz": "texte", "end": "texte", "lat": 1, "lon": 1, "date": "texte", "step": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "rights": "texte", "warnings": [], "attribution": "texte", "next_cursor": "texte", "not_computed": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.cyclecalcs.com/mcp