NumeroClaw
by numeroclaw.com
Order a personalized numerology reading, paid by the person and delivered by email.
Runs in the cloudUpdated today
Install
Auseklis Astrology
Overview
Description from the maker (original English)
Astrology from a real ephemeris: natal charts, transits, synastry, eclipses, returns. No API keys.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Astrology & auspicious dates
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"auseklis": {
"command": "npx",
"args": [
"-y",
"auseklis"
]
}
}
}Run this in your terminal
claude mcp add auseklis -- npx -y auseklisOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"auseklis": {
"command": "npx",
"args": [
"-y",
"auseklis"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"auseklis": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"auseklis"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account igmizo, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Astrology & auspicious datesi
- More stars than 0% of the other 122 servers in this category
- Published to the registry more recently than 11% of the other 122 servers in this category
- Basic checks equal to or better than 100% of the other 122 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Auseklis Astrology safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: NumeroClaw, Yinyang Masters, Homo Universalis — 7 Wisdoms (BaZi, Tarot, Vedic Jyotish, Mayan, I-Ching, Human…
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Yinyang Masters
by gemral-edge
Tarot, astrology, numerology, Tu Vi and Bazi tools plus guides on habits and manifestation.
Runs in the cloudUpdated today
Install
Homo Universalis — 7 Wisdoms (BaZi, Tarot, Vedic Jyotish, Mayan, I-Ching, Human…
by David-Porto-Baraldes
Deterministic 7-Wisdoms (BaZi, Tarot, Vedic Jyotish, Mayan, I-Ching, Human Design, Kabbalah) MCP.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
| Tool | What it does |
|---|---|
get_planet_position | Position of one body/point at a moment (sign, degree, speed, retrograde) |
compute_natal_chart | Full birth chart: 13 points, houses, angles, Part of Fortune, aspects |
compute_transits | Aspects from the current (or any) sky to a natal chart |
compute_progressions | Secondary progressions (day-for-a-year) |
compute_synastry | Cross-chart aspects between two people |
compute_composite_chart | Midpoint composite chart of a relationship |
find_returns | Solar/lunar/planetary returns (exact moments) |
get_moon_phase | Phase, illumination, Moon sign, next four quarters |
find_eclipses | Lunar/solar eclipses with signs, incl. local visibility |
find_retrograde_periods | Station retrograde/direct moments for any planet |
find_sign_ingresses | When a body changes signs (equinoxes, Saturn ingresses, …) |
find_aspect_times | Exact moment a transit perfects ("when does Saturn square my Sun?") |
Plus two prompts (natal_chart_reading, current_sky_report) 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 auseklisClaude 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 deployclaude mcp add --transport http auseklis https://auseklis. .workers.dev/mcp
Set the MCP_SHARED_SECRET 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
Positions come from astronomy-engine (VSOP87 + NOVAS C 3.1): ±1 arcminute for 1700–2200, far below the 1° resolution astrological interpretation uses. Event searches (stations, ingresses, returns, quarters) are refined to ~1 second of time. Verified in CI against published eclipse dates, the 2026 equinox, NOVAS Sun positions, and an independent Placidus implementation.
Architecture
src/├── ephemeris/ Astrology core — backend-agnostic │ ├── engine.ts EphemerisBackend interface + astronomy-engine adapter (the swap seam) │ ├── index.ts Charts, aspects, synastry, composite, progressions │ ├── events.ts Time searches: returns, stations, ingresses, aspect times, moon phases │ ├── eclipses.ts Eclipse searches with astrological context │ ├── houses.ts Whole-sign, equal, Porphyry, Placidus (semi-arc solver) │ ├── points.ts Mean lunar nodes, Black Moon Lilith │ ├── sidereal.ts Ayanamsa (Lahiri, Fagan/Bradley) │ └── time.ts IANA timezone → UTC conversion (no dependencies, uses Intl) ├── mcp/ Tool/prompt/resource definitions on @modelcontextprotocol/sdk ├── stdio.ts Local entry — npx auseklis └── index.ts Remote entry — Cloudflare Worker, Streamable HTTP via @hono/mcp
The EphemerisBackend interface in engine.ts is the deliberate swap seam: a future Rust/WASM clean-room ephemeris only needs to reimplement that one interface.
Development
npm installnpm run typecheck # strict TS npm test # 23-check smoke suite (ephemeris references + MCP end-to-end) npm run build # emit dist/ npm run dev # local Cloudflare Worker on :8787 npx @modelcontextprotocol/inspector node dist/stdio.js # poke tools interactively
See docs/tools.md for the full tool reference and docs/architecture.md for design notes.
Licensing
MIT. This project deliberately avoids the Swiss Ephemeris (.se1/.se2 data files and the sweph bindings): those are AGPL-licensed, which would impose AGPL obligations on any network service built on them. Everything here is computed from MIT-licensed code with no external data files — safe to embed, fork, and deploy commercially. Details in NOTICE.
The trade-off: no Chiron or asteroids (they need ephemeris data files). They are on the roadmap via public-domain JPL-derived data.
Roadmap
- v1: Rust/WASM clean-room ephemeris backend behind the same
EphemerisBackendseam - Chiron + major asteroids from public-domain JPL data
- Koch houses, declination/parallel aspects