Astronomy Mcp Server

io.github.cyanheads由 GitHub 账号 cyanheads 发布v0.5.1更新于 Nov 16, 2026

Offline observational astronomy: positions, rise/set, moon phases, eclipses, and seasons.

已验证Streamable HTTP可网页运行位置与生活数据与分析

概览

AI 生成的概览

离线计算观测天文学数据:任意地点与时间的天空位置、升落与暮光时刻、月相、食、季节,以及此刻可见的天体。

可以做什么
  • 计算行星、月球、太阳与亮星的视位置,给出赤道、地平与黄道坐标。
  • 查询升、落与中天时刻,以及太阳的民用、航海与天文暮光。
  • 报告月相、被照亮比例与接下来四次四分相时刻。
  • 向前搜索日食、月食、二分二至、冲、合、大距、近远地点与流星雨极大。
  • 列出此刻地平线以上的天体并排序,附天空条件说明。
  • 可选获取 JPL Horizons 小天体或航天器星历,并预测可见卫星过境。
适用场景
适合让助手回答观测类问题:某行星何时升起、今晚月光是否干扰、下一次食何时发生、在给定经纬度此刻能看到什么,而无需调用在线天文服务。
运行要求
可作为公共远程端点使用,也可通过 npx、Bun 或 Docker 本地运行(Bun 1.4.4 以上或 Node.js 24 以上)。无需 API 密钥。核心功能离线运行;Horizons 与卫星工具默认关闭,需用 ASTRONOMY_ENABLE_HORIZONS 或 ASTRONOMY_ENABLE_SATELLITES 启用。它不做地理编码,需自行提供坐标与 IANA 时区。
安装前请注意
两个可选扩展会向 JPL Horizons 与 CelesTrak 发起外部请求,启用后会把目标编号与卫星查询发送给这些第三方。约 1900–2100 年之外的时间会报超出范围。结果为计算值,适合规划,不能替代经核实的历书。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Astronomy Mcp Server,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.cyanheads%2Fastronomy-mcp-server/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "astronomy": {
      "type": "http",
      "url": "https://astronomy.caseyjhand.com/mcp"
    }
  }
}

README

@cyanheads/astronomy-mcp-server

What's in the sky, computed offline — planet and moon positions, rise/set, phases, eclipses, and seasons for any place and time via MCP. STDIO or Streamable HTTP.

7 Tools • 1 Resource • 1 Prompt • 1 Skill

Public Hosted Server: https://astronomy.caseyjhand.com/mcp


Overview

Observational astronomy for any place and time: sky positions, rise/set and twilight times, moon phases, and the next eclipse, equinox, opposition, or conjunction — or just ask what's visible right now. Computed locally by astronomy-engine, with optional JPL Horizons ephemerides and satellite passes.

Tools

ToolDescription
astronomy_get_sky_positionApparent position of one body or named star: RA/Dec, alt/az, ecliptic, magnitude, phase, Sun elongation, constellation
astronomy_get_rise_setRise, set, and transit times for a body or named star, plus civil, nautical, and astronomical twilight for the Sun
astronomy_get_moon_phaseIlluminated fraction, phase name, synodic age, and the next four quarter phases
astronomy_find_eventsNext eclipses, equinoxes, solstices, moon quarters, oppositions, conjunctions, greatest elongations, apsides, or meteor-shower maxima
astronomy_list_visibleWhat's up now: naked-eye bodies (and optional bright stars) above the horizon, ranked, with a sky-condition gate
astronomy_get_ephemerisSmall-body or spacecraft ephemeris from JPL Horizons (opt-in)
astronomy_get_satellite_passesVisible satellite passes from a CelesTrak element set propagated with SGP4 (opt-in)

Resources

ResourceDescription
astronomy://body/{body}Reference card for a solar-system body: name, type, mean radius, naked-eye visibility

Tool-only clients get the same type, radius, and naked-eye fields inline from astronomy_get_sky_position.

Prompts

PromptDescription
astronomy_stargazing_planPlan a night of stargazing from a place, chaining the astronomy tools with geocoding and weather steps

Skills

SkillDescription
astronomy-guideChaining the tools for observing questions: anchoring dates to the observer's local night, what "visible" means per tool, Moon interference, eclipses from a place, and the opt-in Horizons and satellite tools

Plugin installs load it from skills/; MCP clients that support the Skills extension read it as skill://astronomy-guide/SKILL.md.

Design reference: docs/design.md.

Capability reference

