astronomy-mcp-server

endpoint

https://astronomy.caseyjhand.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is astronomy-mcp-server live?

Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.

Is astronomy-mcp-server free to use?

Yes — the hub reached it with no key and no payment.

What tools does astronomy-mcp-server have?

7 tools: astronomy_find_events, astronomy_get_ephemeris, astronomy_get_satellite_passes, astronomy_get_sky_position, astronomy_list_visible, astronomy_get_rise_set, astronomy_get_moon_phase.

Is astronomy-mcp-server safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• astronomy_get_moon_phase reads open 24h ago

  Report the Moon phase for an instant: illuminated fraction, phase name, synodic age in days since the new moon, phase longitude (the Moon–Sun ecliptic-longitude difference, 180° at full), and the next four quarter phases (new, first quarter, full, last quarter) with timestamps. Answers "what is the moon phase tonight" and "when is the next full moon" in one call without iteration. The time defaults to now; pass an IANA `timezone` to also receive observer-local timestamps. The phase is geocentric — no observer location is needed.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "time": {
        "type": "string",
        "description": "Instant to evaluate as an ISO 8601 UTC string, e.g. \"2024-12-15T00:00:00Z\". Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "timezone": {
        "type": "string",
        "description": "IANA timezone for localized output, e.g. \"America/Los_Angeles\". When omitted, output is UTC-only."
      }
    },
    "additionalProperties": false
  }

  arguments 15 lines copy
• astronomy_find_events reads unknown 15h ago

  Search forward from a start time for the next occurrences of one sky-event class, selected by the `event` enum: solar_eclipse, lunar_eclipse, equinox, solstice, moon_quarter, opposition, conjunction, max_elongation, or perigee_apogee. Both eclipse classes take an optional observer (latitude and longitude together). solar_eclipse without one returns global eclipses — kind, peak time, obscuration, and for a total or annular eclipse the latitude/longitude where it is greatest; with one it returns only eclipses visible from that point, with local contact times, `local_visible`, and the Sun's altitude at each contact. lunar_eclipse returns geocentric contact times, the same instants everywhere on Earth; an observer adds `local_visible` and the Moon's altitude at each contact. Every other class is geocentric and ignores a location. The body-relative events (opposition, conjunction, max_elongation, perigee_apogee) require a `body`: opposition applies to the superior planets (mars through pluto), conjunction to any planet, max_elongation to mercury and venus, and perigee_apogee to the moon (perigee/apogee), earth, or a planet (perihelion/aphelion). Returns the next `count` occurrences (default 1). Searches stop at the end of 2100, the close of the supported span; when that leaves fewer than `count`, a notice says so. Start defaults to now; pass an IANA `timezone` for observer-local timestamps.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "event"
    ],
    "properties": {
      "body": {
        "enum": [
          "sun",
          "moon",
          "mercury",
          "venus",
          "mars",
          "jupiter",
          "saturn",
          "uranus",
          "neptune",
          "pluto",
          "earth"
        ],
        "type": "string",
        "description": "Target body — required for opposition, conjunction, max_elongation, and perigee_apogee; ignored otherwise. \"earth\" is accepted only for perigee_apogee, which returns its perihelion and aphelion."
      },
      "count": {
        "type": "integer",
        "default": 1,
        "maximum": 20,
        "minimum": 1,
        "description": "Number of forward occurrences to return. Default 1, max 20."
      },
      "event": {
        "enum": [
          "solar_eclipse",
          "lunar_eclipse",
          "equinox",
          "solstice",
          "moon_quarter",
          "opposition",
          "conjunction",
          "max_elongation",
          "perigee_apogee"
        ],
        "type": "string",
        "description": "Which class of event to search for."
      },
      "start": {
        "type": "string",
        "description": "Search start as an ISO 8601 UTC string, e.g. \"2024-01-01T00:00:00Z\". Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "latitude": {
        "type": "number",
        "maximum": 90,
        "minimum": -90,
        "description": "Observer latitude in decimal degrees, supplied together with longitude. Optional for solar_eclipse and lunar_eclipse, where it adds local circumstances; omit both for a global solar search. Ignored by every other event."
      },
      "timezone": {
        "type": "string",
        "description": "IANA timezone for localized output, e.g. \"America/Los_Angeles\". When omitted, output is UTC-only."
      },
      "elevation": {
        "type": "number",
        "default": 0,
        "description": "Observer elevation in meters above sea level. Default 0."
      },
      "longitude": {
        "type": "number",
        "maximum": 180,
        "minimum": -180,
        "description": "Observer longitude in decimal degrees, supplied together with latitude. Optional for solar_eclipse and lunar_eclipse; ignored by every other event."
      }
    },
    "additionalProperties": false
  }

  arguments 74 lines copy
