Skip to main content
Glama

Vedaksha — Visión de los Vedas

Motor de efemérides y astrología védica en Rust de sala limpia, construido para la era de la IA agéntica. Precisión planetaria de sub-segundo de arco, cada algoritmo trazado a una fuente primaria, cualquier carta consultable como grafo de propiedades.

crates.io docs.rs PyPI npm CI MSRV License

Sitio web · Documentación · Playground · Referencia de API · Blog

clean-room · 0.103″ vs JPL Horizons · 1,069 tests + 24,350 oracle rows · MCP-native · BUSL-1.1 → Apache 2.0

Instalación · Inicio rápido · Precisión · Qué incluye · MCP + grafo de propiedades · Procedencia · Licencia


Instalación

Plataforma

Instalación

Notas

Rust

cargo add vedaksha

pipeline completo

Python

pip install vedaksha

motor vía WebAssembly, py3-none-any, Python ≥ 3.9 — sin cadena de herramientas de Rust

WASM

npm install vedaksha-wasm

navegador y edge, sin archivos de datos

MCP

cargo install vedaksha-mcp

stdio + HTTP (autenticación bearer)

Docker

docker run -e VEDAKSHA_MCP_TOKEN=… -p 3100:3100 ghcr.io/arthiqlabs/vedaksha-mcp

multi-arquitectura (amd64 + arm64)

Calcula janam kundali (cartas natales), panchanga, dashas, nakshatras, vargas, shadbala, ashtakavarga, muhurta y transits/gochara a partir de una efeméride de sub-segundo de arco (VSOP87A, ELP/MPP02, JPL DE440s/DE441).

flowchart LR
  K["JPL DE440s / DE441<br/>SPK kernel, ~31 MB"] --> E
  V["VSOP87A + ELP/MPP02<br/>compiled to constants,<br/>no data files"] --> E
  E["Ephemeris core<br/>precession · nutation<br/>light-time · ΔT"] --> W["Western<br/>houses · aspects<br/>dignities"]
  E --> J["Jyotish<br/>nakshatras · dashas · vargas<br/>panchanga · shadbala · muhurta"]
  W --> C["ComputedChart"]
  J --> C
  C --> G["Property graph<br/>Cypher · SurrealQL<br/>JSON-LD · RAG text"]
  C --> M["MCP server<br/>17 tools · stdio + HTTP"]
  C --> S["Rust · Python · WASM"]

Related MCP server: Precision astronomical ephemeris and planetary positions via the Swiss Ephemeris.

Inicio rápido

from vedaksha import Vedaksha

vk = Vedaksha()
chart = vk.natal_chart(julian_day=2451545.0, latitude=28.6139, longitude=77.2090)
cargo install vedaksha-mcp && vedaksha-mcp     # stdio: Claude Desktop, Cursor, VS Code

La ruta de Rust es un doctest compilado en crates/vedaksha/src/lib.rs.

Cada día juliano en las superficies públicas es UT1, no TT ni TDB. El motor convierte a TT internamente para los términos dinámicos y usa UT1 para la rotación de la Tierra, lo que fija el ascendente, el MC y las doce cúspides. Pasar un día juliano TDB añade una rotación de ΔT en lugar de eliminarla — 0,289° (17,3′) con el ΔT actual ≈ 69 s, en cada cúspide. La única excepción es la consulta SPK cruda (state_vector), que indexa el kernel directamente y toma TDB.

Precisión

Cada cifra se imprime mediante una prueba con nombre. Reproduce las tablas de efemérides con bash scripts/download_de440s.sh, luego cargo test -p vedaksha-ephem-core --release -- --include-ignored --nocapture; las cifras de ayanamsha provienen de cargo test -p vedaksha-astro sidereal, y la verificación cruzada contra una derivación independiente en Python de las mismas fuentes primarias de cargo test -p vedaksha-astro --test ayanamsha_fixture.

SpkReader vs JPL Horizons (DE441) — oracle_comparison.rs, 24,350 filas confirmadas (10 cuerpos × 2,435 fechas, 1900–2100). Horizons sirve DE441, por lo que esto mide nuestro pipeline DE440s contra un kernel independiente.

Era

Comparaciones

Media

Máximo

1900–2025 (ΔT medido)

15,350

0.103″

1.187″ (Urano)

1900–2100 (todos)

24,350