astronomy_get_sky_position tool

  • body (sun, moon, mercury … pluto) or star is required, with star winning when both are set; star resolves against a bundled 32-star catalog by common name or Bayer designation (Sirius, α CMa), and a miss fails as star_not_found listing the catalog
  • Returns equatorial, refraction-corrected horizontal, and ecliptic coordinates plus magnitude, angular_diameter_arcsec, phase_angle_degrees, illuminated_fraction, sun_elongation_degrees, and constellation
  • Solar-system bodies also carry body_metadata, the resource card's type, mean_radius_km, and naked_eye; a star has none

astronomy_get_rise_set tool

  • One body or star searched forward from start (default now) for the next count cycles, default 1; 31 are served per call, and a count up to 366 returns the first 31 with a notice naming the start and count that continue the series
  • star takes the same catalog names as astronomy_get_sky_position and wins over body; body echoes the catalog name (Sirius for α CMa), a miss fails as star_not_found, and a star gets no twilight
  • Each cycle carries rise_utc, set_utc, transit_utc, and transit_altitude_degrees; a circumpolar or never-rising body or star gets null rise/set and a note instead of an error
  • For body: "sun", twilight holds civil, nautical, and astronomical dusk/dawn pairs for the night after each cycle's day. When the first day begins after start, night_in_progress holds the preceding night, including polar nights without a sunset; the first cycle otherwise carries its own night. Each pair stays within that night, and times before start remain included

astronomy_get_moon_phase tool

  • Geocentric: takes only time (default now) and an optional timezone
  • Returns illuminated_fraction, phase_name, age_days, next_quarters, and phase_longitude_degrees (0 new, 180 full), which is not the phase_angle_degrees of astronomy_get_sky_position

astronomy_find_events tool

  • One event (solar_eclipse, lunar_eclipse, equinox, solstice, moon_quarter, opposition, conjunction, max_elongation, perigee_apogee, meteor_shower) and the next count occurrences, default 1; 20 are served per call, and a count up to 200 returns the first 20 with a notice naming the start and count that continue the series; searches stop at the end of 2100
  • Body-relative events require body (body_required); a body the event doesn't apply to fails as body_not_supported, and conjunction with body2 takes the Moon or a planet different from body (invalid_body_pair otherwise) and reports separation_degrees
  • Eclipses and meteor showers take an optional observer (latitude and longitude together, else incomplete_observer); for eclipses it adds local_visible and contact_altitudes_degrees
  • With a timezone, each eclipse also carries contacts_local: the contacts phases keyed <phase>_local, each with the zone offset in force at that contact's own instant, and null where contacts is null
  • meteor_shower returns the maxima of nine major annual showers (Quadrantids, April Lyrids, η-Aquariids, Southern δ-Aquariids, Perseids, Orionids, Leonids, Geminids, Ursids) with zhr, the J2000 radiant, activity dates, and the Moon's geocentric moon_illuminated_fraction; an observer adds radiant_altitude_degrees and sun_altitude_degrees at the maximum. shower narrows the search to one by IMO code or name, and a miss fails as shower_not_found. Maxima are the calendar's nominal ones, with no outburst predictions
  • Eclipses and meteor showers are included when their peak is at or after start; eclipse contacts and shower activity dates may precede start
  • Meteor shower table: International Meteor Organization, 2026 Meteor Shower Calendar, ed. Jürgen Rendtel, DOI 10.13140/RG.2.2.36179.08480

astronomy_list_visible tool

  • Observer coordinates and one evaluation instant, time (default now, not a window); min_altitude (default 0) and include_stars (default false) shape the list
  • Returns sky_condition (daylight, civil_twilight, nautical_twilight, astronomical_twilight, dark), sun_altitude_degrees, and bodies ranked brightest-and-highest first, each with a visibility_note that says when daylight, civil twilight, or Sun glare within 15° hides or dims it

astronomy_get_ephemeris tool

  • designation is passed to Horizons verbatim ("433;" for a numbered asteroid, "DES=1P;CAP" for a periodic comet, a negative SPK-ID for a spacecraft); start defaults to now, stop to 24 h later, and step to "1h" (a count plus m, h, d, mo, or y); latitude and longitude together add alt/az
  • Each row carries ra_hours/dec_degrees as astrometric ICRF (J2000), not the apparent of-date values astronomy_get_sky_position returns, plus distance_au, magnitude, constellation, sun_elongation_degrees, and visibility (morning, evening, or null); with an observer, the elongation is measured from that place
  • Up to 200 rows per call; when truncated is true the notice names the start to resume from. target_name is the object Horizons resolved
  • Fails as ambiguous_designation, observer_is_target, body_not_found, invalid_step, invalid_elevation, time_out_of_range, or request_rejected, each naming the input to correct
  • Registered only when ASTRONOMY_ENABLE_HORIZONS=true