• astronomy_get_ephemeris reads unknown 15h ago

  Fetch a time-series ephemeris for a small body (asteroid or comet) or spacecraft from JPL Horizons — RA/Dec, distance, and apparent magnitude over a span, optionally with observer-relative altitude/azimuth. This covers objects the in-process major-body set cannot. The designation is passed to Horizons verbatim, so it must be in a form Horizons resolves to a single record: a numbered asteroid takes a trailing-semicolon record lookup (e.g. "433;" for Eros, "1;" for Ceres), and a periodic comet takes the DES + closest-apparition form (e.g. "DES=1P;CAP" for Halley). Spacecraft take their negative SPK-ID. Anything else goes through the Horizons name search: a bare name matching nothing (e.g. "433 Eros") or several records (e.g. "1P/Halley") is rejected, but one matching a single object succeeds even when that object is not the one meant — "Eros" resolves to Kerberos, a moon of Pluto — so compare `target_name`, the object Horizons resolved, with the one intended. `start` and `stop` are ISO 8601 UTC and `stop` must be after `start`; `step` is a count plus a unit of m, h, d, mo, or y, such as "1d", "1h", or "10m". Supplying observer latitude/longitude yields topocentric coordinates and adds alt/az — supply both or neither. This is a gated, network-backed extension (JPL Horizons is keyless but rate-limited and best-effort); large spans truncate inline at 200 rows, and the truncation notice names the exact `start` to resume from — one step past the last row returned, because Horizons includes the start instant in its output — so re-calling from there continues the series without repeating a sample. Splitting the range into smaller adjacent spans works too; keep the same step either way so no sample is lost.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "designation"
    ],
    "properties": {
      "step": {
        "type": "string",
        "default": "1h",
        "description": "Step size as a positive count plus a unit of m (minutes), h (hours), d (days), mo (months), or y (years), e.g. \"10m\", \"1h\", \"1d\". Default \"1h\"."
      },
      "stop": {
        "type": "string",
        "description": "Ephemeris stop as an ISO 8601 UTC string, and must be later than start. Defaults to 24 hours after start. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "start": {
        "type": "string",
        "description": "Ephemeris start as an ISO 8601 UTC string, e.g. \"2024-01-01T00:00:00Z\". Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "latitude": {
        "type": "number",
        "maximum": 90,
        "minimum": -90,
        "description": "Observer latitude in decimal degrees — supply together with longitude for topocentric coordinates and alt/az. Supplying one without the other is rejected."
      },
      "elevation": {
        "type": "number",
        "default": 0,
        "description": "Observer elevation in meters above sea level. Default 0."
      },
      "longitude": {
        "type": "number",
        "maximum": 180,
        "minimum": -180,
        "description": "Observer longitude in decimal degrees. Supply together with latitude; one without the other is rejected."
      },
      "designation": {
        "type": "string",
        "minLength": 1,
        "description": "JPL Horizons target, passed verbatim — use a form that resolves to one record. Numbered asteroid: trailing-semicolon record lookup, e.g. \"433;\" (Eros), \"1;\" (Ceres). Periodic comet: DES + closest-apparition flag, e.g. \"DES=1P;CAP\" (Halley), \"DES=2P;CAP\" (Encke). Spacecraft: negative SPK-ID, e.g. \"-48\" (Hubble). A bare name like \"433 Eros\" (no match) or \"1P/Halley\" (several records) is rejected, but one matching a single object succeeds even when it is not the object meant — check `target_name` in the result. Look up designations at ssd.jpl.nasa.gov/tools/sbdb_lookup.html."
      }
    },
    "additionalProperties": false
  }

  arguments 45 lines copy
