Auseklis Astrology MCP server

by igmizo·io.github.igmizo/auseklis·v0.4.0·1 stars

No reviews yet

Astrology from a real ephemeris: natal charts, transits, synastry, eclipses, returns. No API keys.

A88/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A88/100

full report

Adoption

New

1 stars51 downloads/wk

Reviews

Write one

Nobody has reviewed Auseklis Astrology yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Auseklis Astrology tools (12)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

compute_composite_chart
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,
compute_natal_chart
compute_progressions
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 po
compute_synastry
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
compute_transits
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.
find_aspect_times
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 Satu
find_eclipses
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" } -
find_retrograde_periods
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.
find_returns
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-
find_sign_ingresses
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 202
get_moon_phase
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)
get_planet_position

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings

Code scan39 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 78 days ago12/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Auseklis Astrology compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 88/100; higher than 75% of 48,255 servers
Tools: 12; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 1; more than 65% of 28,688 servers
Downloads a week: 51; more than 43% of 12,191 servers with a package

What its tools let an agent do: 12 read

Install Auseklis Astrology in Claude Code, Cursor or VS Code

Runs npx -y auseklis on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add auseklis -- npx -y auseklis

Add to Cursor

What the publisher says

From the Auseklis Astrology repository's README, as published. We do not edit it. Read it on GitHub

auseklis

Astrology MCP server — natal charts, transits, synastry, progressions, returns, eclipses, retrogrades, moon phases. Computed from a real ephemeris, so AI agents stop hallucinating planet positions.

Named after the Latvian morning star. MIT-licensed with no AGPL ephemeris data — see Licensing.

Tools

Plus two prompts (natalchartreading, currentskyreport) and a glossary resource (auseklis://glossary).

Features: local birth times with IANA timezones (full historical DST handling) · tropical and sidereal (Lahiri, Fagan/Bradley) zodiacs · whole-sign, equal, Porphyry, and Placidus houses · mean lunar nodes and Black Moon Lilith · Part of Fortune (classical day/night formula).

Installation

Claude Code

claude mcp add auseklis -- npx -y auseklis

Claude Desktop / any MCP client (stdio)

{
  "mcpServers": {
    "auseklis": {
      "command": "npx",
      "args": ["-y", "auseklis"]
    }
  }
}

No API keys, no configuration — the ephemeris is computed locally.

Desktop Extension

Download auseklis.mcpb from the releases page and double-click to install in Claude Desktop. Or build it yourself: npm run bundle.

Remote (self-hosted)

The same server runs as a Cloudflare Worker speaking Streamable HTTP. Deploy it to your own account:

npm run deploy   # wrangler deploy
claude mcp add --transport http auseklis https://auseklis.<your-subdomain>.workers.dev/mcp

Set the MCPSHAREDSECRET secret to require a bearer token.

Library usage

The ephemeris core (everything under src/ephemeris/) is importable directly — no MCP client or subprocess needed. This is the right shape for serverless runtimes (Vercel, Workers), where spawning npx auseklis per request is not an option:

import { computeNatalChart } from "auseklis/ephemeris";
import { findRetrogradePeriods } from "auseklis/ephemeris/events";
import { findEclipses } from "auseklis/ephemeris/eclipses";

const chart = computeNatalChart({
  utc: "1990-03-15T13:45:00Z",
  location: { latitude: 56.95, longitude: 24.11 }, // Riga
  houseSystem: "placidus",
});

auseklis/ephemeris carries the chart math (natal, transits, synastry, composite, progressions, single positions, angles) plus resolveInstant for local-time → UTC conversion; …/events and …/eclipses carry the time-domain searches. Fully typed, ESM only, no data files.

Example questions to ask

"Compute my natal chart — born 15 March 1990, 15:45 in Riga."
"What's transiting my Sun this month?"
"When exactly is my Saturn return?"
"Synastry between me and my partner?" (two birth date/times)
"When is Mercury retrograde in 2027, and in which signs?"
"Is tonight's full moon visible as an eclipse from here?"

The model handles place-name → coordinates; the server handles local-time → UTC via the IANA timezone database.

Accuracy

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Auseklis Astrology: common questions

Is Auseklis Astrology MCP server safe?: Yes, by our scan: it is graded A (88/100). Read the Auseklis Astrology safety report
How do I install Auseklis Astrology?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Auseklis Astrology need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Auseklis Astrology maintained?: The last commit was 117 days ago (2026-07-10). The latest release is v0.4.0.
How does Auseklis Astrology compare with other MCP servers?: safety score 88/100 (higher than 75% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.