astronomy_get_satellite_passes tool

  • Exactly one of norad_id or name (ISS, Hubble/HST, and Tiangong/CSS resolve directly; other names are matched against CelesTrak, and an ambiguous one fails as ambiguous_satellite_name listing candidates); start must be within about a month of today, and days defaults to 7
  • 10 days are searched per call; a days up to 30 returns the first 10 with a notice naming the start and days that continue the search
  • Returns norad_id, satellite_name, and passes that are visible (sunlit, above 10° elevation, Sun below −6°), each with rise/peak/set times and azimuths, peak_altitude_degrees, duration_seconds, sunlit, and visible_start_utc/visible_end_utc
  • Registered only when ASTRONOMY_ENABLE_SATELLITES=true

astronomy://body/{body} resource

  • {body} is one of sun, moon, mercury … pluto, with name completion; anything else fails as unknown_body
  • application/json card with body, name, type (star/planet/moon/dwarf), mean_radius_km, and naked_eye

astronomy_stargazing_plan prompt

  • Arguments: location required; date (YYYY-MM-DD) optional, defaults to tonight
  • Returns one user message that chains astronomy_get_rise_set (sun, then moon), astronomy_get_moon_phase, astronomy_list_visible with include_stars, and astronomy_find_events for meteor_shower (searched from four weeks before the night, keeping the showers active that night), plus the geocoding and weather steps this server doesn't cover

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

Astronomy-specific:

  • Keyless, offline, deterministic core: the five core tools need no network, API key, or rate limit, and return the same answer for the same body, time, and observer
  • Times outside the engine's high-accuracy span (≈1900–2100) fail as time_out_of_range; the Horizons tool is bounded by each target's own data span instead
  • Times are ISO 8601 UTC, and a value with no zone is read as UTC; pass an IANA timezone (or set ASTRONOMY_DEFAULT_TIMEZONE) to get *_local fields alongside UTC. The server never infers a timezone from coordinates
  • No geocoding: resolve a place name to latitude/longitude and a timezone upstream, then pass the coordinates (elevation defaults to 0 m)
  • The two opt-in extensions each carry their own timeout and retry; an upstream failure surfaces as horizons_unavailable or celestrak_unavailable and never falls back to core output

Agent-friendly output:

  • Uncertainty preserved: magnitude, angular_diameter_arcsec, phase_angle_degrees, and illuminated_fraction are null where the engine can't compute them, rendered as "unavailable", never zeroed
  • Deterministic visibility notes: visibility_note comes from real magnitude, altitude, sky condition, and Sun elongation, not a synthetic score
  • Typed error contracts: each declared failure carries a typed reason and a recovery hint, so callers can correct and retry
  • Exact values behind rounded text: format() pairs each rounded figure with its exact value in brackets (RA 4.4116 h [4.411597993526305]), so a content[]-only client loses no precision

Getting started

Public Hosted Instance

A public instance is available at https://astronomy.caseyjhand.com/mcp — no installation required. It serves Streamable HTTP; each client takes its own config shape.

For Claude Code:

sh
claude mcp add --transport http astronomy-mcp-server https://astronomy.caseyjhand.com/mcp

For Cline (cline_mcp_settings.json):

json
{  "mcpServers": {    "astronomy-mcp-server": {      "type": "streamableHttp",      "url": "https://astronomy.caseyjhand.com/mcp"    }  }}

For Cursor (mcp.json):

json
{  "mcpServers": {    "astronomy-mcp-server": {      "url": "https://astronomy.caseyjhand.com/mcp"    }  }}

Claude Desktop adds remote servers under Settings → Connectors.

Self-Hosted / Local

Add the following to your MCP client configuration file. The core tools need no configuration; set ASTRONOMY_ENABLE_HORIZONS and/or ASTRONOMY_ENABLE_SATELLITES to true to register the extensions.

json
{  "mcpServers": {    "astronomy-mcp-server": {      "type": "stdio",      "command": "bunx",      "args": ["@cyanheads/astronomy-mcp-server@latest"],      "env": {        "MCP_TRANSPORT_TYPE": "stdio",        "MCP_LOG_LEVEL": "info"      }    }  }}

Or with npx (no Bun required):

