# io.github.davidmosiah/astral-mcp (npm · astral-mcp)

Precision-audited astrology MCP: natal charts, transits, synastry, moon phases. No API key.

- Trust score: 63/100 (medium)
- Change this week: +39
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `astral-mcp`: 63/100 (this document), [markdown](https://verifymcp.io/servers/davidmosiah-astral-mcp/astral-mcp.md), [page](https://verifymcp.io/servers/davidmosiah-astral-mcp/astral-mcp)

## Channel facts

- Registry: `npm`
- Package: `astral-mcp`
- 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-08-03.

- **Supply Chain Security**: 88/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (99 of 100), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (99 of 100), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2548 tokens (~254/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### Claude

```bash
claude mcp add davidmosiah-astral-mcp -- npx -y astral-mcp
```

### Codex

```bash
codex mcp add davidmosiah-astral-mcp -- npx -y astral-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "davidmosiah-astral-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "astral-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add davidmosiah-astral-mcp --command npx --arg -y --arg astral-mcp
```

### Hermes

```yaml
mcp_servers:
  davidmosiah-astral-mcp:
    command: "npx"
    args: ["-y", "astral-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "davidmosiah-astral-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "astral-mcp"
      ]
    }
  }
}
```

## 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-08-02 (score 63, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: MIT

### 2026-07-31 (score 18, −24)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 42, +18)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: unverified
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail

### 2026-07-27 (score 24)

First indexed and scored.

## MCP tools (10)

### `astral_compute_natal_chart` (~660 tokens)

Compute Natal Chart

Compute a full natal (birth) chart from birth data: planet signs/degrees/houses, retrogrades, major aspects with orb and strength, the Ascendant/MC, and a derived signature (dominant element/modality, chart pattern, stelliums, angular planets). By default the chart is precision-audited by a second independent ephemeris. This is the primary tool. If you only have a city name, call astral_search_birthplace first to get latitude/longitude/timezone. Use privacy_mode to control payload size (a full chart is large): 'full' (default) returns everything; 'structured' drops redundant fields; 'summary' returns only the luminaries, Ascendant, chart signature and top aspects to save tokens.

Input parameters:

- `birth_date` (string, required): Birth date as YYYY-MM-DD, e.g. 1989-02-23. Years before 1900 and after 2100 are supported but less precise.
- `birth_time` (string): Local birth time as 24h HH:MM, e.g. 14:30. Optional — if unknown, noon is assumed and house/ascendant accuracy drops (planets stay accurate).
- `house_system` (string): House system. 'placidus' is the modern default; 'whole-sign' is common in traditional/Hellenistic work; others: koch, campanus, regiomontanus, topocentric, equal-house.
- `latitude` (number, required): Birth latitude in decimal degrees, -90..90. Resolve from a city name with astral_search_birthplace if you don't have it.
- `longitude` (number, required): Birth longitude in decimal degrees, -180..180 (negative = West). Resolve with astral_search_birthplace if unknown.
- `privacy_mode` (string): Payload verbosity — how much of the chart to return, independent of response_format (which only picks markdown vs json). 'full' (default) returns the complete payload: every planet, house and aspect…
- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.
- `timezone` (string, required): IANA timezone of the BIRTHPLACE at birth, e.g. America/Fortaleza. Not the caller's timezone. astral_search_birthplace returns this for each match.
- `verify_precision` (boolean): When true (default), independently re-derives every planet with a second ephemeris and attaches a precision audit. Set false to skip the cross-check.
- `zodiac` (string): Zodiac. 'tropical' (Western, season-anchored) or 'sidereal' (Vedic/constellation-anchored).

Output parameters:

- `aspects` (array)
- `context`
- `houses` (object)
- `meta` (object)
- `planets` (object)
- `precision`

### `astral_current_transits` (~668 tokens)

Current Transits

Read the current (or a chosen date's) planetary transits against a natal chart. Returns the active transit aspects to the natal planets and angles, upcoming activation windows over the next days, and the current moon phase. Supply the same birth data you would for a natal chart; pass on_date/on_time to read a specific moment. Useful for 'what's happening for me astrologically' questions. Set privacy_mode=summary for just the moon phase and top transit aspects (omitting the full current-sky planet map), 'structured' for a leaner payload, or 'full' (default) for everything.

Input parameters:

- `birth_date` (string, required): Birth date as YYYY-MM-DD, e.g. 1989-02-23. Years before 1900 and after 2100 are supported but less precise.
- `birth_time` (string): Local birth time as 24h HH:MM, e.g. 14:30. Optional — if unknown, noon is assumed and house/ascendant accuracy drops (planets stay accurate).
- `house_system` (string): House system. 'placidus' is the modern default; 'whole-sign' is common in traditional/Hellenistic work; others: koch, campanus, regiomontanus, topocentric, equal-house.
- `include_angles` (boolean): Include transits to the Ascendant and Midheaven. Requires an accurate birth_time to be meaningful.
- `latitude` (number, required): Birth latitude in decimal degrees, -90..90. Resolve from a city name with astral_search_birthplace if you don't have it.
- `longitude` (number, required): Birth longitude in decimal degrees, -180..180 (negative = West). Resolve with astral_search_birthplace if unknown.
- `on_date` (string): Local date to read transits for as YYYY-MM-DD. Defaults to today.
- `on_time` (string): Local time of the transit reading as 24h HH:MM. Defaults to noon.
- `privacy_mode` (string): Payload verbosity — how much of the chart to return, independent of response_format (which only picks markdown vs json). 'full' (default) returns the complete payload: every planet, house and aspect…
- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.
- `timezone` (string, required): IANA timezone of the BIRTHPLACE at birth, e.g. America/Fortaleza. Not the caller's timezone. astral_search_birthplace returns this for each match.
- `zodiac` (string): Zodiac. 'tropical' (Western, season-anchored) or 'sidereal' (Vedic/constellation-anchored).

Output parameters:

- `abridged` (boolean)
- `currentPlanets` (object)
- `generatedAt` (string)
- `highlights` (array)
- `localDate` (string)
- `localTime` (string)
- `moon`
- `note` (string)
- `privacy_mode` (string)
- `timezone` (string)
- `upcoming` (array)

### `astral_synastry` (~396 tokens)

Synastry (Two-Chart Comparison)

Compare two birth charts (synastry). Returns the inter-chart aspects between the two people's planets and angles, plus scored dimensions (harmony, chemistry, communication, growth) and an overall 0–100 score with a tone. Provide both people's birth data under 'person' and 'partner'. Resolve any city names with astral_search_birthplace first. Set privacy_mode=summary for just the score, tone, dimensions and strongest aspects; 'full' (default) returns the complete aspect list.

Input parameters:

- `house_system` (string): House system. 'placidus' is the modern default; 'whole-sign' is common in traditional/Hellenistic work; others: koch, campanus, regiomontanus, topocentric, equal-house.
- `partner` (object, required): Second person's birth data.
- `person` (object, required): First person's birth data.
- `privacy_mode` (string): Payload verbosity — how much of the chart to return, independent of response_format (which only picks markdown vs json). 'full' (default) returns the complete payload: every planet, house and aspect…
- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.
- `zodiac` (string): Zodiac. 'tropical' (Western, season-anchored) or 'sidereal' (Vedic/constellation-anchored).

Output parameters:

- `abridged` (boolean)
- `aspects` (array)
- `dimensions`
- `note` (string)
- `privacy_mode` (string)
- `score` (number)
- `tone` (string)

### `astral_moon_phase` (~175 tokens)

Moon Phase

Get the moon phase (new, waxing, full, waning, etc.), the moon's sign, illumination percentage and sun–moon angle for now or a chosen local date/time. Location-independent — no birth data needed. Good for ritual timing, journaling prompts, or 'what phase is the moon in' questions.

Input parameters:

- `on_date` (string): Local date as YYYY-MM-DD. Defaults to today.
- `on_time` (string): Local time as 24h HH:MM. Defaults to noon.
- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.
- `timezone` (string): IANA timezone for interpreting on_date/on_time, e.g. America/New_York. Defaults to UTC.

Output parameters:

- `angle` (number)
- `generatedAt` (string)
- `illumination` (number)
- `moonSign` (string)
- `phase` (string)
- `timezone` (string)

### `astral_search_birthplace` (~186 tokens)

Search Birthplace

Geocode a city or place name into latitude, longitude and IANA timezone using OpenStreetMap (free, no key). Call this FIRST whenever you only have a place name, then pass the chosen match's coordinates and timezone to the chart tools. Returns several matches; pick the one whose displayName matches the intended birthplace.

Input parameters:

- `language` (string): Preferred language for returned place names (ISO code), e.g. en, pt, es.
- `query` (string, required): City or place name to geocode, e.g. 'Fortaleza, Brazil'. Minimum 3 characters. Call this first when you only have a place name, then pass the returned latitude/longitude/timezone to the chart tools.
- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Output parameters:

- `count` (integer)
- `query` (string)
- `results` (array)

### `astral_demo` (~91 tokens)

Astral Demo

Return a fully-worked example natal chart (Greenwich, noon, 2000-01-01) including a precision audit, so you can see the exact payload shape before sending real birth data. No input, no network, no auth.

Input parameters:

- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Output parameters:

- `chart`
- `input`
- `kind` (string)
- `note` (string)

### `astral_capabilities` (~99 tokens)

Astral Capabilities

Explain what astral-mcp can compute: supported house systems, zodiacs, bodies, aspects and features, the dual-engine precision model, what is NOT included (nodes, Chiron, interpretations), and the recommended agent workflow. Read this first to plan a sequence of calls.

Input parameters:

- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Output parameters:

- `creator` (object)
- `engines` (object)
- `links` (object)
- `mcp_name` (string)
- `not_included` (array)
- `project` (string)
- `recommended_agent_flow` (array)
- `supported` (object)

### `astral_data_inventory` (~85 tokens)

Astral Data Inventory

Inventory the data domains this server exposes (natal, transits, relationship, geocoding), which tools serve each, and the recommended first calls. Does not compute anything or take any input beyond response_format.

Input parameters:

- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Output parameters:

- `categories` (array)
- `data_access_model` (string)
- `first_tools` (array)
- `generated_at` (string)
- `kind` (string)
- `mcp_name` (string)
- `notes` (array)

### `astral_agent_manifest` (~93 tokens)

Astral Agent Manifest

Agent-oriented setup and usage guide: install command, recommended first calls, the full tool list, agent rules (resolve birthplace first, pass birthplace timezone, birth_time caveats) and troubleshooting. Call this to learn how to drive astral-mcp correctly.

Input parameters:

- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Output parameters:

- `agent_rules` (array)
- `data_access_model` (string)
- `links` (object)
- `mcp_name` (string)
- `package` (object)
- `project` (string)
- `recommended_first_calls` (array)
- `standard_tools` (array)
- `troubleshooting` (array)

### `astral_connection_status` (~95 tokens)

Astral Connection Status

Health check. The server is stateless and local, so this verifies the Node version and proves both bundled ephemerides load and agree by computing a sample chart and running the dual-engine precision audit. Call this to confirm the install is working before computing real charts.

Input parameters:

- `response_format` (string): Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Output parameters:

- `engines` (object)
- `next_steps` (array)
- `node` (object)
- `notes` (array)
- `ok` (boolean)
- `ready` (boolean)
- `self_check` (object)

## Diagnostics

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

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 18
- 2026-07-31: 18
- 2026-07-30: 42
- 2026-07-28: 42
- 2026-07-27: 24

## Links

- npm package: https://www.npmjs.com/package/astral-mcp
- Socket report: https://socket.dev/npm/package/astral-mcp
- Repository: https://github.com/davidmosiah/astral-mcp
- Changelog RSS feed: https://verifymcp.io/servers/davidmosiah-astral-mcp/astral-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/davidmosiah-astral-mcp/astral-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/davidmosiah-astral-mcp/astral-mcp