0.878″

44.912″ (Luna, 2099)

15,349 de 15,350 comparaciones antes de 2026 son sub-segundo de arco. Más allá de 2025 el residual es predicción de ΔT, no error de efemérides: nuestra extrapolación de Espenak–Meeus y el ΔT de Horizons divergen en ~68 s en 2099, y el error escala con la tasa angular de un cuerpo — la Luna (0,64″/s) acumula ~45″, Plutón prácticamente nada. En 2099-02-06, cinco cuerpos que abarcan 0,03–0,64″/s implican todos el mismo desplazamiento de 66–71 s, lo que es la firma de una diferencia de reloj, no de un error de posición.

AnalyticalProvider vs JPL Horizons — analytical_oracle.rs, 1900–2025: media general 0,239″, peor caso 1,896″ (Neptuno), Luna 0,169″ media vía ELP/MPP02. Muestreado densamente en 2,435 fechas por cuerpo.

Hasta el 2026-08-20 esas cifras eran 2,06″ de media y 24,22″ de peor caso, y este README atribuía la brecha a que VSOP87A es una teoría truncada. Eso era incorrecto, y la redacción protegía un defecto nuestro: el proveedor analítico respondía a EarthMoonBarycenter con la serie centrada en la Tierra de VSOP87A, por lo que el observador estaba a 4,671 km de distancia, y earth_state dividía una Luna relativa al baricentro por 1 + EMRAT en lugar de EMRAT para otros 56,8 km. Ambos están corregidos. El segundo también movió la ruta SPK, de 0,106″ a 0,103″.

ELP/MPP02 Moon — lunar_horizons.rs: 0,015″ en J2000, 0,020–0,053″ entre 1500–2500 d.C.

Lo que no se mide

  • Las cúspides de las casas no se validan contra ninguna referencia externa.

  • Ningún ayanamsha se valida contra otra implementación, y eso es deliberado. Los once se derivan hacia adelante desde una fuente primaria — un capítulo, un comité, el propio artículo del proponente o un catálogo de estrellas — y cada uno reproduce su propio ancla a 1e-9° y, donde su fuente primaria documenta uno, su propio año cero. Lo que no se afirma es acuerdo con los números de nadie más: compararlos sería la ingeniería inversa que esta re-derivación existe para deshacer. Ver docs/audit/2026-08-17-ayanamsha-cleanroom/.

  • Las pruebas de dasha y nakshatra son pruebas invariantes, no comparaciones externas: verifican que las constantes de BPHS suman 120 años y que los límites teselan el círculo.

Qué incluye

Dos proveedores de efemérides. SpkReader lee JPL DE440s (~31 MB) para trabajo de sub-segundo de arco. AnalyticalProvider compila VSOP87A + ELP/MPP02 a constantes y no necesita archivos de datos — para WASM, edge y Cloudflare Workers.

Jyotish, desde fuentes primarias. 27 nakshatras con padas y señores · 5 sistemas de dasha (Vimshottari, Yogini, Ashtottari, y Chara y Narayana de Jaimini) · los 16 vargas (D-1 → D-60) · shadbala de seis componentes con Ishta/Kashta phala · 11 ayanamshas, cada uno trazable a un capítulo, una estrella o un comité · los cinco miembros del panchanga, con vara calculado desde el amanecer local y Rahu/Gulika Kalam como ventanas de tiempo reales · drishti graduado según BPHS cap. 26 · nodos medios, verdaderos y osculadores, todos referidos a la eclíptica de la fecha, con la variante J2000 que sigue el OM de DE441 a 0,6″ (listo para sub-señor KP).

Occidental: cálculo, no interpretación. 10 sistemas de casas, aspectos mayores con movimiento aplicativo/separativo, dignidades esenciales, sinastría y compuesto. ChartConfig por defecto es tropical. No hay capa interpretativa occidental ni paridad con la superficie Jyotish.

Crates, publicados en crates.io al unísono: vedaksha (paraguas, 7 locales) · -math · -ephem-core · -astro · -vedic · -graph · -mcp.

MCP + grafo de propiedades

17 herramientas, descubribles con un solo tools/list. El catálogo se genera a partir de las definiciones de Rust y se bloquea con una prueba de instantánea, por lo que no puede desviarse silenciosamente del código.

