auseklis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_SHARED_SECRET | No | Optional bearer token secret for remote deployment (set as environment variable or secret). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_planet_positionA | 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, and retrograde state. 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), and Chiron (n-body from public JPL initial conditions). Examples:
|
| compute_natal_chartA | Compute a complete natal (birth) chart: the ten classical bodies plus lunar nodes, Lilith, and Chiron, 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:
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). |
| compute_transitsA | 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:
For the exact date a specific transit perfects, use find_aspect_times instead. |
| compute_progressionsA | 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:
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. |
| compute_synastryA | 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:
|
| compute_composite_chartA | 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:
|
| find_returnsA | 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:
To cast the full chart for a return moment, pass the returned datetime to compute_natal_chart with the person's current location. |
| get_moon_phaseA | 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:
|
| find_eclipsesA | 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:
|
| find_retrograde_periodsA | 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:
The Sun and Moon never retrograde and are rejected. |
| find_sign_ingressesA | 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:
|
| find_aspect_timesA | 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:
Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| natal_chart_reading | Compute a birth chart and walk through a structured, balanced interpretation of it. |
| current_sky_report | A snapshot of the sky right now: positions, moon phase, retrogrades, and upcoming events. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| glossary | Reference for interpreting auseklis output: bodies, points, aspects, orbs, house systems, zodiac frames, accuracy, and conventions. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/igmizo/auseklis'
If you have feedback or need assistance with the MCP directory API, please join our Discord server