@vedika-io/mcp-server
OfficialRelated Servers
Alternatives to @vedika-io/mcp-server
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables AI agents to cast deterministic BaZi, Zi Wei Dou Shu, and Western astrology natal charts from birth details, with no setup or API key.145 npmMIT- AlicenseCqualityCmaintenanceEnables AI assistants to access Indian Vedic astrology services including Panchang, Kundli, matchmaking, and festivals through natural language.128MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access real-time Vedic astrology data and perform calculations like horoscopes, panchang, matchmaking, and planetary positions via the AstroChalit API.4 npmISC
- AlicenseAqualityAmaintenanceEnables AI agents to compute natal charts, horoscopes, synastry, transits, Vedic kundli, panchang, tarot, numerology and other insight domains through 258+ typed tools, hosted as Remote MCP over Streamable HTTP or run locally over stdio with one key.390MIT
- AlicenseAqualityAmaintenanceVedic and Western astrology for AI agents: 103 read-only tools for natal charts, dasha, kundali matching with Rajju and Vedha vetoes, panchanga, numerology and tarot, backed by Swiss Ephemeris and verified against NASA JPL Horizons.103MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to retrieve precise astrology calculations, including natal charts, transits, composites, harmonic midpoints, and ranked daily aspects, using real ephemeris data rather than guesses.51AGPL 3.0
TDQS
Scored across 48 tools
The vastu_* / vedika_* prefix split gives a useful first cut, but several pairs are hard to tell apart: vedika_compatibility vs vedika_matrimony_match (both Ashtakoot Guna Milan), vedika_numerology vs vedika_numerology_complete, and vedika_predictions vs vedika_horoscope all read as near-duplicates. vastu_operation is an explicit catch-all over the same 143-operation surface as the dedicated vastu_* tools, and vastu_job_status overlaps with vastu_job_results.
Names are uniformly snake_case and consistently namespaced by domain (vastu_* / vedika_*) with a readable verb_noun pattern (audit_floor_plan, cast, draw, recommend). The only inconsistency is that many tools are bare nouns (vedika_dasha, vedika_panchang, vedika_doshas) while siblings use verbs. No camelCase or style chaos.
48 tools is well past the heavy threshold and forces the agent to scan a long list for every request. The count is inflated by obvious consolidation candidates (numerology vs numerology_complete, two compatibility tools, several job-management tools) and by a catch-all vastu_operation that duplicates part of the dedicated surface.
Coverage of the astrology/vastu domain is genuinely broad — natal charts, dashas, doshas, compatibility, panchang, muhurta, vargas, western techniques, numerology, tarot/I Ching/Ba Zi, remedies, and a full Vastu lifecycle with jobs, artifacts and static references. Minor gaps remain (KP system only reachable via vedika_ai_chat, no update/edit operations for stored conversations beyond TTL extension), but nothing that blocks core workflows.