# Usno Astronomy (npm · @pipeworx/mcp-usno-astronomy)

Next solar eclipse, eclipse times by place, Moon phases and seasons from the US Naval Observatory.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-usno-astronomy/usno-astronomy-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-usno-astronomy/usno-astronomy-mcp)
- npm · `@pipeworx/mcp-usno-astronomy`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-usno-astronomy/pipeworx-mcp-usno-astronomy.md), [page](https://verifymcp.io/servers/pipeworx-io-usno-astronomy/pipeworx-mcp-usno-astronomy)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-usno-astronomy`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-usno-astronomy).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 830 tokens (~207/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Usno Astronomy MCP server?

Usno Astronomy runs locally as an npm package, launched with npx -y @pipeworx/mcp-usno-astronomy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-usno-astronomy -- npx -y @pipeworx/mcp-usno-astronomy
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-usno-astronomy": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usno-astronomy"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-usno-astronomy": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usno-astronomy"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-usno-astronomy -- npx -y @pipeworx/mcp-usno-astronomy
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-usno-astronomy": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-usno-astronomy"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-usno-astronomy --command npx --arg -y --arg @pipeworx/mcp-usno-astronomy
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-usno-astronomy:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-usno-astronomy"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-usno-astronomy": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-usno-astronomy"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-usno-astronomy -t stdio -c npx -a -y @pipeworx/mcp-usno-astronomy
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-usno-astronomy": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usno-astronomy"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `usno_solar_eclipses` (~173 tokens)

When is the next solar eclipse — the list of solar eclipses in a year from the US Naval Observatory, each with its date and type (total, annular, partial, hybrid). With no arguments it returns the NEXT solar eclipse after today plus the rest of the current and following year, so "when is the next solar eclipse", "solar eclipses in 2027", "is there a total eclipse this year" are all one call. For where an eclipse is visible and what time it starts at a given place, follow with usno_eclipse_circumstances. Lunar eclipses are not published by this API.

Input parameters:

- `year` (number): Four-digit year, 1800-2050. Omit for the next eclipse after today (current year and the next).

Output parameters:

- `eclipses` (array)
- `next_eclipse` (object)
- `source` (string)
- `time_note` (string)
- `years_covered` (array)

### `usno_eclipse_circumstances` (~275 tokens)

Local circumstances of a solar eclipse at a given latitude/longitude on a given date — whether the Sun is totally, annularly or partially eclipsed there, the magnitude and obscuration (percentage of the Sun covered), the duration, and the UT time, Sun altitude and azimuth of each contact (eclipse begins, totality begins/ends, maximum eclipse, eclipse ends, or sunrise/sunset if the eclipse is in progress then). Answers "what time does the August 12 2026 eclipse start in Madrid", "how much of the Sun will be covered in Denver", "will the eclipse be total where I am". Needs coordinates: resolve a place name to lat/lon first. Find the eclipse date with usno_solar_eclipses.

Input parameters:

- `date` (string, required): Date of the eclipse as YYYY-MM-DD, e.g. "2026-08-12". Must be a solar eclipse date from usno_solar_eclipses.
- `height` (number): Observer height in metres above sea level. Default 0.
- `lat` (number, required): Latitude in decimal degrees, north positive, e.g. 40.42 for Madrid.
- `lon` (number, required): Longitude in decimal degrees, east positive, e.g. -3.70 for Madrid.

Output parameters:

- `contacts` (array)
- `description` (string)
- `duration` (string)
- `event` (string)
- `found` (boolean)
- `magnitude` (number)
- `obscuration_pct` (number)
- `source` (string)
- `time_note` (string)

### `usno_moon_phases` (~196 tokens)

Moon phases from the US Naval Observatory: the UT date and time of every New Moon, First Quarter, Full Moon and Last Quarter in a year, or the next few phases from a given date. Answers "when is the next full moon", "full moons in 2026", "what phase is the Moon in this week", "date of the new moon in October". Pass a year for the whole year, or a start date (default today) with a count for the next phases.

Input parameters:

- `count` (number): How many phases to return from the start date, 1-99. Default 8 (about two lunar months).
- `date` (string): Start date YYYY-MM-DD for the next phases from that day. Default today when year is omitted.
- `year` (number): Four-digit year, 1800-2050, for every phase in that year (about 50).

Output parameters:

- `next_full_moon` (object)
- `next_new_moon` (object)
- `phases` (array)
- `returned` (number)
- `source` (string)
- `time_note` (string)

### `usno_seasons` (~128 tokens)

The seasons for a year from the US Naval Observatory: the UT date and time of the March and September equinoxes, the June and December solstices, and Earth's perihelion and aphelion. Answers "when is the summer solstice", "what date is the autumn equinox in 2027", "first day of spring", "when is Earth closest to the Sun". Northern-hemisphere season names are attached; the southern hemisphere is the opposite.

Input parameters:

- `year` (number): Four-digit year, 1800-2050. Default: current year.

Output parameters:

- `events` (array)
- `source` (string)
- `time_note` (string)
- `year` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-usno-astronomy/pipeworx-mcp-usno-astronomy#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Usno Astronomy MCP server?

Usno Astronomy is an MCP server listed in the public MCP registry as io.github.pipeworx-io/usno-astronomy. Next solar eclipse, eclipse times by place, Moon phases and seasons from the US Naval Observatory. This page covers its npm package (@pipeworx/mcp-usno-astronomy).

### Is the Usno Astronomy MCP server safe to use?

Usno Astronomy scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Usno Astronomy MCP server expose?

Usno Astronomy exposes 4 tools: usno_solar_eclipses, usno_eclipse_circumstances, usno_moon_phases, usno_seasons. Their descriptions and schemas cost roughly 772 tokens of context every time the server is loaded.

### Is the Usno Astronomy MCP server still maintained?

Usno Astronomy is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Usno Astronomy MCP server under?

Usno Astronomy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Usno Astronomy MCP server?

VerifyMCP ran 16 checks on Usno Astronomy, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-usno-astronomy
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-usno-astronomy
- Repository: https://github.com/pipeworx-io/mcp-usno-astronomy
- Website: https://pipeworx.io/packs/usno-astronomy
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-usno-astronomy/pipeworx-mcp-usno-astronomy.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-usno-astronomy/pipeworx-mcp-usno-astronomy/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-usno-astronomy/pipeworx-mcp-usno-astronomy.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-usno-astronomy/pipeworx-mcp-usno-astronomy