io.github.davidmosiah/astral-mcp
NPM · ASTRAL-MCP · SCANNED SEP 21
Precision-audited astrology MCP: natal charts, transits, synastry, moon phases. No API key.
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 22 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
- 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.davidmosiah/astral-mcp server?
io.github.davidmosiah/astral-mcp runs locally as an npm package, launched with npx -y astral-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · astral-mcp
claude mcp add davidmosiah-astral-mcp -- npx -y astral-mcp
{
"mcpServers": {
"davidmosiah-astral-mcp": {
"command": "npx",
"args": [
"-y",
"astral-mcp"
]
}
}
} {
"servers": {
"davidmosiah-astral-mcp": {
"command": "npx",
"args": [
"-y",
"astral-mcp"
]
}
}
} codex mcp add davidmosiah-astral-mcp -- npx -y astral-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"davidmosiah-astral-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"astral-mcp"
],
"enabled": true
}
}
} openclaw mcp add davidmosiah-astral-mcp --command npx --arg -y --arg astral-mcp
mcp_servers:
davidmosiah-astral-mcp:
command: "npx"
args: ["-y", "astral-mcp"] {
"McpServers": {
"davidmosiah-astral-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"astral-mcp"
]
}
}
} assistant mcp add davidmosiah-astral-mcp -t stdio -c npx -a -y astral-mcp
{
"mcpServers": {
"davidmosiah-astral-mcp": {
"command": "npx",
"args": [
"-y",
"astral-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Sept 26 −1
- Security disclosure: pass → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Analysed npm/astral-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
What is the io.github.davidmosiah/astral-mcp server?
io.github.davidmosiah/astral-mcp is listed in the public MCP registry as io.github.davidmosiah/astral-mcp. Precision-audited astrology MCP: natal charts, transits, synastry, moon phases. No API key. This page covers its npm package (astral-mcp).
Is the io.github.davidmosiah/astral-mcp server safe to use?
io.github.davidmosiah/astral-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.davidmosiah/astral-mcp server expose?
io.github.davidmosiah/astral-mcp exposes 10 tools: astral_compute_natal_chart, astral_current_transits, astral_synastry, astral_moon_phase, astral_search_birthplace, and 5 more. Their descriptions and schemas cost roughly 2,548 tokens of context every time the server is loaded.
Is the io.github.davidmosiah/astral-mcp server still maintained?
io.github.davidmosiah/astral-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.davidmosiah/astral-mcp server under?
io.github.davidmosiah/astral-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.