json
{  "mcpServers": {    "astronomy-mcp-server": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@cyanheads/astronomy-mcp-server@latest"],      "env": {        "MCP_TRANSPORT_TYPE": "stdio",        "MCP_LOG_LEVEL": "info"      }    }  }}

Or with Docker:

json
{  "mcpServers": {    "astronomy-mcp-server": {      "type": "stdio",      "command": "docker",      "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/astronomy-mcp-server:latest"]    }  }}

For Streamable HTTP, set the transport and start the server:

sh
MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http# Server listens at http://localhost:3010/mcp

Prerequisites

  • Bun v1.4.4 or higher (or Node.js v24+).
  • No API key. The core is offline, and both extensions (JPL Horizons, CelesTrak) are keyless.

Installation

  1. Clone the repository:
sh
git clone https://github.com/cyanheads/astronomy-mcp-server.git
  1. Navigate into the directory:
sh
cd astronomy-mcp-server
  1. Install dependencies:
sh
bun install
  1. Configure environment (optional):
sh
cp .env.example .env# edit .env only to enable the extensions or override a default

Configuration

Every variable is optional; the core runs with none set.

VariableDescriptionDefault
ASTRONOMY_ENABLE_HORIZONSRegister astronomy_get_ephemeris (JPL Horizons).false
ASTRONOMY_ENABLE_SATELLITESRegister astronomy_get_satellite_passes (CelesTrak + SGP4).false
ASTRONOMY_DEFAULT_TIMEZONEFallback IANA timezone when a call omits timezone. Unset means UTC-only output.none
ASTRONOMY_REQUEST_TIMEOUT_MSHTTP timeout for Horizons and CelesTrak requests, in ms.15000
ASTRONOMY_TLE_CACHE_TTL_MSIn-process element-set cache TTL, in ms. The 2 h default follows CelesTrak's refetch guidance.7200000
ASTRONOMY_HORIZONS_BASE_URLJPL Horizons API endpoint.https://ssd.jpl.nasa.gov/api/horizons.api
ASTRONOMY_CELESTRAK_BASE_URLCelesTrak GP endpoint.https://celestrak.org/NORAD/elements/gp.php
MCP_TRANSPORT_TYPETransport: stdio or http.stdio
MCP_HTTP_PORTHTTP server port.3010
MCP_SESSION_MODEHTTP session mode: stateless, stateful, or auto.stateless
MCP_AUTH_MODEAuthentication: none, jwt, or oauth.none
MCP_LOG_LEVELLog level (debug, info, warning, error, etc.).info
OTEL_ENABLEDEnable OpenTelemetry.false

See .env.example for the full list of optional overrides.

Running the server

Local development

  • Build and run:

    sh
    # One-time buildbun run rebuild
    # Run the built serverbun run start:stdio# orbun run start:http
  • Run checks and tests:

    sh
    bun run devcheck   # Lint, format, typecheck, securitybun run test       # Vitest test suitebun run lint:mcp   # Validate MCP definitions against spec

Docker

sh
docker build -t astronomy-mcp-server .docker run --rm -p 3010:3010 astronomy-mcp-server

The Dockerfile defaults to HTTP transport, stateless session mode, and logs to /var/log/astronomy-mcp-server. OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.

Project structure

DirectoryPurpose
src/index.tscreateApp() entry point — registers tools/resources/prompts and inits services.
src/configServer-specific environment variable parsing and validation with Zod.
src/mcp-server/toolsTool definitions (*.tool.ts). Five core tools plus two opt-in extensions.
src/mcp-server/resourcesResource definitions (*.resource.ts). Body reference card.
src/mcp-server/promptsPrompt definitions (*.prompt.ts). Stargazing plan.
src/services/ephemerisOffline compute core — astronomy-engine wrapper, body table, bright-star catalog.
src/services/horizonsJPL Horizons HTTP client (extension).
src/services/satelliteCelesTrak element-set fetch and SGP4 propagation (extension).
tests/Unit and integration tests mirroring src/.

Development guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

  • Handlers throw, framework catches — no try/catch in tool logic
  • Use ctx.log for request-scoped logging, ctx.state for tenant-scoped storage
  • Register new tools and resources in the createApp() arrays in src/index.ts
  • Normalize raw engine/API values to the domain type; preserve uncertainty as null and never fabricate missing fields

Contributing

Issues are welcome. Run checks and tests before submitting:

sh
bun run devcheckbun run test

License

Apache-2.0 — see LICENSE for details.

来源:README.md,提交 ab5a404

工具

7

astronomy_get_sky_position

astronomy-mcp-server: get sky position

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.

输入参数bodystartimelatitude必填timezoneelevationlongitude必填

astronomy_get_rise_set

astronomy-mcp-server: get rise/set times

Compute rise, set, and culmination (transit) times and maximum transit altitude for a solar-system body or a named bright star at an observer location. Searches forward from `start` (default now) for `count` daily cycles (default 1), including days without crossings. For the Sun, each cycle carries civil −6°, nautical −12°, and astronomical −18° twilight: dusk after its set or culmination, then dawn before the next day begins. A crossing absent from that night is null. When the Sun is down and the first cycle's day begins after `start`, `night_in_progress` carries the preceding night, including polar nights without a sunset and times before `start` that have passed. A first cycle beginning after the culmination of a dark day instead carries that night itself, with rise, set, and transit null. When a body is already up, the partial first cycle has null rise and the imminent set; no set precedes its own rise. Circumpolar and never-rises cycles have null crossings and explanatory notes. At most 31 cycles are served per call; a count up to 366 returns the first 31 with a notice naming the exact `start` and `count` for the rest, or saying no continuation exists past 2100. A continuation may repeat the preceding night in `night_in_progress`, while cycles continue without overlap. Supply `star` (e.g. Sirius, Polaris) instead of `body` to target a catalog star; `body` is ignored when `star` is set. Default elevation is 0 m; pass an IANA `timezone` for local output. Resolve coordinates upstream; this server does not geocode.

输入参数bodystarcountstartlatitude必填timezoneelevationlongitude必填

astronomy_get_moon_phase

astronomy-mcp-server: get moon phase

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.

输入参数timetimezone

astronomy_find_events

astronomy-mcp-server: find sky events

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, perigee_apogee, or meteor_shower. Both eclipse classes and meteor_shower 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. meteor_shower returns the maxima of nine major annual showers from a table bundled from the IMO Meteor Shower Calendar — ZHR, J2000 radiant, activity dates, and the Moon's geocentric illuminated fraction at each; an observer adds the radiant's and the Sun's altitude at the maximum, which can fall in daylight. The maxima are the calendar's nominal ones, with no outburst predictions. `shower` narrows the search to one shower by IMO code or name. A shower counts when its maximum is at or after start, so one past its maximum but still active needs an earlier start. 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). conjunction with `body` alone is that planet's conjunction with the Sun. Add `body2` for a conjunction of two bodies — the Moon or a planet with another: the instant they share one ecliptic longitude seen from Earth's center, with their `se

输入参数bodybody2countevent必填startshowerlatitudetimezoneelevationlongitude

astronomy_list_visible

astronomy-mcp-server: list visible bodies

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.

输入参数timelatitude必填timezoneelevationlongitude必填min_altitudeinclude_stars

astronomy_get_ephemeris

astronomy-mcp-server: get small-body ephemeris

Fetch a time-series ephemeris for a small body (asteroid or comet) or spacecraft from JPL Horizons — RA/Dec, distance, apparent magnitude, the constellation, and the angle from the Sun with its morning or evening side over a span, optionally with observer-relative altitude/azimuth. RA/Dec are astrometric ICRF (J2000), the frame of modern star charts, so they differ from the apparent of-date values astronomy_get_sky_position returns by precession, nutation, and aberration — a gap that grows with distance from the year 2000. 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. A major-body name matching several bodies (e.g. "Mars") is rejected with the ID number of each body it matched — pass one, such as "499" for the planet. `start` and `stop` are ISO 8601 UTC dates in the Gregorian calendar, extended before 1582, in years 0100 through 9999; `stop` must not be before `start`, and a `stop` equal to `start` returns the single row at that instant. `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

