mcpbeat Sign in

Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) MCP Server

by jagannathahora Your server? Claim it
answering

Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) is answering right now. Last checked 9 min ago. It exposes 32 tools.

Vedic astrology (Jyotish): birth charts, divisional charts, dashas, yogas, transits, panchang

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 days of history
39 days agonow
100.0%
Uptime 24h
88 of 88 checks
32
Tools
read from the server
150 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 31

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.

1 Sep a tool description was rewritten get_dasha
26 Aug 29 tools changed the parameters they ask for generate_horoscope, get_amsa_rulers, get_arudha_padas and 26 more
24 Aug a tool description was rewritten get_ashtakavarga

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add vedic-astrology --transport http https://jagannatha-hora-359167915530.europe-west1.run.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "vedic-astrology": {
      "url": "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.vedic-astrology]
url = "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "vedic-astrology": {
      "url": "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "vedic-astrology": {
      "url": "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp"
    }
  }
}

Available tools 32

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

divisional
get_divisional_chart
Return ONE divisional (varga) chart for the birth. The response maps each body (Ascendant, Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu, Uranus, Neptune, Pluto) to its position in that chart as {'sign': <zodiac sign>, 'longitude': <degrees in sign 0-30>}. HOW TO REQUEST: set the 'varga' argument to EXACTLY ONE of these tokens (use this exact text, including the hyphen — do not send names like 'Rasi' or 'Navamsa'): D-1, D-2, D-3, D-4, D-5, D-6, D-7, D-8, D-9, D-10, D-11, D-12, D-16, D-20, D-24, D-27, D-30, D-40, D-45, D-60, D-81, D-108, D-144 If 'varga' is omitted, D-1 is returned. Pick the token by the area being asked about: D-1 general/body · D-2 wealth · D-3 siblings/courage · D-4 home/property · D-5 fame/power · D-6 health/enemies · D-7 children · D-8 longevity · D-9 marriage/dharma & overall strength · D-10 career · D-11 gains · D-12 parents · D-16 vehicles/luxuries · D-20 spirituality · D-24 education · D-27 general strength · D-30 misfortunes/character · D-40 maternal legacy · D-45 paternal legacy/conduct · D-60 past-life karma · D-81 finer marriage · D-108 finer/spiritual · D-144 lineage. If an unrecognised value is sent, the response returns the list of valid tokens. Data only — no interpretation is included. (Call 'list_divisional_charts' first if you want to browse the menu.)
list_divisional_charts
List the 23 divisional (varga) charts available via 'get_divisional_chart'. Returns, for each chart, the 'request_as' value to pass as the 'varga' argument (e.g. 'D-9'), its 'name' (e.g. Navamsa) and 'purpose' (what life area it analyses — marriage, career, children, etc.). Use this to choose the right chart for a question, then call 'get_divisional_chart' with that varga. Takes no birth details. Data only — no interpretation is included.
gochara
get_gochara
Planetary transit (Gochara) snapshot for a given date vs the natal chart. Returns that day's panchanga (vara, tithi+rikta, nakshatra, yoga, karana, paksha), muhurta windows (sunrise/sunset, Abhijit plus a clean Abhijit with Rahu/Gulika/Yamaganda overlap removed, and the avoid windows), all 9 planets (sign, degree, nakshatra/pada, retrograde, combust, house from Moon and Lagna, Ashtakavarga bindus, Gochara-phala favourable/Vedha), and the native's Tara Bala (Moon/Sun/Lagna), Chandra Bala and Sade Sati. Also returns the transit moment's D-1 (Rasi) and D-9 (Navamsa) charts under 'transit_charts' — each planet plus the Ascendant with sign and longitude. Rahu/Ketu use the Mean node by default; pass node_type='true' for True nodes. Data only — no verdict.
get_gochara_range
Raw transit (Gochara) details for EVERY day in a date range, in one call. For the 'AI decides' flow: returns the full per-day snapshot (panchanga, muhurta windows incl. clean Abhijit, all 9 planets, Ashtakavarga, Gochara-phala/Vedha, and the native's Tara/Chandra bala and Sade Sati) with NO scoring or 'best date' selection — you reason and decide. Natal reference computed once. Range capped at 60 days. Use get_muhurta instead if you want the system to rank dates by rules.
amsa
get_amsa_rulers
Return the amsa (fine sub-division) ruler for every point in the chart. Each entry maps a point to its 'sign', 'longitude', 'division_index', 'amsa_index' and 'amsa_name' (the named amsa it falls in, e.g. Dhanadaa, Sukhadaa). Points covered include the Ascendant and planets (Sun..Pluto), the upagrahas (Kaala, Mrityu, Gulika, Maandi, Dhooma, etc.), the special lagnas (Bhava, Hora, Ghati, Vighati, Pranapada, Indu, Sree, Kunda, Bhrigu Bindu), the varnada lagnas (Varnada_Lagna, V2–V12) and the sphutas (TriSphuta, Beeja_Sphuta, Tithi_Sphuta, Yogi_Sphuta, etc.). Data only — no interpretation is added.
arudha
get_arudha_padas
Return the arudha padas (the perceived/reflected sign of each house) for the divisional charts. Each key is '<chart>-<pada name>' (e.g. 'D-1-Arudha Lagna (AL)', 'D-1-Dhanarudha (A2)', 'D-9-Upapada Lagna (UL)') and the value is the sign that pada falls in. The 12 padas per chart are Arudha Lagna (AL), Dhanarudha (A2), Bhatrarudha (A3), Matri Pada (A4), Mantra Pada (A5), Roga Pada (A6), Dara Pada (A7), Mrityu Pada (A8), Bhagya Pada (A9), Karma Pada (A10), Labha Pada (A11) and Upapada Lagna (UL). By default only the D-1 (Rasi) chart's 12 padas are returned. To get a different chart's 12 padas, set the optional 'varga' argument to EXACTLY one of these tokens (use this exact text, with the hyphen): D-1, D-2, D-3, D-4, D-5, D-6, D-7, D-8, D-9, D-10, D-11, D-12, D-16, D-20, D-24, D-27, D-30, D-40, D-45, D-60, D-81, D-108, D-144. Only one chart is returned per call. Data only — no interpretation is added.
ashtakavarga
get_ashtakavarga
Return the Ashtakavarga bindu (benefic point) scores for the chart, labelled by planet and sign. 'binna_ashtaka_varga' (BAV) maps each of the Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn and the Ascendant to its bindu count in every sign (Aries..Pisces, 0-8 each). 'samudhaya_ashtaka_varga' (SAV) is the combined total per sign across the seven planets (sums to 337); higher SAV signs are stronger. 'sodhita_ashtaka_varga' (SoAV) is that same BAV after Trikona and Ekaadhipatya sodhana — the reduced grid the pindas are actually computed from — keyed by planet Sun..Saturn (7 rows; the Ascendant has no reduced row). 'raasi_pindas', 'graha_pindas' and 'sodhya_pindas' give per-planet pinda totals (sodhya = raasi + graha), keyed by planet Sun..Saturn. Data only — no interpretation is added. (The detailed prastara contributor grid is not included.)
bhava
get_bhava_bala
Return the Bhava Bala (strength of the 12 houses/bhavas), labelled by house. Keys are 'House 1' through 'House 12' (House 1 = Lagna/Ascendant bhava). Each house maps to 'total_virupas' (total bhava strength in virupas/shashtiamsas), 'rupas' (virupas / 60) and 'strength_ratio' (rupas divided by the required minimum — above 1 means the house meets the strength threshold). A higher value means a stronger house. Data only — no interpretation is added.
chandra
get_chandra_arudhas
Return the chandra arudhas: the arudha sign for each of the 12 houses counted from the Moon (Chandra Lagna). Keys are 'chandra_arudha_house_1' through 'chandra_arudha_house_12'; each value is the zodiac sign of that house's arudha. Data only — no interpretation is added.
chara
get_chara_karakas
Return the eight Jaimini chara (variable) karakas. Each role maps to the planet assigned to it, with that planet's sign and longitude. Roles: 'atma_karaka' (soul/self), 'amatya_karaka' (career/advisor), 'bhratri_karaka' (siblings), 'maitri_karaka' (friends/happiness), 'pitri_karaka' (father), 'putra_karaka' (children), 'jnaati_karaka' (relatives/obstacles) and 'data_karaka' (spouse). Each value has 'planet', 'sign' and 'longitude'. Roles are assigned by descending planetary longitude. Data only — no interpretation is added.
dasha
get_dasha
Return a dasha (planetary period) timeline as a nested tree anchored on a date — past, present and future in ONE call. Works for BOTH planetary (graha) and sign (rasi) dasha systems; name the 'system' and the tool routes it automatically (default: vimsottari, anchored today, depth 3). Every period node has the same shape: 'level' (maha/antar/pratyantar/sookshma), 'ruler' (planet for graha, sign for rasi), 'start', 'end' (YYYY-MM-DD) and 'relation' (past/current/future). The result carries 'dasha_type' ('graha'/'rasi'), 'system', 'as_of', 'depth', a ready-made 'current' summary (with a 'path' and 'current_period_ends'), the full 'maha_timeline', and the expanded 'current_maha' → 'current_antar' → 'current_pratyantar' branches (rasi systems have two levels, no pratyantar; level 4 'sookshma' is graha-only). To drill into a SPECIFIC period regardless of date, pass 'maha' (and optionally 'antar') as a ruler name — it returns under 'selected_maha'/'selected_antar'. The full list of supported graha and rasi systems is the 'system' enum below. Set 'as_of_date' (YYYY-MM-DD, separate from birth 'date') to anchor on another time. Data only — no interpretation.
doshas
get_doshas
Return the standard dosha (planetary affliction) checks for the chart. The result maps each dosha name to a verdict describing whether it is present in this horoscope and the reasoning. Doshas covered: Kala Sarpa Dosha, Manglik Dosha, Pitru Dosha, Guru Chandala Dosha, Ganda Moola Dosha, Kalathra Dosha, Ghata Dosha and Shrapit Dosha. The verdict text may contain light HTML markup (e.g. <br>). Data only — no interpretation is added beyond what the engine reports.
generate
generate_horoscope
Generate a Vedic (sidereal) birth horoscope from birth date, time and place, and return a concise summary (ascendant/lagna, moon sign, sun sign, birth nakshatra and pada). Call this first; later tools reuse the same cached chart.
graha
get_graha_arudhas
Return the graha arudhas: the arudha (reflected/perceived) sign for the Ascendant and for each of the nine grahas. Keys are 'Ascendant_arudha', 'Sun_arudha', 'Moon_arudha', 'Mars_arudha', 'Mercury_arudha', 'Jupiter_arudha', 'Venus_arudha', 'Saturn_arudha', 'Rahu_arudha' and 'Ketu_arudha'; each value is the zodiac sign of that arudha. Data only — no interpretation is added.
house
get_house_varnadas
Return the varnada lagnas for the houses. Keys are 'V2', 'V3' … 'V12' (the varnada for each house); each value has its 'sign' and 'longitude'. Data only — no interpretation is added.
longevity
get_longevity
Return the chart's classical Ayurdaya (longevity) computations for astrologer interpretation. The tool does not issue a longevity verdict; it exposes the classical signals side-by-side. 'overall_assessment' carries the sign-modality method result only: 'life_span_category' (0=Alpayu, 1=Madhyayu, 2=Poornayu) and a 'category_name' (the classical term, without an age bracket). 'method_note' explicitly states that this reflects the sign-modality method alone and is not a reconciled verdict. 'checks_summary' counts how many enumerated combinations were present in each band. 'baladrishta_checks' (child-mortality combinations), 'alpayu_checks' (short-life combinations) and 'madhyayu_checks' (medium-life combinations) list each combination with id, name, description and a 'present' boolean. 'calculation_basis' and 'key_planetary_positions' give the inputs used. 'reference_computations' is the full inventory of classical signals: the sign-modality method result and its classical age bracket (as a cited footnote value, not a claim), the Baladrishta / Alpayu / Madhyayu enumerated combinations with source citations, and 'longevity_related_yogas.detected' — the longevity-related yogas actually present in the chart, each cited to its BV Raman combination number.
marriage
get_marriage_match
Check Vedic marriage compatibility between a couple. Unlike the other tools, this needs TWO births: 'boy' and 'girl', each an object with date (YYYY-MM-DD), time (HH:MM:SS), latitude, longitude and timezone. Returns: 'summary' (headline North score/36 + rating, South matched/10 + rating, and Manglik flags for each); 'north_indian' (Ashtakoota — the 8 kootas Varna/Vasiya/Gana/Dina-Tara/Yoni/Raasi-Adhipathi/Raasi/Naadi each with score, max, category names and quality, the 4 additional poruthams, and overall total_score/36 + percentage + rating); 'south_indian' (the 10 Porutham booleans + matched count + rating); 'boy'/'girl' (nakshatra, pada, raasi); 'boy_dosha_data'/'girl_dosha_data' (mars/sun/saturn/rahu_ketu/total dosha scores — mars_dosha>0 means Manglik); and 'beeja_rasi'/'kshetra_rasi'. By default both systems are returned; set 'system' to 'north' or 'south' to get just one. Data only — no interpretation is added.
muhurta
get_muhurta
Find auspicious dates for an event across a date range (the system ranks the dates by classical rules). Scores each day by vara, nakshatra, tithi, paksha and the native's Tara Bala / Chandra Bala / Sade Sati, per the event's rule table, returning candidates sorted by a deterministic score (with breakdown + weights), the Abhijit / clean best-window and the Rahu/Gulika/Yamaganda avoid-windows. A failed mandatory rule caps the score. event_type is one of: griha_pravesha_own, griha_pravesha_rented, travel_prayana, vehicle_purchase, business_shop_opening, property_purchase_registration. Data only — the caller writes the recommendation. (Use get_gochara_range instead to get raw per-day details and decide yourself.)
nakshatra
get_nakshatra_pada
Return the birth (sidereal) nakshatra, nakshatra number, pada (quarter), nakshatra lord and degrees-within-nakshatra for every body in the chart: the Ascendant (lagna), the Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu and Ketu, plus the outer planets Uranus, Neptune and Pluto. Each entry contains: 'nakshatra' (one of the 27 nakshatras, e.g. Bharani, Magha, Ashwini), 'nakshatra_number' (1-27), 'pada' (1-4, the quarter of the nakshatra), 'nakshatra_lord' (the planet ruling that nakshatra) and 'degrees_in_nakshatra' (0-13.333, the body's position within the nakshatra). Data only — no interpretation is included.
other
get_other_bala
Return the additional planetary strength measures for the seven planets (Sun..Saturn). Contains 'harsha_bala' (joy/positional strength), 'pancha_vargeeya_bala' (five-source compound strength), 'dwadhasa_vargeeya_bala' (twelve-source strength), 'ishta_phala' (benefic result, 0-60) and 'kashta_phala' (malefic result, 60 - ishta). Each is a map of planet name to its value. Data only — no interpretation is added.
planet
get_planet_ingress
Sign-change (ingress) dates for one or more planets across a date range, retrograde-aware. Returns every sidereal sign change (default planets: the slow movers Saturn/Jupiter/Rahu/Ketu), including retrograde back-out and re-entry, each flagged forward/retrograde and with 'final_settling' marking the last crossing of each boundary in the window. Use for 'when does Saturn/Jupiter change sign' timing. Data only. Range capped at ~5 years.
planetary
get_planetary_states
Return the dignity and motion state of the planets, grouped by condition. Each field is a list of planet names: 'retrograde_planets' (planets in retrograde motion), 'combusted_planets' (too close to the Sun / combust), 'exalted_planets' (in their sign of exaltation), 'debilitated_planets' (in their sign of debilitation/fall), 'own_sign_planets' (in a sign they rule), 'friend_sign_planets' (in a friendly planet's sign) and 'enemy_sign_planets' (in an enemy planet's sign). A planet absent from all lists is in a neutral sign. Data only — no interpretation is included.
sahams
get_sahams
Return the sahams (Arabic parts / sensitive points) of the chart. The result maps each saham name to its computed zodiacal position, formatted as sign + degrees, minutes and seconds (e.g. 'Gemini 28° 47’ 58"'). Includes the full set such as Punya, Vidya, Yasas, Mitra, Vivaha, Putra, Karma, Roga, Mrithyu and the rest. Data only — no interpretation is added.
saturn
get_saturn_transit
Return Saturn's Sade Sati and related transit windows for the chart, with dates. 'sadeSati' holds the ~7.5-year Sade Sati periods two ways: 'degreeBased' (Saturn within ±45° of the natal Moon) and 'signBased' (Saturn in the 12th/1st/2nd signs from the Moon, each split into phase1/phase2/phase3 with sign, house and start/end dates); it also reports 'moonDegree' and 'moonSign'. 'moonTransits' and 'ascendantTransits' give Saturn's transit periods over the Moon and Ascendant, and 'ascendantDegree'/'ascendantSign' give the reference Ascendant. Each period has startDate, endDate and a description. Data only — no interpretation is added.
shad
get_shad_bala
Return the Shadbala (six-fold strength) of the seven planets (Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn), labelled by component and planet. The six source components are 'sthana_bala' (positional), 'kala_bala' (temporal), 'dig_bala' (directional), 'cheshta_bala' (motional), 'naisargika_bala' (natural) and 'drik_bala' (aspectual). It also returns 'total_virupas' (summed strength in virupas/shashtiamsas), 'total_rupas' (virupas / 60) and 'strength_ratio' (total rupas divided by the required minimum — a ratio above 1 means the planet meets the strength threshold). Each component maps planet name to its value. Data only — no interpretation is added.
special
get_special_lagnas
Return the special (derived) lagnas of the chart. Each lagna maps to its 'sign' and 'longitude'. Includes 'pranapada_lagna', 'indu_lagna', 'bhrigu_bindhu_lagna', 'sree_lagna', 'kunda_lagna', 'bhava_lagna', 'hora_lagna', 'ghati_lagna' and 'vighati_lagna'. Data only — no interpretation is added.
sphutas
get_sphutas
Return the sphutas (special computed sensitive points) of the chart. The result maps each sphuta name to its zodiacal position, formatted as sign + degrees, minutes and seconds (e.g. 'Scorpio 21° 18’ 7"'). Includes Tri Sphuta, Chatur Sphuta, Pancha Sphuta, Prana Sphuta, Deha Sphuta, Mrityu Sphuta, Sookshma Tri Sphuta, Beeja Sphuta (male fertility point), Kshetra Sphuta (female fertility point), Tithi Sphuta, Yoga Sphuta, Rahu Tithi Sphuta, Yogi Sphuta and Avayogi Sphuta. Data only — no interpretation is added.
surya
get_surya_arudhas
Return the surya arudhas: the arudha sign for each of the 12 houses counted from the Sun (Surya Lagna). Keys are 'surya_arudha_house_1' through 'surya_arudha_house_12'; each value is the zodiac sign of that house's arudha. Data only — no interpretation is added.
upagrahas
get_upagrahas
Return the upagrahas (shadowy sub-planets / calculated upagrahas) of the chart. Each upagraha maps to its 'sign' and 'longitude'. Includes dhuma, vyatipaata, parivesha, indrachaapa, upaketu, kaala, mrityu, artha_praharaka, yama_ghantaka, gulika and maandi. Data only — no interpretation is added.
vaiseshikamsa
get_vaiseshikamsa_bala
Return the Vaiseshikamsa Bala — the count of auspicious vargas (good divisional-chart dignities) each planet attains. The result is a list of four entries, one per classical weighting scheme (Shadvarga=6 charts, Sapthavarga=7, Dashavarga=10, Shodashavarga=16). Each entry maps the planets (Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Raagu, Kethu) to a string of the form 'AmsaName\n(vargas)\ncount' — e.g. 'Vyanjanaamsa\n(D1/D3/D12)\n3' meaning the amsa dignity name, the divisional charts contributing, and the integer count of good vargas. Data only — no interpretation is added.
vimsopaka
get_vimsopaka_bala
Return the Vimsopaka Bala — each planet's strength based on the dignity (varga / amsa) it occupies across the divisional charts. The result is a list of four entries, one per classical weighting scheme (Shadvarga=6 charts, Sapthavarga=7, Dashavarga=10, Shodashavarga=16). Each entry maps the planets (Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Raagu, Kethu) to a string of the form 'AmsaName\n(vargas)\nscore' — e.g. 'Kimsukaamsa\n(D2/D30)\n9.2' meaning the amsa dignity name, the divisional charts contributing, and the numeric Vimsopaka score (out of 20). Data only — no interpretation is added.
yogas
get_yogas
Return every yoga (planetary combination) detected in the birth chart. The result has two parts. 'summary' gives counts: 'total_yogas_found', 'total_yogas_possible', 'total_raja_yogas_found', 'total_raja_yogas_possible'. 'yoga_list' maps each detected yoga's key (e.g. nipuna_yoga, kedaara_yoga, amala_yoga) to a 4-element list: [chart it was found in (e.g. 'D1'), the yoga's display name, the condition/definition that formed it, and the effect/result it gives]. All detected yogas are included. Data only — no interpretation is added.

Endpoints

URLTransportStateLatencyChecked
https://jagannatha-hora-359167915530.europe-west1.run.app/mcp streamable-http answering 126 ms 9 min ago

Alternatives to Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang)

