Skip to content

Astro Agents - research-grade astronomical data API MCP server

io.github.aidatatools-dev/astro-agentsaidatatools-devstreamable-httpv1.10.0Scanned

Research-grade astronomical data API: NASA/JPL DE440 ephemerides, any date, SHA-256 verifiable.

20 tools: 18 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 18 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

18 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Astro Agents - research-grade astronomical data API MCP server can do

The Astro Agents - research-grade astronomical data API MCP server is published by the GitHub account aidatatools-dev. It has 20 tools. It can create or change data (18 tools: rise_set_times, altitude_azimuth, observation_windows, moon_details and 14 more), but cannot delete data. 2 tools only read.

1 tool reads private data (astro_catalog).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 8 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.10.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

20 tools

Changes things 18Claude Code: ask
  • altitude_azimuthWhere the Sun, Moon and planets are in the sky from a place at a moment: altitude, azimuth, compass point, topocentric right ascension and declination, distance, elongation, illumi…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Where the Sun, Moon and planets are in the sky from a place at a moment: altitude, azimuth, compass point, topocentric right ascension and declination, distance, elongation, illumination, magnitude and the sky state. E.g. {datetime: '2026-06-21T23:00', latitude: 48.8566, longitude: 2.3522}. For sky maps, telescope pointing, AR and observation apps: each body's apparent altitude and azimuth (with refraction, or airless), whether it is above the horizon, its topocentric right ascension and declination, distance (and the Moon's in km), angular distance from the Sun, illuminated fraction and visual magnitude (planets), plus the sky state (day, civil / nautical / astronomical twilight, night). Matches NASA/JPL Horizons to under a second of arc. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/altaz (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Altitude and azimuth of every body from a place
  • angular_separationsAngular separations between planets at a moment, or between longitudes you supply: the pairs near 0, 60, 90, 120 or 180 degrees (or any angle you choose) with the deviation, approa…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Angular separations between planets at a moment, or between longitudes you supply: the pairs near 0, 60, 90, 120 or 180 degrees (or any angle you choose) with the deviation, approaching or receding; optionally equal and opposite declinations. E.g. {longitudes: {sun: 54.4, moon: 297.4}}. For a moment (computed from DE440) or for longitudes you supply: every pair of bodies at a chosen separation angle, with its deviation from the exact angle, the tolerance applied, and whether the bodies are approaching or receding from it. Option 'declination': pairs with equal or opposite declinations. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.02 per call via REST POST https://astro-agent.dev/v1/astronomy/angles (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Angular separations between bodies
  • body_positionsPlanetary positions and ephemeris API (NASA/JPL DE440): the ecliptic longitude, latitude, speed, retrograde flag and distance of the Sun, Moon, planets and lunar nodes at any momen…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Planetary positions and ephemeris API (NASA/JPL DE440): the ecliptic longitude, latitude, speed, retrograde flag and distance of the Sun, Moon, planets and lunar nodes at any moment 1800-2200, geocentric or heliocentric, ecliptic or equatorial (right ascension, declination). E.g. {datetime: '2026-10-01T12:00:00Z'}. Geocentric apparent positions from NASA/JPL DE440 (true ecliptic and equinox of date, IAU 2006/2000A), with the Moon's ascending and descending nodes and its mean apogee. Location is optional (only used to interpret a local time). Options: 'heliocentric' perspective (seen from the Sun) and 'equatorial' coordinates (right ascension, declination, and whether |declination| exceeds the obliquity). Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/positions (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Planetary positions for any date (ephemeris)
  • celestial_eventsCelestial event calendar: the exact UTC minute and unix timestamp of every solar and lunar eclipse, planetary station (retrograde / direct), lunation and separation between two dat…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Celestial event calendar: the exact UTC minute and unix timestamp of every solar and lunar eclipse, planetary station (retrograde / direct), lunation and separation between two dates, 1800-2200. E.g. {start: '2026-01-01', end: '2026-12-31', include: ['eclipse', 'station']}. A calendar of exact events between two dates: solar and lunar eclipses (type and magnitude), stations (retrograde / direct), new and full Moons and quarters, separations between planets at chosen angles, ecliptic longitudes crossing multiples of 30 degrees, equal / opposite declinations, and declinations passing the obliquity of the ecliptic. Geocentric or heliocentric. Each event has its UTC minute, a unix timestamp and a stable key. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.25 per call via REST POST https://astro-agent.dev/v1/astronomy/events (x402 or MPP); always paid, never a free call.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Celestial event calendar (eclipses, stations, lunations)
  • convert_coordinatesConvert sky coordinates between equatorial (J2000, of date), ecliptic, galactic and horizontal (alt-az) frames.1 finding

    Why it is in this group

    • The name "convert_coordinates" says "convert": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "convert_coordinates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_coordinates" says "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Convert sky coordinates between equatorial (J2000, of date), ecliptic, galactic and horizontal (alt-az) frames. E.g. {frame: 'equatorial_j2000', coordinates: {ra_hours: 6.7525, dec: -16.7161}, datetime: '2026-06-21T21:00:00Z', latitude: 48.8566, longitude: 2.3522}. For catalogues, planetarium and telescope software: give a direction in one frame and get it in all the others: equatorial J2000 (ICRS) and of date, ecliptic J2000 and of date, galactic, and horizontal (altitude, azimuth) when a datetime and a place are given. Geometric frame rotations of a direction (no aberration or refraction is added: use astronomy/altaz for where a body appears). Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/convert (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Coordinate conversion between sky frames
  • day_summaryToday's sky for a place in one call: sunrise, sunset, twilight, golden and blue hour, the Moon's phase and moonrise, the planets visible tonight, the next lunations and the next ec…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Today's sky for a place in one call: sunrise, sunset, twilight, golden and blue hour, the Moon's phase and moonrise, the planets visible tonight, the next lunations and the next eclipse. E.g. {date: '2026-08-10', latitude: 48.8566, longitude: 2.3522}. The daily sky block of a weather, calendar or outdoor app, in one request: the Sun (rise, solar noon, set, civil / nautical / astronomical dawn and dusk, day length, golden and blue hour), the Moon (phase, illuminated fraction, age, distance, moonrise, transit, moonset, the next principal phase), the planets observable that night (window, best time, altitude, azimuth, magnitude; brightest first), the lunations and planetary stations of the next 7 days, and the next solar or lunar eclipse anywhere on Earth. Local times with offset, UTC and unix timestamps; each block follows the conventions of its own route. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.02 per call via REST POST https://astro-agent.dev/v1/astronomy/day (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Astronomical summary of the day for a place
  • local_eclipseSolar and lunar eclipses seen from a place: local type, contact times (C1-C4, P1-P4, U1-U4), magnitude, obscuration, duration of totality and the Sun's or Moon's altitude.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Solar and lunar eclipses seen from a place: local type, contact times (C1-C4, P1-P4, U1-U4), magnitude, obscuration, duration of totality and the Sun's or Moon's altitude. E.g. {start: '2026-08-01', end: '2026-08-31', latitude: 39.47, longitude: -0.38}. For eclipse chasers, planetariums, schools and travel apps: solar eclipses from the place's own viewpoint (local type: total, annular, partial or none; contacts C1, C2, maximum, C3, C4 with the Sun's altitude and azimuth; magnitude, obscuration, duration, duration of totality or annularity) and lunar eclipses (penumbral and umbral contacts P1, U1, U2, maximum, U3, U4, P4 with the Moon's altitude, umbral and penumbral magnitude, durations), each marked visible when the body is above the horizon. Matches NASA's predictions to a few seconds (2024-04-08 at Dallas, 2025-03-14 lunar eclipse). Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.10 per call via REST POST https://astro-agent.dev/v1/astronomy/eclipse-local (x402 or MPP); always paid, never a free call.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Local circumstances of solar and lunar eclipses
  • longitude_seriesPlanetary longitude time series: planet degrees seen from the Earth and from the Sun (geocentric and heliocentric) at a moment or every hour to every week, as pandas-ready columns,…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Planetary longitude time series: planet degrees seen from the Earth and from the Sun (geocentric and heliocentric) at a moment or every hour to every week, as pandas-ready columns, with speeds, retrograde flags and declinations. E.g. {start: '2024-01-01', end: '2024-12-31', interval: '1w', bodies: ['jupiter', 'saturn']}. Planetary longitudes as data: at a moment, or as a series of up to 1000 samples (columns ready for pandas). Geocentric apparent and heliocentric geometric, each with its speed and retrograde flag; optional offsets (longitude + angle), circular or arithmetic multi-body averages, unwrapped degrees for plotting, and declinations. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.20 per call via REST POST https://astro-agent.dev/v1/astronomy/longitude-series (x402 or MPP); always paid, never a free call.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Planetary longitude series (geocentric + heliocentric)
  • moon_detailsMoon phase today and in detail: phase name and angle, illuminated fraction, age, distance, apparent size, the next new, quarter and full Moons, and the next perigee and apogee; wit…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Moon phase today and in detail: phase name and angle, illuminated fraction, age, distance, apparent size, the next new, quarter and full Moons, and the next perigee and apogee; with a place, moonrise and moonset. E.g. {datetime: '2026-01-03T12:00:00Z'}. For calendar, weather, photography and tide apps: phase (8 names), phase angle, illuminated fraction, waxing or waning, age in days since the new Moon, Brown lunation number, centre-to-centre distance in km and Earth radii, angular diameter, ecliptic position, the previous new Moon, the next four principal phases and the next perigee and apogee with their distances, to the second. With latitude/longitude: the Moon's altitude and azimuth there and that local day's moonrise, transit and moonset. Perigee and apogee match NASA/JPL Horizons to the minute. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/moon (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Moon phase, illumination, distance and next phases
  • observation_windowsWhich planets and the Moon can be observed tonight from a place, and when: windows above a minimum altitude while the sky is dark, with the best time, altitude, azimuth and magnitu…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Which planets and the Moon can be observed tonight from a place, and when: windows above a minimum altitude while the sky is dark, with the best time, altitude, azimuth and magnitude. E.g. {date: '2026-06-21', latitude: 48.8566, longitude: 2.3522}. For observation planning: over the night that starts on 'date' (local noon to noon), the intervals when each body stands at least min_altitude_deg above the horizon while the Sun is at or below sun_altitude_max_deg (default -6: after civil dusk), each with start, end, duration and the best moment (highest altitude) with its azimuth and visual magnitude; plus the dark interval itself. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.02 per call via REST POST https://astro-agent.dev/v1/astronomy/visibility (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Observation windows for a night
  • planetary_phenomenaPlanetary phenomena between two dates: oppositions, conjunctions with the Sun, greatest elongations of Mercury and Venus, conjunctions between planets, perihelion and aphelion.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Planetary phenomena between two dates: oppositions, conjunctions with the Sun, greatest elongations of Mercury and Venus, conjunctions between planets, perihelion and aphelion. E.g. {start: '2026-01-01', end: '2026-12-31', include: ['opposition']}. For almanacs, observing guides and astronomy newsletters: between two dates (up to 366 days, 1800-2199), each planet's conjunctions with the Sun, oppositions (with the Earth distance), greatest elongations east or west (with the angle), conjunctions between planets (with their angular separation and distance from the Sun), and perihelion and aphelion (heliocentric distance), each with a stable key. Matches the published 2026 dates. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.10 per call via REST POST https://astro-agent.dev/v1/astronomy/phenomena (x402 or MPP); always paid, never a free call.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Planetary phenomena: oppositions, conjunctions, elongations
  • rise_set_timesSunrise, sunset, moonrise, moonset and twilight times for a place and date: rise, transit and set of the Sun, Moon and planets, civil/nautical/astronomical dawn and dusk, day lengt…1 finding

    Why it is in this group

    • The name "rise_set_times" says "set": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "rise_set_times" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "rise_set_times" says "set": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Sunrise, sunset, moonrise, moonset and twilight times for a place and date: rise, transit and set of the Sun, Moon and planets, civil/nautical/astronomical dawn and dusk, day length, golden hour and blue hour, in UTC and local time. E.g. {date: '2026-06-21', latitude: 48.8566, longitude: 2.3522}. For sky, weather, photography and outdoor apps: for one local calendar day at a place (time zone and DST resolved from the coordinates), each body's rise and set (with azimuth) and upper transit (with altitude), or 'always_up' / 'always_down' when it neither rises nor sets (polar day and night); for the Sun, dawn and dusk at -6, -12 and -18 degrees, solar noon, day length, and the golden hour (Sun between -4 and +6 degrees) and blue hour (-6 to -4) intervals. Times in UTC to the second, local time with its offset, and unix timestamps; every convention (refraction, limb, horizon) is in result.settings. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/rise-set (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Rise, set and twilight times for a place
  • seasonsEquinoxes and solstices of a year, Earth's perihelion and aphelion, and optionally the Sun day by day (sunrise, sunset, day length, declination, equation of time) for a place.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Equinoxes and solstices of a year, Earth's perihelion and aphelion, and optionally the Sun day by day (sunrise, sunset, day length, declination, equation of time) for a place. E.g. {year: 2026}. For calendars, almanacs, education and solar apps: the March and September equinoxes and the June and December solstices (UTC, and local with a place), Earth's perihelion and aphelion with their distances, and with daily=true a row per day: solar noon, the Sun's apparent declination, the equation of time and, for a place, sunrise, sunset and day length, plus the longest and shortest days. Matches the published 2026 times to the minute. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/seasons (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Equinoxes, solstices, perihelion and day length over a year
  • similar_skiesSky similarity search: find the past or future dates whose planetary positions best match a reference sky, ranked by a stated angular distance in degrees.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Sky similarity search: find the past or future dates whose planetary positions best match a reference sky, ranked by a stated angular distance in degrees. E.g. {reference: '2026-10-29T00:00Z', direction: 'past', bodies: ['jupiter', 'saturn']}. Searches a date grid (1 hour to 1 week steps, 1800-2200) for the skies closest to a reference: by longitude, by the separations between bodies, by declination, optionally with the same retrograde flags. The score is a weighted mean angular distance in degrees, defined in result.settings.metric. Data for your own analysis — never a signal or forecast. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.25 per call via REST POST https://astro-agent.dev/v1/astronomy/sky-analogues (x402 or MPP); always paid, never a free call.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Sky similarity search (matching skies)
  • sky_nowThe sky now (no location needed): planet positions, retrograde planets and the Moon phase, plus the exact UTC minute of the next stations, lunations and separations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The sky now (no location needed): planet positions, retrograde planets and the Moon phase, plus the exact UTC minute of the next stations, lunations and separations. E.g. {datetime: '2026-10-01T00:00Z', days: 30}. One call for 'what is happening in the sky': positions, retrograde planets, the Moon's phase, and the events of the next days (1-90): stations, lunations, separations of 0, 60, 90, 120 and 180 degrees, and ecliptic longitudes crossing multiples of 30 degrees, each to the minute (UTC). Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/sky (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: The sky now: positions, Moon phase, next events
  • solunar_periodsSolunar periods for a place and day: major periods around the Moon's upper and lower transits, minor periods around moonrise and moonset, in local time.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Solunar periods for a place and day: major periods around the Moon's upper and lower transits, minor periods around moonrise and moonset, in local time. E.g. {date: '2026-06-21', latitude: 48.8566, longitude: 2.3522}. For fishing, hunting and outdoor apps that use the solunar timing convention: for one local day at a place, each major period (centred on the Moon's upper transit overhead and lower transit underfoot, 2 h by default) and minor period (centred on moonrise and moonset, 1 h by default) with its start, centre and end in local time, the Moon's altitude at its transits and its phase. The events are exact (astronomy/rise-set conventions); the windows are the convention's, adjustable. No rating attached. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/solunar (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Solunar periods: lunar transits, moonrise and moonset
  • time_scalesJulian day, modified Julian day, sidereal time (Greenwich and local, mean and apparent), Delta T, TAI-UTC and UT1-UTC for a moment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Julian day, modified Julian day, sidereal time (Greenwich and local, mean and apparent), Delta T, TAI-UTC and UT1-UTC for a moment. E.g. {datetime: '2026-06-21T12:00:00Z', longitude: 2.35, latitude: 48.86}. For telescope control, data reduction and education: the Julian day in UTC, UT1, TT and TDB, the modified Julian day, Julian centuries since J2000 (TT), Delta T (TT - UT1), TAI - UTC and UT1 - UTC, Greenwich mean and apparent sidereal time and, with a longitude, the local ones; plus day of year and ISO week. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/time (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Julian day, sidereal time, Delta T and time scales
  • verify_result_hashVerify that an astronomical data result was not altered: recompute the SHA-256 of a 'result' object returned by any tool and compare it with the result_sha256 you hold.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify that an astronomical data result was not altered: recompute the SHA-256 of a 'result' object returned by any tool and compare it with the result_sha256 you hold. Free.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Verify a result hash (free)
Only reads 2Show 2 read-only tools
  • astro_catalogList every astronomical data and ephemeris tool with its price, input schema and an example request: planet positions, event calendar (eclipses, Mercury retrograde), longitude seri…Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
    Description, as the server wrote it
    List every astronomical data and ephemeris tool with its price, input schema and an example request: planet positions, event calendar (eclipses, Mercury retrograde), longitude series, sky similarity search and more. Free; call it first to pick the right tool.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Catalog (free)
  • resolve_local_timeLocal time to UTC conversion: convert a local date, time and place into exact Universal Time, with the historical time zone and UTC offset, Delta T, Local Mean Time and true solar …No findings

    Why it is in this group

    • The name "resolve_local_time" says "resolve": a word for reading.
    Description, as the server wrote it
    Local time to UTC conversion: convert a local date, time and place into exact Universal Time, with the historical time zone and UTC offset, Delta T, Local Mean Time and true solar time. E.g. {datetime: '1947-08-15T00:00', latitude: 28.6139, longitude: 77.209}. Resolves the IANA time zone from coordinates, applies the offset in force on that date (historical daylight saving, Local Mean Time before standard time), flags ambiguous or non-existent local times instead of guessing, and returns Julian Days (UT/TT), Delta T, Local Mean Time, true (apparent) solar time and the equation of time. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/astronomy/local-time (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Local time resolver (historical time zones)

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:01 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
18
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 18 tools that change things (18 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://astro-agent.dev/mcp: tools/list returned 20 tools to an anonymous client, including rise_set_times (write), altitude_azimuth (write), observation_windows (write), moon_details (write), day_summary (write) and 13 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 22 to 18
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 20 to 22
  3. Oct 29, 2026
    • Tools that change things, listed without credentials: 14 to 20

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "rise_set_times" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "rise_set_times" says "set": a word for a change.

    What this check looks for
  • The server marks "convert_coordinates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_coordinates" says "convert": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 22 -> 18.View diff
    • Tools that change things, listed without credentials: 22 to 18
  2. Tools7 added, 10 removed, 1 changed.+7 added−10 removed~1 changedView diff
  3. Tools11 added, 12 removed, 11 changed.+11 added−12 removed~11 changedView diff
    • Added:altitude_azimuthChanges things
    • Added:convert_coordinatesChanges things
    • Added:day_summaryChanges things
    • Added:local_eclipseChanges things
    • Added:moon_detailsChanges things
    • Added:observation_windowsChanges things
    • Added:planetary_phenomenaChanges things
    • Added:rise_set_timesChanges things
    • Added:seasonsChanges things
    • Added:solunar_periodsChanges things
    • Added:time_scalesChanges things
    • Removed:doshas
    • Removed:gun_milan
    • Removed:kp_chart
    • Removed:kundli
    • Removed:kundli_full
    • Removed:nakshatras
    • Removed:panchang
    • Removed:token_chart
    • Removed:token_synastry
    • Removed:vedic_report
    • Removed:vimshottari_dasha
    • Removed:yogas
    • Changed:aspectsChanges thingstitledescriptioninputSchemaannotations
    • Changed:astro_catalogOnly readsdescription
    • Changed:astro_event_calendarChanges thingstitledescriptionannotations
    • Changed:natal_chartChanges thingstitledescriptioninputSchemaannotations
    • Changed:planet_positionsChanges thingsdescriptioninputSchema
    • Changed:planetary_linesChanges thingstitledescriptioninputSchemaannotations
    • Changed:resolve_birth_timeOnly readstitledescriptioninputSchemaannotations
    • Changed:sky_analoguesChanges thingstitledescriptioninputSchemaannotations
    • Changed:sky_todayChanges thingsdescriptioninputSchema
    • Changed:synastryChanges thingstitledescriptioninputSchemaannotations
    • Changed:transitsChanges thingsdescriptioninputSchema
  4. Tools5 changed.~5 changedView diff
    • Changed:astro_catalogOnly readsdescription
    • Changed:astro_event_calendarChanges thingstitledescriptionannotations
    • Changed:planetary_linesChanges thingsdescription
    • Changed:sky_analoguesChanges thingsdescription
    • Changed:sky_todayChanges thingsdescription
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 20 -> 22.View diff
    • Tools that change things, listed without credentials: 20 to 22
  6. Tools1 changed.~1 changedView diff
    • Changed:token_synastryChanges thingsdescription
  7. Tools2 added.+2 addedView diff
    • Added:token_chartChanges things
    • Added:token_synastryChanges things
  8. Tools1 added, 6 changed.+1 added~6 changedView diff
    • Added:sky_analoguesChanges things
    • Changed:astro_catalogOnly readsdescription
    • Changed:astro_event_calendarChanges thingstitledescriptionannotations
    • Changed:natal_chartChanges thingstitleannotations
    • Changed:planet_positionsChanges thingstitledescriptionannotations
    • Changed:planetary_linesChanges thingsdescription
    • Changed:sky_todayChanges thingstitleannotations
  9. PostureRemote posture changed. Tools that change things, listed without credentials: 14 -> 20.View diff
    • Tools that change things, listed without credentials: 14 to 20
  10. Tools3 added, 16 changed.+3 added~16 changedView diff
    • Added:astro_event_calendarChanges things
    • Added:planetary_linesChanges things
    • Added:sky_todayChanges things
    • Changed:aspectsChanges thingsdescriptioninputSchema
    • Changed:doshasChanges thingsdescription
    • Changed:gun_milanChanges thingsdescription
    • Changed:kp_chartChanges thingsdescription
    • Changed:kundliChanges thingsdescription
    • Changed:kundli_fullChanges thingsdescription
    • Changed:nakshatrasChanges thingsdescription
    • Changed:natal_chartChanges thingsdescription
    • Changed:panchangChanges thingsdescription
    • Changed:planet_positionsChanges thingsdescriptioninputSchema
    • Changed:resolve_birth_timeOnly readsdescription
    • Changed:synastryChanges thingsdescription
    • Changed:transitsChanges thingsdescription
    • Changed:vedic_reportChanges thingsdescription
    • Changed:vimshottari_dashaChanges thingsdescription
    • Changed:yogasChanges thingsdescription

Install

Pinned to version 1.10.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http astro-agents https://astro-agent.dev/mcp
claude mcp add --transport http astro-agents https://astro-agent.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__astro-agents__resolve_local_time",
      "mcp__astro-agents__astro_catalog"
    ],
    "ask": [
      "mcp__astro-agents__rise_set_times",
      "mcp__astro-agents__altitude_azimuth",
      "mcp__astro-agents__observation_windows",
      "mcp__astro-agents__moon_details",
      "mcp__astro-agents__day_summary",
      "mcp__astro-agents__seasons",
      "mcp__astro-agents__time_scales",
      "mcp__astro-agents__convert_coordinates",
      "mcp__astro-agents__planetary_phenomena",
      "mcp__astro-agents__local_eclipse",
      "mcp__astro-agents__solunar_periods",
      "mcp__astro-agents__body_positions",
      "mcp__astro-agents__sky_now",
      "mcp__astro-agents__angular_separations",
      "mcp__astro-agents__celestial_events",
      "mcp__astro-agents__longitude_series",
      "mcp__astro-agents__similar_skies",
      "mcp__astro-agents__verify_result_hash"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as astro-agents. Review it before you use it.

Capability tags behind 1 rule
  • mcp__astro-agents__astro_catalog private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.aidatatools-dev/astro-agents/verify?hash=6f7230435cb836aac522951c46ba5c9cb02daa9af1e3794a714ea1c02e159f0c" | jq -e '.changed == false'

Pinned hash 6f7230435cb8, from Nov 19, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.aidatatools-dev/astro-agents/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.aidatatools-dev/astro-agents
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.aidatatools-dev/astro-agents.svg)](https://radar.anlyon.com/servers/io.github.aidatatools-dev/astro-agents)

Source: MCP Registry · repository. Synced Nov 19, 2026, 18:18 UTC.

Astro Agents - research-grade astronomical data API MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Astro Agents - research-grade astronomical data API MCP server safe?

No scan can promise that. What its definitions show: 20 tools, 18 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Astro Agents - research-grade astronomical data API MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Astro Agents - research-grade astronomical data API MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Astro Agents - research-grade astronomical data API MCP server have?

20 tools: 18 write, 2 read. rise_set_times, altitude_azimuth, observation_windows, moon_details, day_summary, seasons, time_scales, convert_coordinates and 12 more.

Does the Astro Agents - research-grade astronomical data API MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Astro Agents - research-grade astronomical data API MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Astro Agents - research-grade astronomical data API MCP server changed its tools?

Yes, 8 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.