Vedaksha
Related Servers
Alternatives to Vedaksha
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for Indian astrology (Jyotisha) that provides deterministic Lahiri sidereal calculations, question-aware natal context, Vimshottari dasha, and current gochara, enabling natural language conversations about astrology with saved birth profiles.-
- 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.11-
- AlicenseNot gradedqualityCmaintenanceA 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%4AGPL 3.0
- AlicenseAqualityCmaintenanceAstrology 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.1299 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA 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.-
- AlicenseNot gradedqualityDmaintenanceVedic astrology MCP server that computes birth charts, dashas, transits, and ashtakavarga using Swiss ephemerides, enabling Claude to provide astrological interpretations.MIT
TDQS
Scored across 17 tools
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.
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.
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.
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.