compute_natal_chart · compute_dasha · compute_vargas · compute_karakas · compute_combustion · compute_shadbala · compute_ashtakavarga · compute_transit · compute_gochara · search_transits · search_muhurta · compute_panchanga · compute_drishti · compute_bhavas · compute_synastry · compute_composite · emit_graph

Cualquier carta se convierte en un grafo de propiedades mediante emit_graph o vedaksha_graph::chart_to_graph, emitiendo Cypher, SurrealQL, JSON-LD, JSON o texto de incrustación RAG. Un agente puede entonces preguntar "¿qué planetas aspectan al señor de la 7ª casa?" como una consulta de grafo en lugar de reimplementar la lógica de la carta. Los cálculos en sí devuelven structs tipados; el grafo es una proyección que se solicita.

Lo que una carta realmente produce: 4 de los 9 tipos de nodo de la ontología (Chart, Planet, Sign, House) y 7 de sus 12 tipos de arista. Nakshatra, Pada, Pattern, DashaPeriod y FixedStar están definidos en vedaksha_graph::ontology pero no se construyen a partir de un ComputedChart, que no lleva los datos que necesitan. Calcúlalos a través de sus propias APIs.

VEDAKSHA_MCP_TOKEN=… vedaksha-mcp --http --port 3100

El modo HTTP requiere Authorization: Bearer <token> en cada POST y se niega a iniciar sin VEDAKSHA_MCP_TOKEN, a menos que pases --insecure-no-auth para una red de confianza. /health y el GET informativo permanecen abiertos.

Procedencia de sala limpia

Cada algoritmo implementado lleva un comentario de documentación // Source: que nombra su artículo o tratado primario — VSOP87A, ELP/MPP02, estándares IAU, BPHS, Jaimini. Dos subsistemas se han re-derivado de fuentes primarias detrás de un firewall documentado, y cada uno incluye su propio directorio de auditoría: la teoría lunar (2026-05-09) y la superficie sidérea (2026-08-17). Cada uno registra las fuentes primarias, el proceso, lo que se buscó y rechazó, y un generador que re-deriva los valores para que la afirmación pueda re-ejecutarse en lugar de tomarse por confianza. Ver también DATA_PROVENANCE.md. Esta es la evidencia que un licenciatario de BUSL-1.1 puede auditar.

En producción

Producto

Qué es

kundalimcp.com

MCP Jyotish de IA agéntica con la suite completa de cálculos. Se construye directamente sobre los crates vedaksha-*.

kundali.live

Endpoint de consumidor — lecturas basadas en chat e informes PDF de autoservicio.

Licencia

Business Source License 1.1 — SPDX BUSL-1.1, que es lo que muestran crates.io, PyPI y npm. (BSL-1.0 es la licencia Boost no relacionada, de ahí el prefijo BUSL.)

  • No comercial — gratis (personal, investigación, educación, herramientas internas).

  • Comercial — $500, cobrado una vez por organización. Productos y asientos ilimitados, perpetuo, y cubre la versión que licencias y todas las versiones posteriores — no se cobra de nuevo por versión. Comprar →

  • Se convierte a Apache 2.0 cuatro años después del lanzamiento de cada versión. Ese texto de licencia futura se mantiene en CHANGE-LICENSE.txt — es la Change License en términos BUSL, no una licencia que puedas elegir hoy.

Ver LICENSE, SECURITY.md, CONTRIBUTING.md y MAINTENANCE.md.


Copyright © 2026 ArthIQ Labs LLC · Licenciado bajo la Business Source License 1.1 (BUSL-1.1).

Available Tools

17 tools
compute_ashtakavargaA
Read-only

Compute Bhinna Ashtakavarga (raw bindu tables) and Sarvashtakavarga for all 7 planets from sign positions. Source: BPHS Ch.66 vv.13-68. Trikona/Ekadhipatya Shodhana and Pinda Sadhana are not included.

Inputs: sun (required), mars (required), moon (required), lagna (required), +4 more. Returns: tables, sarvashtakavarga

compute_bhavasA
Read-only

Compute the whole-sign bhava (house) chart from an ascendant. In the Vedic whole-sign system the entire sign containing the ascendant is the 1st bhava, the next sign the 2nd, and so on — houses do not have cusps within signs. Returns the sign of each of the twelve bhavas with its kendra / trikona / dusthana / upachaya classification, and optionally places supplied grahas into their bhavas.