• astronomy_get_satellite_passes reads unknown 24h ago

  Predict visible passes of a satellite (e.g. the ISS, NORAD 25544) over an observer in the next `days`. Identify the satellite by exactly one of `norad_id` or `name` — supplying both, or neither, is rejected. A few well-known common names resolve directly to their catalog numbers, ignoring case: ISS or International Space Station (25544), Hubble, Hubble Space Telescope, or HST (20580), and Tiangong, CSS, or Chinese Space Station (48274). Any other `name` is matched as a case-insensitive substring of CelesTrak's catalog names, so it resolves only when it picks out a single object: a broader query comes back with the matching objects and their catalog numbers to choose from. Either way the result echoes the query that resolved it as `resolved_from_name`. Fetches the object's current GP element set from CelesTrak, propagates it with SGP4 in-process, and returns each pass's rise, peak, and set times with azimuths and the peak elevation. Only passes that are naked-eye-plausible are returned — the satellite must be sunlit at peak while the observer's sky is dark. Every returned pass rises within the requested window: a pass already underway at `start` is omitted rather than reported with `start` as its rise, so back up `start` to see it, while a pass still up when the window ends is reported through its actual set. A `start` further than about a month from the element set's epoch is rejected as out of range on that distance alone, and an element set that will not propagate to a window inside that horizon is rejected as a reentry — so an empty `passes` means only that nothing was visible. CelesTrak publishes only current element sets, so in practice `start` must be within about a month of today. NORAD catalog numbers and catalog names are found at celestrak.org or heavens-above.com. This is a gated, network-backed extension (CelesTrak is keyless but rate-limited; element sets are cached briefly). Default elevation 0 m; pass an IANA timezone for observer-local pass times.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677

  {
    "type": "object",
    "oneOf": [
      {
        "not": {
          "required": [
            "name"
          ]
        },
        "type": "object",
        "required": [
          "norad_id"
        ]
      },
      {
        "not": {
          "required": [
            "norad_id"
          ]
        },
        "type": "object",
        "required": [
          "name"
        ]
      }
    ],
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "latitude",
      "longitude"
    ],
    "properties": {
      "days": {
        "type": "integer",
        "default": 7,
        "maximum": 10,
        "minimum": 1,
        "description": "Number of days ahead to search for passes. Default 7, max 10."
      },
      "name": {
        "type": "string",
        "description": "Satellite name to resolve, e.g. \"ISS (ZARYA)\". The common names ISS, International Space Station, Hubble, Hubble Space Telescope, HST, Tiangong, CSS, and Chinese Space Station resolve directly to their catalog numbers, ignoring case and surrounding whitespace. Any other name is matched against CelesTrak as a case-insensitive substring of the catalog name, so give the fullest name you have — a short one matches many objects and is rejected as ambiguous. Mutually exclusive with `norad_id` — supply exactly one."
      },
      "start": {
        "type": "string",
        "description": "Search start as an ISO 8601 UTC string, within about a month of the current element set's epoch — for a tracked object that epoch is hours old, so in practice within about a month of today. A start further out is rejected rather than answered from elements that no longer describe the orbit. Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "latitude": {
        "type": "number",
        "maximum": 90,
        "minimum": -90,
        "description": "Observer latitude in decimal degrees, north positive."
      },
      "norad_id": {
        "type": "integer",
        "maximum": 9007199254740991,
        "description": "NORAD catalog number of the satellite, e.g. 25544 for the ISS. Found at celestrak.org or heavens-above.com. Mutually exclusive with `name` — supply exactly one.",
        "exclusiveMinimum": 0
      },
      "timezone": {
        "type": "string",
        "description": "IANA timezone for localized pass times, e.g. \"America/Los_Angeles\". When omitted, output is UTC-only."
      },
      "elevation": {
        "type": "number",
        "default": 0,
        "description": "Observer elevation in meters above sea level. Default 0."
      },
      "longitude": {
        "type": "number",
        "maximum": 180,
        "minimum": -180,
        "description": "Observer longitude in decimal degrees, east positive."
      }
    },
    "additionalProperties": false
  }

  arguments 77 lines copy
