Asterwise
OfficialRelated Servers
Alternatives to Asterwise
- FlicenseNot gradedqualityDmaintenanceWorld'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.9-
- AlicenseAqualityDmaintenanceCalculates astrological natal charts with high precision using Swiss Ephemeris, supporting multiple house systems and location inputs.28 npm5AGPL 3.0
- AlicenseAqualityAmaintenanceHosted Streamable HTTP MCP server for Vedic astrology: panchang, kundali (birth chart), matchmaking, dashas, doshas, muhurta and 16 tools computed by a precision astronomy engine.1738 npmMIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceHigh-precision astrology tools for LLM agents, including natal charts, transits, progressions, synastry, and more, backed by Swiss Ephemeris.1MIT
- AlicenseAqualityCmaintenanceEnables compute of live Vedic astrology birth charts, dashas, kundali matches, and AI readings via 22 real API tools.2210 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to compute deterministic astrological data with Swiss Ephemeris, including natal charts, transits, synastry, and birth-place resolution, so they never invent planetary positions.4614 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to answer Vedic astrology questions about dashas, transits, and planetary positions using real sidereal calculations.AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceProvides real astrology and tarot computations using actual ephemeris and a 78-card deck, returning structured data such as natal charts, synastry, transits, and tarot draws without relying on an LLM for astrological facts.-
- FlicenseNot gradedqualityCmaintenanceMulti-tradition astrology engine that computes real birth charts, transits, and synastry for AI agents via MCP tools.8-
TDQS
Scored across 103 tools
The DO NOT CONFUSE WITH sections are exemplary and do heavy lifting, but 103 tools across heavily overlapping clusters (5 crystal tools, 9 tarot tools, 4 Vedic compatibility tools, 3 western transit variants, 4 dasha systems) still create significant selection risk. The pair asterwise_get_gemstone_recommendations and asterwise_get_crystal_recommendations_natal is genuinely hazardous — both derive gem/crystal prescriptions from natal charts using different engines.
Nearly every tool follows asterwise_get_<resource> in clean snake_case, and within-domain suffixes (varshaphal, varshaphal_saham, varshaphal_harsha_bala) are highly predictable. The deviations — check_sade_sati, check_mobile_number, check_vehicle_number, draw_tarot_cards — are semantically justified but break the dominant get_ pattern, preventing a 5.
103 tools is extreme by any standard, quadruple the 25+ threshold from the calibration rubric. Even granting the server's broad multi-domain scope (Vedic astrology, Western astrology, numerology, tarot, crystals, dreams, remedies), the surface is fragmented into overly granular endpoints: three transit-window variants, six individual numerology number calculators that duplicate the existing profile tool, and nine tarot tools.
Coverage is exhaustive for a read-only computational API: all major dasha systems, transits, multiple compatibility traditions, panchanga/muhurta, remedies, Western returns/progressions/synastry, numerology systems, tarot spreads, crystals, and dream symbols. Minor gaps — no standalone current-planetary-position ephemeris tool, no Vedic moon-sign-only endpoint, no house-system override for Vedic charts — are workable but not fatal.