Inputs: ascendant (required), planets. Returns: houses, planets, lagna_sign

compute_combustionA
Read-only

Compute combustion state for each planet relative to the Sun: principle per BPHS Ch.7 vv.28-29, orbs per Surya Siddhanta IX.6-8 and X.1 (Moon 12, Mars 17, Mercury 14 or 12 retrograde, Jupiter 11, Venus 10 or 8 retrograde, Saturn 15 deg). Returns Combust, DeeplyCombust, or None for Moon, Mars, Mercury, Jupiter, Venus, Saturn with degrees of separation. This is a low-level tool over already-known positions, not a natal-chart tool: call compute_natal_chart first and pass its planets[].longitude (matched by planets[].name) and planets[].retrograde values straight through as this tool's inputs — do not recompute or re-derive them.

Inputs: sun (required), mars (required), moon (required), venus (required), +8 more. Returns: states

compute_compositeA
Read-only

Compute the midpoint composite chart of two charts: for each graha, the shorter-arc midpoint of its longitude in the two charts, and the arithmetic mean of its two speeds. The two charts must carry the SAME graha names — each graha is paired with its namesake, not with whatever happens to sit at the same position in a list — and a name present in one chart but not the other is an error naming that graha. Longitudes only: this tool needs no birth time, place or ephemeris.

Inputs: chart_a (required), chart_b (required). Returns: planets

compute_dashaA
Read-only

