io.github.cyanheads/astronomy-mcp-server
NPM · @CYANHEADS/ASTRONOMY-MCP-SERVER · SCANNED AUG 6
Offline observational astronomy: positions, rise/set, moon phases, eclipses, and seasons.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 127 of 134 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 127 of 134 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2463 tokens (~164/item across 15 items; 5 tools + 10 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @cyanheads/astronomy-mcp-server
claude mcp add cyanheads-astronomy-mcp-server -- npx -y @cyanheads/astronomy-mcp-server
codex mcp add cyanheads-astronomy-mcp-server -- npx -y @cyanheads/astronomy-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-astronomy-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@cyanheads/astronomy-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add cyanheads-astronomy-mcp-server --command npx --arg -y --arg @cyanheads/astronomy-mcp-server
mcp_servers:
cyanheads-astronomy-mcp-server:
command: "npx"
args: ["-y", "@cyanheads/astronomy-mcp-server"] {
"mcpServers": {
"cyanheads-astronomy-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/astronomy-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Aug 26 +32
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- 5 Aug 26 +1
- CVE-2026-69207 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 4 Aug 26 −1
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Licence: Apache-2.0 functional
- 1 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Package version: 0.1.3 → 0.2.3 functional
- 27 Jul 26 24
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Aug 2026 · Analysed npm/@cyanheads/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 127 packages
| Packages resolved | 127 |
|---|---|
| Deprecated | 125 |
| Stale | 40 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
astronomy_find_events astronomy-mcp-server: find sky events ~472
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. Only solar_eclipse takes an observer: pass latitude and longitude to get local circumstances (contact times plus `local_visible`). Every other class is geocentric and needs no location — a lunar eclipse is the same event everywhere the Moon is up, so it returns contact times and no `local_visible`. 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). Start defaults to now; pass an IANA `timezone` for observer-local timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | 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 | integer | — | Number of forward occurrences to return. Default 1, max 20. |
| elevation | number | — | Observer elevation in meters above sea level. Default 0. |
| event | string | yes | Which class of event to search for. |
| latitude | number | — | Observer latitude in decimal degrees — required for solar_eclipse to get local circumstances, ignored by every other event. |
| longitude | number | — | Observer longitude in decimal degrees — required for solar_eclipse, ignored by every other event. |
| start | string | — | Search start as an ISO 8601 UTC string, e.g. "2024-01-01T00:00:00Z". Defaults to now. |
| timezone | string | — | IANA timezone for localized output, e.g. "America/Los_Angeles". When omitted, output is UTC-only. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | The next occurrences of the requested event class, in chronological order. |
| totalCount | number | yes | Number of event occurrences returned. |
No examples provided.
astronomy_get_moon_phase astronomy-mcp-server: get moon phase ~187
Report the Moon phase for an instant: illuminated fraction, phase name, synodic age in days since the new moon, phase angle, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| time | string | — | Instant to evaluate as an ISO 8601 UTC string, e.g. "2024-12-15T00:00:00Z". Defaults to now. |
| timezone | string | — | IANA timezone for localized output, e.g. "America/Los_Angeles". When omitted, output is UTC-only. |
| Name | Type | Req | Description |
|---|---|---|---|
| age_days | number | yes | Synodic age in days since the previous new moon. |
| illuminated_fraction | number | yes | Fraction of the lunar disc illuminated, 0 to 1. |
| next_quarters | array | yes | The next four lunar quarter phases (new/first/full/last) in chronological order. |
| phase_angle_degrees | number | yes | Moon phase angle in degrees: 0 = new, 90 = first quarter, 180 = full, 270 = last quarter. |
| phase_name | string | yes | Human-readable phase name (New Moon, Waxing Crescent, First Quarter, …, Waning Crescent). |
| time_local | string | — | The same instant in the observer-local timezone with offset, present only when a timezone was supplied. |
| time_utc | string | yes | The instant the phase was computed for, in ISO 8601 UTC. |
No examples provided.
astronomy_get_rise_set astronomy-mcp-server: get rise/set times ~329
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." Searches forward from `start` (default today) and returns the next `count` cycles (default 1). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The body to compute rise/set for. Twilight is included only when this is "sun". |
| count | integer | — | Number of forward rise/set cycles to return. Default 1, max 31. |
| elevation | number | — | Observer elevation in meters above sea level. Default 0. |
| latitude | number | yes | Observer latitude in decimal degrees, north positive. |
| longitude | number | yes | Observer longitude in decimal degrees, east positive. |
| start | string | — | Search start as an ISO 8601 UTC string, e.g. "2024-06-21T00:00:00Z". Defaults to now. |
| timezone | string | — | IANA timezone for localized output, e.g. "America/Los_Angeles". When omitted, output is UTC-only. |
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The body these rise/set cycles are for, echoed from the request. |
| events | array | yes | One entry per rise/set/transit cycle, searching forward from the start time. |
| totalCount | number | yes | Number of rise/set cycles returned. |
No examples provided.
astronomy_get_sky_position astronomy-mcp-server: get sky position ~378
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, and the constellation it falls in. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | Solar-system body to locate. Omit when targeting a named star via `star`. |
| elevation | number | — | Observer elevation in meters above sea level. Default 0. |
| latitude | number | yes | Observer latitude in decimal degrees, north positive. |
| longitude | number | yes | Observer longitude in decimal degrees, east positive. |
| star | string | — | Named bright star to locate (common name or Bayer designation, e.g. "Sirius", "Alpha Centauri"). Takes precedence over `body`. |
| time | string | — | Instant of observation as an ISO 8601 UTC string, e.g. "2024-04-08T18:00:00Z". Defaults to now. |
| timezone | string | — | IANA timezone for localized output, e.g. "America/Los_Angeles". When omitted, output is UTC-only. |
| Name | Type | Req | Description |
|---|---|---|---|
| angular_diameter_arcsec | — | yes | Apparent angular diameter of the disc in arcseconds. Null for point-source convention bodies. |
| body | string | yes | The body or star this position is for, echoed from the request. |
| constellation | object | yes | The constellation the body currently falls within. |
| ecliptic | object | yes | Ecliptic-of-date coordinates of the body. |
| equatorial | object | yes | Apparent equatorial coordinates, corrected for precession, nutation, parallax, and aberration. |
| horizontal | object | yes | Refraction-corrected horizontal coordinates as seen from the observer. |
| illuminated_fraction | — | yes | Fraction of the disc illuminated, 0 to 1. Null when not applicable. |
| magnitude | — | yes | Apparent visual magnitude (lower is brighter). Null for bodies where the engine cannot compute it. |
| phase_angle_degrees | — | yes | Sun-body-observer phase angle in degrees. Null when not applicable (e.g. stars). |
| time_local | string | — | The same instant in the observer-local timezone with offset, present only when a timezone was supplied. |
| time_utc | string | yes | The instant of the observation in ISO 8601 UTC. |
No examples provided.
astronomy_list_visible astronomy-mcp-server: list visible bodies ~365
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. The whole sky is gated by the Sun's altitude into daylight / civil / nautical / astronomical twilight / dark, returned alongside the list. `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.
| Name | Type | Req | Description |
|---|---|---|---|
| elevation | number | — | Observer elevation in meters above sea level. Default 0. |
| include_stars | boolean | — | Include the bundled bright stars alongside planets. Default false. |
| latitude | number | yes | Observer latitude in decimal degrees, north positive. |
| longitude | number | yes | Observer longitude in decimal degrees, east positive. |
| min_altitude | number | — | Minimum altitude in degrees to include a body. Default 0 (above the horizon); use e.g. 5 to require clearance. |
| time | string | — | Evaluation instant as an ISO 8601 UTC string, e.g. "2024-08-12T05:00:00Z". Defaults to now. A single instant, not a window. |
| timezone | string | — | IANA timezone for localized output, e.g. "America/Los_Angeles". When omitted, output is UTC-only. |
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | yes | Every body (and optional star) above the minimum-altitude filter, ranked brightest-and-highest first. |
| sky_condition | string | yes | Sky condition derived from the Sun's altitude — the gate for whether faint objects are observable. |
| sun_altitude_degrees | number | yes | The Sun's altitude in degrees that produced the sky condition. |
| total_count | number | yes | Number of bodies returned above the minimum-altitude filter. |
No examples provided.