io.github.davidmosiah/astral-mcp

NPM · ASTRAL-MCP · SCANNED AUG 3

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

Available components

+39 this week 63 63 Trust /100

Trust breakdown (6 categories)

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 Security88

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (99 of 100), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (99 of 100), 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 (MIT).Pass
Actively maintained (last published 1 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability65

AI-judged instruction clarity (excellent).Pass
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. 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.

Install

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 · astral-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.json

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

Changelog

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.

2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
31 Jul 26 −24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +18
- 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 functional
27 Jul 26 24

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 99 packages

99 packages in the resolved dependency tree · 94 deprecated · 33 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 10 exposed · ~2,548 tokens

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.

Tool Tokens

astral_agent_manifest Astral Agent Manifest ~93

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 Output Examples

Name	Type	Req	Description
response_format	string	—	Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Name	Type	Req	Description
agent_rules	array	yes	—
data_access_model	string	yes	—
links	object	yes	—
mcp_name	string	yes	—
package	object	yes	—
project	string	yes	—
recommended_first_calls	array	yes	—
standard_tools	array	yes	—
troubleshooting	array	yes	—

No examples provided.

astral_capabilities Astral Capabilities ~99

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 Output Examples

Name	Type	Req	Description
response_format	string	—	Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Name	Type	Req	Description
creator	object	yes	—
engines	object	yes	—
links	object	yes	—
mcp_name	string	yes	—
not_included	array	yes	—
project	string	yes	—
recommended_agent_flow	array	yes	—
supported	object	yes	—

No examples provided.

astral_compute_natal_chart Compute Natal Chart ~660

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 Output Examples

Name	Type	Req	Description
birth_date	string	yes	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	yes	Birth latitude in decimal degrees, -90..90. Resolve from a city name with astral_search_birthplace if you don't have it.
longitude	number	yes	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	yes	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).

Name	Type	Req	Description
aspects	array	yes	—
context	—	yes	—
houses	object	yes	—
meta	object	yes	—
planets	object	yes	—
precision	—	—	—

No examples provided.

astral_connection_status Astral Connection Status ~95

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 Output Examples

Name	Type	Req	Description
response_format	string	—	Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Name	Type	Req	Description
engines	object	yes	—
next_steps	array	yes	—
node	object	yes	—
notes	array	yes	—
ok	boolean	yes	—
ready	boolean	yes	—
self_check	object	—	—

No examples provided.

astral_current_transits Current Transits ~668

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 Output Examples

Name	Type	Req	Description
birth_date	string	yes	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	yes	Birth latitude in decimal degrees, -90..90. Resolve from a city name with astral_search_birthplace if you don't have it.
longitude	number	yes	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	yes	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).

Name	Type	Req	Description
abridged	boolean	—	—
currentPlanets	object	yes	—
generatedAt	string	yes	—
highlights	array	yes	—
localDate	string	yes	—
localTime	string	yes	—
moon	—	yes	—
note	string	—	—
privacy_mode	string	—	—
timezone	string	yes	—
upcoming	array	yes	—

No examples provided.

astral_data_inventory Astral Data Inventory ~85

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 Output Examples

Name	Type	Req	Description
response_format	string	—	Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Name	Type	Req	Description
categories	array	yes	—
data_access_model	string	yes	—
first_tools	array	yes	—
generated_at	string	yes	—
kind	string	yes	—
mcp_name	string	yes	—
notes	array	yes	—

No examples provided.

astral_demo Astral Demo ~91

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 Output Examples

Name	Type	Req	Description
response_format	string	—	Output shape. 'markdown' is a readable briefing for display; 'json' returns the full structured chart for further processing.

Name	Type	Req	Description
chart	—	yes	—
input	—	yes	—
kind	string	yes	—
note	string	yes	—

No examples provided.

astral_moon_phase Moon Phase ~175

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 Output Examples

Name	Type	Req	Description
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.

Name	Type	Req	Description
angle	number	yes	—
generatedAt	string	yes	—
illumination	number	yes	—
moonSign	string	yes	—
phase	string	yes	—
timezone	string	yes	—

No examples provided.

astral_search_birthplace Search Birthplace ~186

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 Output Examples

Name	Type	Req	Description
language	string	—	Preferred language for returned place names (ISO code), e.g. en, pt, es.
query	string	yes	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.

Name	Type	Req	Description
count	integer	yes	—
query	string	yes	—
results	array	yes	—

No examples provided.

astral_synastry Synastry (Two-Chart Comparison) ~396

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 Output Examples

Name	Type	Req	Description
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	yes	Second person's birth data.
person	object	yes	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).

Name	Type	Req	Description
abridged	boolean	—	—
aspects	array	yes	—
dimensions	—	yes	—
note	string	—	—
privacy_mode	string	—	—
score	number	yes	—
tone	string	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug