Auseklis Astrology
NPM · AUSEKLIS · SCANNED SEP 20
Astrology from a real ephemeris: natal charts, transits, synastry, eclipses, returns. No API keys.
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
- 32 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to igmizo/auseklis). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 3579 tokens (~275/item across 13 items; 12 tools + 1 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 Management83
- Stability observed for 25 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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 Auseklis Astrology MCP server?
Auseklis Astrology runs locally as an npm package, launched with npx -y auseklis. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · auseklis
claude mcp add igmizo-auseklis -- npx -y auseklis
{
"mcpServers": {
"igmizo-auseklis": {
"command": "npx",
"args": [
"-y",
"auseklis"
]
}
}
} {
"servers": {
"igmizo-auseklis": {
"command": "npx",
"args": [
"-y",
"auseklis"
]
}
}
} codex mcp add igmizo-auseklis -- npx -y auseklis
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"igmizo-auseklis": {
"type": "local",
"command": [
"npx",
"-y",
"auseklis"
],
"enabled": true
}
}
} openclaw mcp add igmizo-auseklis --command npx --arg -y --arg auseklis
mcp_servers:
igmizo-auseklis:
command: "npx"
args: ["-y", "auseklis"] {
"McpServers": {
"igmizo-auseklis": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"auseklis"
]
}
}
} assistant mcp add igmizo-auseklis -t stdio -c npx -a -y auseklis
{
"mcpServers": {
"igmizo-auseklis": {
"command": "npx",
"args": [
"-y",
"auseklis"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −4
- Stability: pass → 0.77 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 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.
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 20 Sept 2026 · Analysed npm/auseklis@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | igmizo/auseklis |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/igmizo/auseklis/.github/workflows/release.yml@refs/tags/v0.4.0 |
| Rekor log index | 2137243508 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:30a898073cbdae786d62d4c0a5d59f06163ae7126c6c049b02cb0eb0c647720fdcbd313b21494ac69f3a88a3f72a84d715c1bac47916bc2a6705bfe81 |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 32 |
| 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 →
compute_composite_chart Compute Composite Chart ~386
Compute a midpoint composite chart for two people: a single chart describing the relationship itself, built from the shorter-arc midpoints of the two natal charts' positions and angles. Both birth locations are required (the composite angles derive from each chart's Ascendant/Midheaven). Example: - { datetime_a: "1990-03-15T15:45", timezone_a: "Europe/Riga", latitude_a: 56.95, longitude_a: 24.11, datetime_b: "1992-07-22T08:30", timezone_b: "America/New_York", latitude_b: 40.71, longitude_b: -74.01 }
| Name | Type | Req | Description |
|---|---|---|---|
| datetime_a | string | yes | Person A's birth date and time. |
| datetime_b | string | yes | Person B's birth date and time. |
| house_system | string | – | House system: whole-sign (default), equal, porphyry, or placidus. |
| latitude_a | number | yes | Person A's birth latitude. |
| latitude_b | number | yes | Person B's birth latitude. |
| longitude_a | number | yes | Person A's birth longitude. |
| longitude_b | number | yes | Person B's birth longitude. |
| timezone_a | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| timezone_b | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| zodiac | string | – | Zodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal). |
| Name | Type | Req | Description |
|---|---|---|---|
| aspects | array | yes | – |
| houses | object | yes | – |
| note | string | yes | – |
| positions | array | yes | – |
| zodiac | string | yes | – |
No examples provided.
compute_natal_chart Compute Natal Chart ~389
Compute a complete natal (birth) chart: the ten classical bodies plus lunar nodes, Lilith, Chiron and the four major asteroids, house cusps, Ascendant and Midheaven, the Part of Fortune, and all aspects. Accepts local birth time directly when given the IANA timezone — no manual UTC conversion needed. Supports tropical (Western) and sidereal (Vedic/Lahiri, Fagan-Bradley) zodiacs. Examples: - "Chart for 15 March 1990, 3:45pm in Riga" -> { datetime: "1990-03-15T15:45", timezone: "Europe/Riga", latitude: 56.95, longitude: 24.11 } - Vedic chart: add { zodiac: "sidereal-lahiri" } Returns: positions (13 points), houses (12 cusps + angles), the Part of Fortune (classical day/night formula, with the dayChart flag showing which applied), aspects, and the ayanamsa applied (0 for tropical).
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | yes | Birth date and time. |
| house_system | string | – | House system: whole-sign (default), equal, porphyry, or placidus. |
| latitude | number | yes | Geographic latitude in degrees, positive north (-90 to 90). |
| longitude | number | yes | Geographic longitude in degrees, positive east (-180 to 180). |
| timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| zodiac | string | – | Zodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal). |
| Name | Type | Req | Description |
|---|---|---|---|
| aspects | array | yes | – |
| ayanamsa | number | yes | – |
| houses | object | yes | – |
| location | object | yes | – |
| partOfFortune | object | yes | – |
| positions | array | yes | – |
| utc | string | yes | – |
| zodiac | string | yes | – |
No examples provided.
compute_progressions Compute Secondary Progressions ~312
Compute a secondary-progressed chart: the natal chart advanced one ephemeris day per year of life (the standard "day-for-a-year" method). Shows how the chart has symbolically evolved by a given date. Examples: - "My progressed chart for today, born 1990-03-15 15:45 Riga" -> { natal_datetime: "1990-03-15T15:45", natal_timezone: "Europe/Riga" } (target_datetime defaults to now) Returns progressed positions and the aspects progressed bodies make to natal bodies. The progressed Moon (~1 sign per 2.5 years) and progressed Sun (~1° per year) carry the most interpretive weight.
| Name | Type | Req | Description |
|---|---|---|---|
| natal_datetime | string | yes | Birth date and time. |
| natal_timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| target_datetime | string | – | Date to progress to. Defaults to now. |
| target_timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| zodiac | string | – | Zodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal). |
| Name | Type | Req | Description |
|---|---|---|---|
| ageYears | number | yes | – |
| aspectsToNatal | array | yes | – |
| natalUtc | string | yes | – |
| positions | array | yes | – |
| progressedUtc | string | yes | – |
| targetUtc | string | yes | – |
No examples provided.
compute_synastry Compute Synastry ~299
Compute the cross-chart aspects between two people's natal charts — the classic relationship-compatibility technique. Every aspect from person A's bodies/points to person B's is returned, along with both sets of positions. Locations are not needed: synastry aspects depend only on planetary positions. (House overlays would need both birth locations — compute the two natal charts separately for that.) Example: - { datetime_a: "1990-03-15T15:45", timezone_a: "Europe/Riga", datetime_b: "1992-07-22T08:30", timezone_b: "America/New_York" }
| Name | Type | Req | Description |
|---|---|---|---|
| datetime_a | string | yes | Person A's birth date and time. |
| datetime_b | string | yes | Person B's birth date and time. |
| timezone_a | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| timezone_b | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| zodiac | string | – | Zodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal). |
| Name | Type | Req | Description |
|---|---|---|---|
| aspects | array | yes | – |
| positionsA | array | yes | – |
| positionsB | array | yes | – |
No examples provided.
compute_transits Compute Transits ~236
Compute the aspects from a transiting sky to a natal chart — how the planets at one moment relate to the planets at a birth moment. Examples: - "What's transiting my chart today, born 1990-03-15 15:45 Riga time?" -> { natal_datetime: "1990-03-15T15:45", natal_timezone: "Europe/Riga" } (transit_datetime defaults to now) For the exact date a specific transit perfects, use find_aspect_times instead.
| Name | Type | Req | Description |
|---|---|---|---|
| natal_datetime | string | yes | Birth date and time. |
| natal_timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| transit_datetime | string | – | Moment of the transiting sky. Defaults to now. |
| transit_timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| Name | Type | Req | Description |
|---|---|---|---|
| transits | array | yes | – |
No examples provided.
find_aspect_times Find Aspect Times ~349
Find the exact moments a transiting body perfects an aspect to a natal position — "when exactly does Saturn square my Sun?" Retrograde loops produce multiple hits (typically three) and each is returned. The natal position can be given two ways: 1. natal_datetime (+ natal_timezone) and natal_body — computed for you 2. natal_longitude directly, if already known Examples: - "When does transiting Saturn square my natal Sun (born 1990-03-15 15:45 Riga)?" -> { transiting_body: "Saturn", aspect: "square", natal_datetime: "1990-03-15T15:45", natal_timezone: "Europe/Riga", natal_body: "Sun", from_datetime: "2026-01-01", to_datetime: "2030-01-01" }
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | yes | Which classical aspect to search for. |
| from_datetime | string | yes | Start of the search window. |
| natal_body | string | – | Which natal body/point is aspected. |
| natal_datetime | string | – | Birth date/time (with natal_body). |
| natal_longitude | number | – | Natal longitude in degrees, as an alternative to natal_datetime + natal_body. |
| natal_timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| to_datetime | string | yes | End of the search window (max 120 years after start). |
| transiting_body | string | yes | The moving body. |
| Name | Type | Req | Description |
|---|---|---|---|
| hits | array | yes | – |
No examples provided.
find_eclipses Find Eclipses ~227
Find lunar and solar eclipses in a date range (max 30 years), with the sign and longitude of the eclipsed luminary — the astrologically relevant datum. When latitude/longitude are provided, each solar eclipse also reports whether it is visible from that location and how much of the Sun is obscured there. Examples: - "Eclipses in 2026" -> { from_datetime: "2026-01-01", to_datetime: "2027-01-01" } - "Will I see the August 2026 eclipse from Riga?" -> add latitude: 56.95, longitude: 24.11
| Name | Type | Req | Description |
|---|---|---|---|
| from_datetime | string | yes | Start of the search window. |
| latitude | number | – | Observer latitude for local solar-eclipse visibility. |
| longitude | number | – | Observer longitude for local solar-eclipse visibility. |
| to_datetime | string | yes | End of the search window (max 30 years after start). |
| types | array | – | Restrict to lunar or solar eclipses. Default: both. |
| Name | Type | Req | Description |
|---|---|---|---|
| eclipses | array | yes | – |
No examples provided.
find_retrograde_periods Find Retrograde Periods ~161
Find a planet's retrograde periods in a date range: exact station-retrograde and station-direct moments, with the longitude and sign at each end. Periods overlapping the range edges are included whole. Examples: - "When is Mercury retrograde in 2026?" -> { body: "Mercury", from_datetime: "2026-01-01", to_datetime: "2027-01-01" } The Sun and Moon never retrograde and are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Which planet (not Sun/Moon). |
| from_datetime | string | yes | Start of the search window. |
| to_datetime | string | yes | End of the search window (max 50 years after start). |
| Name | Type | Req | Description |
|---|---|---|---|
| periods | array | yes | – |
No examples provided.
find_returns Find Returns ~313
Find the exact moments a body returns to its natal longitude — solar returns (the astrological "birthday", one per year), lunar returns (one per ~27.3 days), or any planetary return (e.g. Saturn return, one per ~29.5 years). Examples: - "My solar return in 2026, born 1990-03-15 15:45 Riga" -> { body: "Sun", natal_datetime: "1990-03-15T15:45", natal_timezone: "Europe/Riga", from_datetime: "2026-01-01", to_datetime: "2027-01-01" } - "When is my Saturn return?" -> body: "Saturn" with a multi-year window around ages 27–31. To cast the full chart for a return moment, pass the returned datetime to compute_natal_chart with the person's current location.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Which body's return to find, e.g. "Sun", "Saturn". |
| from_datetime | string | yes | Start of the search window. |
| natal_datetime | string | yes | Birth date and time. |
| natal_timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| to_datetime | string | yes | End of the search window (max 120 years after start). |
| Name | Type | Req | Description |
|---|---|---|---|
| returns | array | yes | – |
No examples provided.
find_sign_ingresses Find Sign Ingresses ~184
Find when a body crosses sign boundaries in a date range. Retrograde crossings (backing into the previous sign) are flagged. The Sun's Aries ingress is the March equinox; Sun ingresses mark the astrological "seasons". Examples: - "When does Saturn change signs in the next 3 years?" -> { body: "Saturn", from_datetime: "2026-01-01", to_datetime: "2029-01-01" } - "When does the Sun enter Aries in 2027?" -> body: "Sun", window covering March 2027
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Which body's ingresses to find. |
| from_datetime | string | yes | Start of the search window. |
| to_datetime | string | yes | End of the search window (max 120 years after start). |
| Name | Type | Req | Description |
|---|---|---|---|
| ingresses | array | yes | – |
No examples provided.
get_moon_phase Get Moon Phase ~151
Moon phase at a moment: phase angle, common name (e.g. "Waxing Gibbous"), illuminated fraction, the Moon's sign, and the next four quarter events (new moon, first quarter, full moon, last quarter) with exact times. Example: - "What's the moon phase tonight, and when is the next full moon?" -> {} (datetime defaults to now)
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | – | Moment to compute for. Defaults to now. |
| timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| Name | Type | Req | Description |
|---|---|---|---|
| illumination | number | yes | – |
| moonLongitude | number | yes | – |
| moonSign | string | yes | – |
| nextQuarters | array | yes | – |
| phaseAngle | number | yes | – |
| phaseName | string | yes | – |
No examples provided.
get_planet_position Get Planet Position ~356
Compute the zodiac position of a single body or point at a single moment. Returns the geocentric ecliptic longitude, sign and degree within sign, daily motion, retrograde state, declination, and ecliptic latitude. Use for "where is X" questions rather than a full chart. Bodies: Sun through Pluto, plus NorthNode, SouthNode (mean lunar nodes), Lilith (mean lunar apogee / Black Moon Lilith), Chiron, and the four major asteroids (Ceres, Pallas, Juno, Vesta) — all n-body from public JPL data. Aspects include parallels and contraparallels in declination. Examples: - "Where is Mars right now?" -> { body: "Mars" } (datetime defaults to now) - "Was Mercury retrograde on 2026-01-01?" -> inspect retrograde in the result - "Moon sign at 14:30 in Riga on 3 May 1985" -> { body: "Moon", datetime: "1985-05-03T14:30", timezone: "Europe/Riga" }
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Which body or point to locate. |
| datetime | string | – | Moment to compute for. Defaults to now. |
| timezone | string | – | IANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset. |
| zodiac | string | – | Zodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal). |
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| declination | number | yes | – |
| degreeInSign | number | yes | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| retrograde | boolean | yes | – |
| sign | string | yes | – |
| speed | number | yes | – |
No examples provided.
What is the Auseklis Astrology MCP server?
Auseklis Astrology is an MCP server listed in the public MCP registry as io.github.igmizo/auseklis. Astrology from a real ephemeris: natal charts, transits, synastry, eclipses, returns. No API keys. This page covers its npm package (auseklis).
Is the Auseklis Astrology MCP server safe to use?
Auseklis Astrology scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Auseklis Astrology MCP server expose?
Auseklis Astrology exposes 12 tools: get_planet_position, compute_natal_chart, compute_transits, compute_progressions, compute_synastry, and 7 more. Their descriptions and schemas cost roughly 3,363 tokens of context every time the server is loaded.
Is the Auseklis Astrology MCP server still maintained?
Auseklis Astrology is still listed as active in the MCP registry. We last reached this channel on 20 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 Auseklis Astrology MCP server under?
Auseklis Astrology declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.