Compute Vedic dasha (planetary period) sequences. Supports eight classical systems: Vimshottari, Ashtottari, Yogini (Moon-longitude based, require moon_longitude); Chara, Narayana (sign based, require BOTH lagna_sign AND graha_signs, since each sign's period length is counted to the sign its lord occupies in this chart); Sthira, NiryanaShoola (niryana_shoola is accepted too) and Maheshwara (Jaimini rashi dashas, require lagna_sign AND graha_longitudes, since the atmakaraka and the tie-breaks of the strength tests read degrees). graha_signs takes the eight sign_index values compute_natal_chart already returns, graha_longitudes the eight sidereal longitudes; Ketu is derived from Rahu and must not be supplied. Yogini takes rounds (1 to 10 whole 36-year rounds) or until (a horizon Julian Day); Chara takes antardashas (twelve per period, BPHS 51.5-51.9). Sthira, NiryanaShoola and Maheshwara use the defaults of the vedic crate's dasha functions (see their module docs) and always carry their antardashas. Sthira and Maheshwara start from the Brahma graha; a chart whose marks leave none returns no_brahma: true with a message, not an error. Returns a JSON dasha tree with start/end Julian Days.

Inputs: birth_jd (required), until, levels, rounds, +7 more. Returns: Envelope depends on `system`; see the four variants below. Every period carries…

compute_drishtiA
Read-only

Compute graha drishti — Vedic sign aspects — for all nine grahas. Unlike Western aspects, drishti is cast from sign to sign and is asymmetric: every graha aspects the 7th from itself, and Mars additionally aspects the 4th and 8th, Jupiter the 5th and 9th, Saturn the 3rd and 10th. Returns each aspect with its graded strength (Full, ThreeQuarter, Half, Quarter) and the house distance.

Inputs: sun (required), ketu (required), mars (required), moon (required), +5 more. Returns: aspects

compute_gocharaA
Read-only

Compute Gochara (transit interpretation) for the seven grahas against a natal reference sign per BPHS Ch.29. Returns favourable/unfavourable verdict, house from natal, and raw vedha (obstruction) candidates per planet. The natal reference sign is the caller's choice — typically the natal Moon's sign (Chandra Gochara) or the natal Lagna's sign. Rahu and Ketu are not included.

Inputs: sun (required), mars (required), moon (required), venus (required), +6 more. Returns: entries

compute_karakasA
Read-only

Compute Jaimini Chara Karaka assignments from sidereal planet longitudes. Ranks planets by degrees within their current sign: highest = Atmakaraka (soul significator), lowest = Darakaraka (spouse significator). Supports 7-karaka (Sun–Saturn) and 8-karaka (adds Rahu) schemes.

Inputs: sun (required), mars (required), moon (required), venus (required), +5 more. Returns: karakas

compute_natal_chartA
Read-only

Compute a natal astrological chart for a given time and location. Returns JSON with each body's longitude, latitude, speed, sign, house, dignity and retrograde flag, the house cusps with ascendant and MC, the aspects, and the ayanamsha applied. Pass a sidereal ayanamsha for a Vedic chart (kundali); the default is tropical. To get a property graph, pass this output to emit_graph.

Inputs: latitude (required), longitude (required), julian_day (required), ayanamsha, +1 more. Returns: houses, aspects, planets, julian_day, +2 more

compute_panchangaA
Read-only

Compute the panchanga — the five limbs of the Vedic almanac — for an instant: tithi (lunar day, with paksha and lord), vara (weekday reckoned from local sunrise, with its lord and the Rahu and Gulika Kalam windows as Julian Days), nakshatra (with pada), yoga (one of the 27 nithya yogas, with degrees remaining), and karana (half-tithi). Takes sidereal longitudes; all returned instants are Julian Days (UT). vara.from_sunrise reports HOW the weekday was reckoned: true means it was taken from an actual local sunrise (the Vedic definition); false means no sunrise exists to reckon from — the polar day or polar night, above about ±66.5° latitude — and the value is the observer's local CIVIL weekday as a documented fallback, which is a different quantity. Check it before presenting the vara at high latitude. vara.rahu_kalam being null is NOT the same signal: the Kalam windows can also be null while from_sunrise is true.

Inputs: jd (required), sun (required), moon (required), latitude (required), +3 more. Returns: vara, yoga, tithi, karana, +1 more

compute_shadbalaA
Read-only

Compute the complete six-fold Shadbala of the seven grahas (Sun to Saturn) for a birth moment and place, per BPHS Ch.27, with Ishta and Kashta Phala per Ch.28, in virupas. Pass the moment and the place; the tool casts the chart itself and reads sunrise, sunset and the next sunrise from the engine. Every part is in the output, each in its own field: Sthana (uccha, saptavargaja, ojhayugma, kendradi, drekkana), Dig (continuous, the arc from the weak cusp over 3, 27.7), Kala (nathonnata, paksha, tribhaga, abda, masa, vara, hora, ayana and yuddha, which is signed), Cheshta (the cheshta kendra for Mars to Saturn, the Sun's ayana and the Moon's paksha bala, 27.18 and 27.24-25), Naisargika and Drik (a quarter of the benefic sphuta drishti added, a quarter of the malefic taken away, the aspect of Mercury and Jupiter added whole, 27.19; it can be negative or pass 60). The Sun's ayana and the Moon's paksha bala are counted once in kala and once in cheshta, each undoubled. The rules are the verses' defaults; the benefic and malefic grahas are those of BPHS 3.11, with Rahu (the mean node) and Ketu counting only as malefic company for Mercury. Each graha also carries its motion state (vakra, anuvakra, ... atichara, 27.21-23) against the mean geocentric motion; it is reported beside the strengths and is not part of any total. The Sun must both rise and set at the place: in the polar day or night there is no Hindu day to divide into thirds and horas, and the call fails by name.

Inputs: latitude (required), ayanamsha (required), longitude (required), julian_day (required), +3 more. Returns: cusps, moment, planets, julian_day, +3 more

compute_synastryA
Read-only

Compute synastry — the aspects each graha in one chart makes to each graha in another chart. Every graha in chart A is tested against every graha in chart B (the two charts do not need the same graha names), and each hit is returned with its aspect type, orb in degrees and strength (1.0 at exact, falling linearly to 0.0 at the orb boundary). Orbs are the traditional Lilly values — conjunction, trine and opposition 8°, square 7°, sextile 6°, minors 2° — scaled by orb_factor. Longitudes only: this tool needs no birth time, place or ephemeris.

Inputs: chart_a (required), chart_b (required), aspect_set, orb_factor. Returns: aspects

compute_transitA
Read-only

Compute transiting planet positions relative to a natal chart at a specific moment. Returns planet longitudes for the transit time alongside natal positions, enabling aspect calculation between transit and natal placements.

Inputs: natal_jd (required), natal_lat (required), natal_lon (required), transit_jd (required). Returns: natal_jd, transit_jd, natal_positions, transit_positions, +1 more

compute_vargasA
Read-only

Compute Vedic divisional charts (vargas). Given a time and place, returns one chart per requested division: the varga lagna, and for each of the ten bodies compute_natal_chart returns — the seven grahas plus the mean, true and osculating lunar node — its rashi longitude, the sign it occupies within that varga, its dignity in that sign, and its whole-sign bhava counted from the varga lagna. Ketu is not listed separately: it is the node's opposite point, 180 degrees away. The nodes carry no dignity, so that field is absent for them. Supply planet_longitude instead to divide a single longitude without an ephemeris lookup, in which case no graha name, dignity or bhava is returned because none is defined. Vargas are classically read on a sidereal zodiac: pass an ayanamsha, or accept the Tropical default this surface uses everywhere. Source: BPHS Ch. 6-7.

Inputs: latitude (required), divisions (required), longitude (required), julian_day (required), +3 more. Returns: vargas, tradition, julian_day, true_ayanamsha_value

emit_graphA
Read-only

Turn a chart into a queryable property graph. Accepts the output of compute_natal_chart directly (pass latitude and longitude alongside it), or an existing ChartGraph. Emits Neo4j Cypher, SurrealDB SurrealQL, JSON-LD, plain JSON, or RAG embedding text.

Inputs: format (required), chart_json (required), latitude, longitude, +1 more.

search_muhurtaA
Read-only

Search for auspicious time windows (muhurta) within a given period for a geographic location. Returns ranked muhurta candidates with quality scores based on tithi, nakshatra, yoga, karana, and planetary positions. The search window is capped at 30 days (see MUHURTA_SEARCH_RANGE_TOO_LARGE), a scope limit; for a longer horizon, issue several searches.

Inputs: end_jd (required), latitude (required), start_jd (required), longitude (required), +3 more. Returns: end_jd, results, latitude, start_jd, +4 more

search_transitsA
Read-only

Search for transiting planet–natal planet aspects within a time window. Supply natal positions and a Julian Day range; receive a list of exact transit moments with aspect type, orb, and applying/separating status.

Inputs: end_jd (required), start_jd (required), natal_positions (required), bodies, +2 more. Returns: end_jd, events, max_orb, start_jd, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target clearly different computations (dasha, shadbala, panchanga, ashtakavarga, karakas), and descriptions explicitly disambiguate close pairs like compute_transit vs search_transits (positions vs exact aspect moments) and compute_drishti vs compute_synastry (intra-chart sign aspects vs inter-chart aspects). The only residual overlap is conceptual: compute_transit vs compute_gochara both concern transits, and compute_natal_chart vs compute_bhavas both involve houses, so an agent may briefly hesitate before selecting.

    Naming Consistency5/5

    All 17 names are snake_case with a clear verb_noun shape: 13 compute_* tools, 2 search_* tools, and emit_graph. The pattern is predictable and immediately readable, with no camelCase or stylistic mixing.

    Tool Count4/5

    17 tools is on the upper edge but each corresponds to a genuinely distinct Vedic computation (vargas, dasha, shadbala, combustion, ashtakavarga, gochara, panchanga, drishti, bhavas, synastry, composite, transits, muhurta, graph export). The surface is broad and no tool feels decorative, though it is slightly heavy for easy scanning.

    Completeness4/5

    The surface covers the full lifecycle from natal chart construction through derived analyses (vargas, karakas, dashas, shadbala, ashtakavarga), prediction (transits, gochara, muhurta), and export (emit_graph). Minor gaps remain: no explicit yoga/combination detection, and ashtakavarga explicitly omits Trikona/Ekadhipatya Shodhana and Pinda Sadhana, but agents can work around these.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      World's first Vedic Astrology MCP Server — connect Claude, ChatGPT, Cursor, or any AI to real Vedic astrology. Provides horoscope predictions, compatibility matching, numerology, planetary positions, yogas and house analysis via MCP.
      11
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A self-contained MCP server that gives AI agents the ability to calculate high-precision astronomical data. It provides tropical zodiac coordinates, planetary speeds, retrograde detection, and house cusps using the trusted Swiss Ephemeris engine. 100%
      4
      AGPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Astrology MCP server that computes natal charts, transits, synastry, progressions, returns, eclipses, retrogrades, and moon phases from a real ephemeris, enabling AI agents to provide accurate astrological calculations without hallucination.
      12
      75 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Vedic astrology MCP server that computes birth charts, dashas, transits, and yogas locally using Swiss Ephemeris, enabling an LLM to interpret horoscopes and provide personalized advice.
      -