输入参数stepstopstartlatitudeelevationlongitudedesignation必填

astronomy_get_satellite_passes

astronomy-mcp-server: get satellite passes

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, plus the stretch of the pass visible to the naked eye: `visible_start_utc` through `visible_end_utc`, with the elevation and azimuth at each end. A pass is returned when that visible stretch — the satellite above the horizon and sunlit while the Sun is below −6° for the observer — reaches 10° elevation, wherever in the pass it falls. `sunlit` reports illumination at the peak instant, so it is false on a pass seen only before it enters Earth's shadow or after it leaves. Rise, set, and the visible-stretch edges are within 1 s of the true instants; the peak is the highest sample of a 30-second scan. Every returned pass rises in the requested window or in the 30 s before `start`: a pass up longer than that 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. Searches at most 10 days per call: a larger `days`, up to 30, searches the first 10 and returns a notice naming the exact `start` and `days` that continue the searc

输入参数daysnamestartlatitude必填norad_idtimezoneelevationlongitude必填

版本历史

8
  1. v0.5.1最新Nov 16, 2026
  2. v0.5.0Oct 29, 2026
  3. v0.4.3Oct 25, 2026
  4. v0.4.2Oct 15, 2026
  5. v0.4.1Oct 8, 2026
  6. v0.4.0Sep 24, 2026
  7. v0.2.10Sep 19, 2026
  8. v0.2.9Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分