same job, measured the same way
Birthstar Vedic Astrology MCP
by amarpathak

30 Vedic Jyotish tools: natal charts, dashas, yogas, nakshatras. Swiss Ephemeris.

30 tools answering
I
Kundali Chart — Vedic Astrology MCP
by acerank-vedic-kundli

Vedic astrology MCP: 54 tools for charts, dashas, yogas, compatibility, muhurta, transit, remedies.

71 installs/wk local only
Vedic Astrology and Kundli MCP Server by RoxyAPI
by roxyapi

Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.

56 tools answering
MCP Starmeet
by star-meet

Free Vedic astrology MCP: birth-chart, panchang & nakshatra tools. Public API, no key required.

51 installs/wk local only
Asterwise
by asterwise

Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot.

103 tools answering
Marriage Astro
by novaventures-ai

Vedic Astrology MCP Server - birth charts, compatibility, and dosha analysis.

25 installs/wk local only
Western Astrology MCP Server by RoxyAPI
by roxyapi

Western natal charts, horoscopes, transits and synastry for AI agents, verified vs NASA JPL.

39 tools answering
Astral MCP
by davidmosiah

Precision-audited astrology MCP: natal charts, transits, synastry, moon phases. No API key.

62 installs/wk local only

Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) — questions

Answers built from our own checks of this server.

What can Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) do?
It exposes 32 tools, read directly from the server on our last check. Among them: generate_horoscope, get_amsa_rulers, get_arudha_padas, get_ashtakavarga, get_bhava_bala, get_chandra_arudhas and 26 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) mostly used for?
Its tools cluster around gochara and divisional. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 88 checks got a reply (100.0%), average response time 150 ms. The bar chart above shows every period we have measured.
Is Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang)?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) need an API key?
No. Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 32 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang)?
It answers our handshake in 150 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.