# Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) (remote · jagannatha-hora-359167915530.europe-west1.run.app) Vedic astrology (Jyotish): birth charts, divisional charts, dashas, yogas, transits, panchang - Trust score: 70/100 (medium) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-17 ## Components - remote · `jagannatha-hora-359167915530.europe-west1.run.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-jagannathahora-vedic-astrology/jagannatha-hora-359167915530.md), [page](https://verifymcp.io/servers/com-jagannathahora-vedic-astrology/jagannatha-hora-359167915530) ## Channel facts - Endpoint: `https://jagannatha-hora-359167915530.europe-west1.run.app/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.1` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-17. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 62/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 10962 tokens (~342/item across 32 items; 32 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http com-jagannathahora-vedic-astrology https://jagannatha-hora-359167915530.europe-west1.run.app/mcp ``` ### Codex ```toml [mcp_servers.com-jagannathahora-vedic-astrology] url = "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-jagannathahora-vedic-astrology": { "type": "remote", "url": "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-jagannathahora-vedic-astrology --url https://jagannatha-hora-359167915530.europe-west1.run.app/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-jagannathahora-vedic-astrology: url: "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp" ``` ### Other ```json { "mcpServers": { "com-jagannathahora-vedic-astrology": { "type": "http", "url": "https://jagannatha-hora-359167915530.europe-west1.run.app/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-15 (score 70, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-13 (score 69, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-12 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-11 (score 67, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-08-10 (score 66) First indexed and scored. ## MCP tools (32) ### `generate_horoscope` (~202 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_amsa_rulers` (~348 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_arudha_padas` (~556 tokens) Return the arudha padas (the perceived/reflected sign of each house) for the divisional charts. Each key is '-' (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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST - `varga` (string): Optional. Send EXACTLY one enum token (e.g. 'D-1', 'D-9', 'D-10') to return only that chart's arudha padas. Omit to get the D-1 (Rasi) chart's arudha padas. ### `get_ashtakavarga` (~333 tokens) 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. '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.) Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_bhava_bala` (~273 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_chandra_arudhas` (~220 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_chara_karakas` (~304 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_dasha` (~1100 tokens) 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; just name the system and the tool routes it automatically. 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 has 'dasha_type' ('graha' or 'rasi'), 'system', 'as_of' (anchor date), 'depth', and: 'current' — a ready-made summary of the running period ('maha'/'antar'/'pratyantar', a 'path' string, and 'current_period_ends'); 'maha_timeline' — every Maha-dasha over the life; 'current_maha' with its 'antars'; for graha systems 'current_antar' with its 'pratyantars'; and, at depth 4, 'current_pratyantar' with its 'sookshmas'. Rasi systems have two levels (no pratyantar). To drill into a SPECIFIC period regardless of date, pass 'maha' (and optionally 'antar') as a ruler name — the matching branch comes back under 'selected_maha'/'selected_antar' with a 'selection' echo. HOW TO REQUEST: send only birth details for the default (vimsottari, anchored today, depth 3). Optionally set 'system' to EXACTLY one enum token. Planetary (graha) systems: vimsottari (standard 120-yr), ashtottari, yogini, shodasottari, dwadasottari, panchottari, satabdika, chaturaaseeti_sama, shashtisama, shattrimsa_sama, dwisatpathi, kaala, buddhi_gathi, naisargika, aayu, tara, karaka, tithi_ashtottari, tithi_yogini, karana_chaturaaseeti_sama, saptharishi_nakshathra, rasi_bhukthi_vimsottari, yoga_vimsottari, ashtaka_varga_planet, ashtaka_varga_sign, ashtaka_varga_pinda, moola_graha, rashmi. Sign (rasi) systems: narayana, chara, kendraadhi_rasi, sudasa, drig, nirayana, shoola, kendraadhi_karaka, lagnamsaka, padhanadhamsa, mandooka, sthira, tara_lagna, brahma, varnada, yogardha, navamsa, paryaaya, trikona, kalachakra, chakra, sandhya_panchaka, chathurvidha_utthara, karaka_kendr… Input parameters: - `antar` (string): Optional ruler name of an antar to expand inside the maha named in 'maha' (graha systems). Returned under 'selected_antar'. Requires 'maha' to be set. - `as_of_date` (string): Anchor date as YYYY-MM-DD. The tree is centred on the period active at this date. Defaults to today. (This is separate from the birth 'date'.) - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `depth` (integer): How many levels to expand for the active branch: 1=maha, 2=+antar, 3=+pratyantar, 4=+sookshma. Defaults to 3 for graha systems and 2 for rasi. Level 4 (sookshma) applies to graha systems only. - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `maha` (string): Optional ruler name (planet for graha, sign for rasi) to expand a SPECIFIC maha regardless of date, e.g. 'Saturn'. Returned under 'selected_maha'. If the ruler occurs more than once, the occurrence n… - `place` (string): Optional birth-place name (cosmetic only). - `system` (string): Dasha system to use — any planetary (graha) or sign (rasi) system. Send EXACTLY one enum token. Defaults to 'vimsottari'. - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_divisional_chart` (~637 tokens) 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': , 'longitude': }. 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.) Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST - `varga` (string): The divisional chart to return. Send EXACTLY one of the enum tokens, e.g. 'D-9' for marriage (navamsa) or 'D-10' for career (dasamsa). Defaults to 'D-1' if omitted. ### `get_doshas` (~263 tokens) 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.
). Data only — no interpretation is added beyond what the engine reports. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_gochara` (~533 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `event_elevation` (number): Event elevation in metres (optional) - `event_latitude` (number): Event latitude (optional) - `event_longitude` (number): Event longitude (optional) - `event_place` (string): Event place name (optional; defaults to birth place) - `event_timezone` (number): Event timezone offset from UTC (optional) - `include` (array): Enrichment sections: 'ashtakavarga', 'gochara_phala', 'transit_charts' (default all three). Pass [] for lean. - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `node_type` (string): Rahu/Ketu node: 'mean' (default) or 'true'. - `place` (string): Optional birth-place name (cosmetic only). - `target_date` (string, required): Target date YYYY-MM-DD - `target_time` (string): Target time HH:MM:SS (default local noon) - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_gochara_range` (~420 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `event_elevation` (number): Event elevation in metres (optional) - `event_latitude` (number): Event latitude (optional) - `event_longitude` (number): Event longitude (optional) - `event_place` (string): Event place name (optional; defaults to birth place) - `event_timezone` (number): Event timezone offset from UTC (optional) - `from_date` (string, required): Range start YYYY-MM-DD - `include` (array): Enrichment sections (default all). Pass [] for lean per-day output. - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `time_of_day` (string): Time used per day (default local noon) - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST - `to_date` (string, required): Range end YYYY-MM-DD (max 60 days) ### `get_graha_arudhas` (~260 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_house_varnadas` (~201 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_longevity` (~437 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_marriage_match` (~353 tokens) 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. Input parameters: - `boy` (object, required): Boy / groom's birth details. - `girl` (object, required): Girl / bride's birth details. - `system` (string): Which match system to return: 'both' (default), 'north' (North Indian Ashtakoota / 36 points) or 'south' (South Indian 10 Porutham). ### `get_muhurta` (~476 tokens) 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.) Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `day_part_resolution_minutes` (integer): Time-of-day granularity (5-60) - `event_elevation` (number): Event elevation in metres (optional) - `event_latitude` (number): Event latitude (optional) - `event_longitude` (number): Event longitude (optional) - `event_place` (string): Event place name (optional; defaults to birth place) - `event_timezone` (number): Event timezone offset from UTC (optional) - `event_type` (string, required): Event to find a date for - `from_date` (string, required): Scan start YYYY-MM-DD - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `respect_inauspicious_windows` (boolean): Report Rahu/Gulika/Yamaganda avoid windows - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST - `to_date` (string, required): Scan end YYYY-MM-DD (max 90 days) ### `get_nakshatra_pada` (~337 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_other_bala` (~262 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_planet_ingress` (~194 tokens) 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. Input parameters: - `ayanamsa_mode` (string): Ayanamsa mode (default LAHIRI) - `from_date` (string, required): Range start YYYY-MM-DD - `planets` (array): Planet names; default Saturn/Jupiter/Rahu/Ketu - `timezone` (number): Offset for crossing dates (default UTC) - `to_date` (string, required): Range end YYYY-MM-DD (max ~5 years) ### `get_planetary_states` (~294 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_sahams` (~245 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_saturn_transit` (~320 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_shad_bala` (~331 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_special_lagnas` (~242 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_sphutas` (~307 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_surya_arudhas` (~220 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_upagrahas` (~238 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_vaiseshikamsa_bala` (~318 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_vimsopaka_bala` (~323 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `get_yogas` (~287 tokens) 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. Input parameters: - `date` (string, required): Birth date in YYYY-MM-DD format, e.g. 1985-06-15 - `latitude` (number, required): Birth-place latitude in decimal degrees, e.g. 13.0827 - `longitude` (number, required): Birth-place longitude in decimal degrees, e.g. 80.2707 - `place` (string): Optional birth-place name (cosmetic only). - `time` (string, required): Birth time in 24h HH:MM:SS format, e.g. 10:30:00 - `timezone` (number, required): Timezone offset from UTC in hours, e.g. 5.5 for IST ### `list_divisional_charts` (~128 tokens) 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. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-jagannathahora-vedic-astrology/jagannatha-hora-359167915530#diagnostics ## Score history - 2026-08-17: 70 - 2026-08-16: 70 - 2026-08-15: 70 - 2026-08-14: 69 - 2026-08-13: 69 - 2026-08-12: 68 - 2026-08-11: 67 - 2026-08-10: 66 ## Links - Remote endpoint: https://jagannatha-hora-359167915530.europe-west1.run.app/mcp - Repository: https://github.com/WorldAstrologers/jagannatha-hora - Website: https://jagannathahora.com/api-mcp/mcp-usage - Changelog RSS feed: https://verifymcp.io/servers/com-jagannathahora-vedic-astrology/jagannatha-hora-359167915530.xml - Changelog JSON feed: https://verifymcp.io/servers/com-jagannathahora-vedic-astrology/jagannatha-hora-359167915530.json - HTML version of this page: https://verifymcp.io/servers/com-jagannathahora-vedic-astrology/jagannatha-hora-359167915530