• astronomy_get_sky_position reads unknown 24h ago

  Compute the apparent topocentric position of one solar-system body (sun, moon, mercury through neptune, pluto) or a named bright star for an observer location and instant. Returns equatorial (RA/Dec), refraction-corrected horizontal (altitude/azimuth), and ecliptic coordinates, plus distance, apparent magnitude, angular diameter, phase angle, illuminated fraction, angular distance from the Sun, and the constellation it falls in. For a solar-system body it also returns that body card — classification, mean radius, naked-eye visibility — the same values served at astronomy://body/{body}, so a client without resource support does not need a second surface to reach them; a catalog star has no card and the field is absent. Positions are parallax- and aberration-corrected for the given observer; default elevation is 0 m and the default time is now. Supply `star` (e.g. "Sirius", "Polaris") instead of `body` to target a catalog star; `body` is ignored when `star` is set. Pass an IANA `timezone` to also receive the observer-local time. This server does not geocode — resolve a place name to latitude/longitude upstream first.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "latitude",
      "longitude"
    ],
    "properties": {
      "body": {
        "enum": [
          "sun",
          "moon",
          "mercury",
          "venus",
          "mars",
          "jupiter",
          "saturn",
          "uranus",
          "neptune",
          "pluto"
        ],
        "type": "string",
        "description": "Solar-system body to locate. Omit when targeting a named star via `star`."
      },
      "star": {
        "type": "string",
        "description": "Named star to locate, from a bundled catalog of 32 stars — about 30 of the brightest naked-eye stars plus Polaris, not an arbitrary star. Accepts a common name or Bayer designation, with the Greek letter spelled out or as a symbol and the constellation as its genitive or IAU abbreviation (e.g. \"Sirius\", \"Alpha Centauri\", \"α CMa\"). A name outside the catalog fails with the full list of catalog stars. Takes precedence over `body`."
      },
      "time": {
        "type": "string",
        "description": "Instant of observation as an ISO 8601 UTC string, e.g. \"2024-04-08T18:00:00Z\". Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "latitude": {
        "type": "number",
        "maximum": 90,
        "minimum": -90,
        "description": "Observer latitude in decimal degrees, north positive."
      },
      "timezone": {
        "type": "string",
        "description": "IANA timezone for localized output, e.g. \"America/Los_Angeles\". When omitted, output is UTC-only."
      },
      "elevation": {
        "type": "number",
        "default": 0,
        "description": "Observer elevation in meters above sea level. Default 0."
      },
      "longitude": {
        "type": "number",
        "maximum": 180,
        "minimum": -180,
        "description": "Observer longitude in decimal degrees, east positive."
      }
    },
    "additionalProperties": false
  }

  arguments 56 lines copy
• astronomy_list_visible reads unknown 15h ago

  The one-call "what is up right now" answer. For an observer location and instant, iterate every naked-eye solar-system body (and, with include_stars, the bundled bright stars), compute altitude and azimuth, keep those above the horizon, rank them brightest-and-highest first, and attach a plain-language visibility note to each, along with its angular distance from the Sun. The whole sky is gated by the Sun's altitude into daylight / civil / nautical / astronomical twilight / dark, returned alongside the list, and each note says when daylight, civil twilight, or the Sun's glare hides or dims that body. `time` is a single evaluation instant, not a window — for "tonight" pass a time after astronomical dusk (use astronomy_get_rise_set on the sun to find it). Default elevation 0 m; use min_altitude to skip objects grazing the horizon. This server does not geocode — resolve coordinates upstream first; pass an IANA timezone for observer-local times on each body.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "latitude",
      "longitude"
    ],
    "properties": {
      "time": {
        "type": "string",
        "description": "Evaluation instant as an ISO 8601 UTC string, e.g. \"2024-08-12T05:00:00Z\". Defaults to now. A single instant, not a window. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "latitude": {
        "type": "number",
        "maximum": 90,
        "minimum": -90,
        "description": "Observer latitude in decimal degrees, north positive."
      },
      "timezone": {
        "type": "string",
        "description": "IANA timezone for localized output, e.g. \"America/Los_Angeles\". When omitted, output is UTC-only."
      },
      "elevation": {
        "type": "number",
        "default": 0,
        "description": "Observer elevation in meters above sea level. Default 0."
      },
      "longitude": {
        "type": "number",
        "maximum": 180,
        "minimum": -180,
        "description": "Observer longitude in decimal degrees, east positive."
      },
      "min_altitude": {
        "type": "number",
        "default": 0,
        "maximum": 90,
        "minimum": -90,
        "description": "Minimum altitude in degrees to include a body. Default 0 (above the horizon); use e.g. 5 to require clearance."
      },
      "include_stars": {
        "type": "boolean",
        "default": false,
        "description": "Include the bundled bright stars alongside planets. Default false."
      }
    },
    "additionalProperties": false
  }

  arguments 48 lines copy
• astronomy_get_rise_set reads unknown never probed

  Compute rise, set, and culmination (transit) times for a body at an observer location, plus the maximum altitude at culmination. For the Sun, also returns the three twilight pairs (civil −6°, nautical −12°, astronomical −18°) so a single call answers "when does the sun set and when is it truly dark." Each pair covers the night after the cycle's set — dusk that evening, dawn the next morning — so the dawn listed beside a sunrise is the following day's; for the dawn before a sunrise, read the previous cycle or start a day earlier. Searches forward from `start` (default today) and returns the next `count` cycles (default 1). When the body is already above the horizon at `start`, the first cycle is the interval in progress: its `set` is the imminent one and its `rise` is null, since that rise precedes the search — so a set is never reported earlier than the rise beside it. Circumpolar or never-rises situations are reported as null rise/set fields with an explanatory note rather than an error — the fact is the answer. Default elevation is 0 m; pass an IANA `timezone` for observer-local times. This server does not geocode — resolve coordinates upstream first.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "body",
      "latitude",
      "longitude"
    ],
    "properties": {
      "body": {
        "enum": [
          "sun",
          "moon",
          "mercury",
          "venus",
          "mars",
          "jupiter",
          "saturn",
          "uranus",
          "neptune",
          "pluto"
        ],
        "type": "string",
        "description": "The body to compute rise/set for. Twilight is included only when this is \"sun\"."
      },
      "count": {
        "type": "integer",
        "default": 1,
        "maximum": 31,
        "minimum": 1,
        "description": "Number of forward rise/set cycles to return. Default 1, max 31."
      },
      "start": {
        "type": "string",
        "description": "Search start as an ISO 8601 UTC string, e.g. \"2024-06-21T00:00:00Z\". Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process."
      },
      "latitude": {
        "type": "number",
        "maximum": 90,
        "minimum": -90,
        "description": "Observer latitude in decimal degrees, north positive."
      },
      "timezone": {
        "type": "string",
        "description": "IANA timezone for localized output, e.g. \"America/Los_Angeles\". When omitted, output is UTC-only."
      },
      "elevation": {
        "type": "number",
        "default": 0,
        "description": "Observer elevation in meters above sea level. Default 0."
      },
      "longitude": {
        "type": "number",
        "maximum": 180,
        "minimum": -180,
        "description": "Observer longitude in decimal degrees, east positive."
      }
    },
    "additionalProperties": false
  }

  arguments 60 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• brapi.caseyjhand.com brapi-mcp-server mcp · 22 tools
• usaspending.caseyjhand.com usaspending-mcp-server mcp · 18 tools
• onebusaway.caseyjhand.com onebusaway-mcp-server mcp · 16 tools
• secedgar.caseyjhand.com secedgar-mcp-server mcp · 16 tools
• courtlistener.caseyjhand.com courtlistener-mcp-server mcp · 14 tools
• openfda.caseyjhand.com openfda-mcp-server mcp · 14 tools
• gbif-biodiversity.caseyjhand.com gbif-biodiversity-mcp-server mcp · 13 tools
• openfec.caseyjhand.com openfec-mcp-server mcp · 12 tools

101 more sit on this domain. All of them.