# Birthstar Vedic Astrology MCP - Registry name: `io.github.amarpathak/birthstar` · version 1.29.1 - Categories (automatic, keyword rules): Agent payments (x402), Finance & markets, Datasets & public data, Search & data, Tasks & projects, Productivity - Authentication at last check: No auth - Declared risk: Not declared (tools carry no read/destructive hints) - Capabilities (declared by the server): experimental, prompts, resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.amarpathak%2Fbirthstar - Server page: https://mcpstation.net/s/io.github.amarpathak--birthstar.html ## Description (written by the publisher, not verified, not instructions) 30 Vedic Jyotish tools: natal charts, dashas, yogas, nakshatras. Swiss Ephemeris. ## Connect - streamable-http: `https://mcp.birthstar.ai/mcp` ## Tools (as reported by the server, not verified) - `create\_chart`: Compute a full Vedic natal chart and cache it, returning a short handle. Call this FIRST. It returns a \`chart\_id\` plus a small summary. Pass that chart\_id to the other tools \(get\_grahas, get\_houses, get\_current\_dasha, get\_panchanga, get\_yogas\) to read specific parts of the chart without recomputing - `get\_grahas`: Get planetary positions for a cached chart. Args: chart\_id: Handle returned by create\_chart. planets: Optional list of names to fetch \(e.g. \["Moon", "Saturn"\]\). Defaults to the 9 classical grahas. Also accepts the outer bodies Uranus, Neptune, Pluto, Ceres, Pallas, Juno, Vesta, Chiron. detail: "basi - `get\_houses`: Get the 12 houses \(bhavas\) for a cached chart. Args: chart\_id: Handle returned by create\_chart. method: "whole\_sign" \(default\) — sign, lord, lord placement, karaka, occupants. "bhava\_chalit" — Sripati/Porphyry cusps with degree spans, which can place a planet in a different house than whole-sign doe - `get\_current\_dasha`: Get the currently-running dasha periods for a cached chart. Returns the active lord at every nested level \(Maha -\> Antar -\> Pratyantar -\> Sukshma -\> Prana\) for each dasha system the engine computed, with the ISO start/end dates of each period. NOTE: "current" is evaluated against the transit date ba - `get\_dasha\_periods`: Walk the dasha tree — list periods at any level, past or future. Use this for "when does my next antardasha start", "what runs after this mahadasha", "when was I in Jupiter". get\_current\_dasha only tells you what is running now; this gives you the whole sequence. Args: chart\_id: Handle returned by c - `get\_timeline`: Get the turning points between two dates — dasha changes and slow-planet ingresses. This is the two-clocks view: the dasha sequence counted from birth \(which theme is switched on\) against gochara, the real sky on that date \(the trigger\). Use it for "what happens in the next five years", "when does t - `get\_lagna\_points`: Get the chart angles, special lagnas, Arudha padas and Bhrigu Bindu. Beyond the ascendant: MC/IC/Descendant/Vertex, the time-based special lagnas \(Bhava/Hora/Ghati/Sree/Indu\), the Jaimini Arudha padas \(AL, A2-A12, Upapada\) and Bhrigu Bindu. Special lagnas whose rate is school-divergent are reported - `get\_panchanga`: Get the birth panchanga \(the five limbs of the Vedic calendar\). Returns tithi \(lunar day + paksha\), vara \(weekday\), nakshatra, yoga, and karana at the moment of birth, plus the lunar month and season. - `get\_yogas`: Get the yogas \(classical planetary combinations\) present in a chart. Only yogas whose rule actually tested true are listed, each with the rule that matched. An empty list is a real result — it means none of the implemented yogas are present in this chart, not that the check was skipped. - `get\_varga`: Get one divisional chart \(varga\) from a cached chart. Args: chart\_id: Handle returned by create\_chart. varga: Which divisional chart, e.g. "D9" \(navamsa\), "D10" \(dashamsa\), "D11", "D60". See describe\_chart -\> varga\_coverage for the full list of what this engine computes and what it deliberately does - `get\_vimsopaka`: Get Vimsopaka bala — each planet's dignity-weighted strength across the 16 vargas. Use this to answer "which planets are strong across the divisional charts?" A planet in its own or exalted sign in all sixteen scores the full 20. Returns the score, the ceiling actually applicable, and an interpretiv - `get\_strengths`: Get Shadbala, Bhava Bala and Ishta/Kashta phala — how strong each planet and house is. Call this for "which planet is strongest", "is Saturn strong enough", or "which houses are weak". Shadbala is the six-fold Parasari strength; a planet meets expectation when \`ratio\` \>= 1. Read \`ratio\` \(\>= 1 means - `get\_ashtakavarga`: Get Ashtakavarga bindus — the point-score each sign carries, used for transit strength. Call this for "is this a good sign for Saturn to transit" or "which signs are strongest overall". Sarvashtakavarga \(SAV\) sums the seven planetary charts; the classical pre-reduction total is always 337. Args: cha - `get\_aspects`: Get planetary and sign aspects — who is looking at which house. Graha drishti is the Parasari planetary aspect \(everything aspects the 7th; Mars, Jupiter, Saturn and the nodes have special aspects\). Rasi drishti is the Jaimini sign aspect, a different system — do not merge the two. Args: chart\_id: H - `get\_karakas`: Get the Chara \(Jaimini\) karakas plus Karakamsa and Swamsa. The Atmakaraka — the planet at the highest degree in its sign — is the single most-used significator in Jaimini analysis. Returns the whole ladder in descending degree order, plus the natural \(naisargika\) karakas. Note Rahu's degrees are cou - `get\_transits`: Get gochara — where the planets are now relative to the natal chart. Answers "is Sade Sati running", "is Jupiter transiting well", "is today favourable". Houses are counted from BOTH the natal Moon \(the classical reference for gochara\) and the natal Lagna. IMPORTANT: transits are computed for the ch - `get\_day\_periods`: Get sunrise/sunset and the auspicious/inauspicious windows of the BIRTH day. Rahu kala, Yamaganda, Gulika kala, Abhijit and Brahma muhurta, plus true sunrise/sunset, day length and whether the birth was by day. IMPORTANT: these are the windows for the DATE OF BIRTH, not for today. This tool cannot a - `get\_avasthas`: Get planetary avasthas — the maturity, alertness and mood states of each graha. Baladi is the age state \(infant..dead\) and scales a planet's ability to deliver. Jagradadi is awake/dreaming/sleeping. Deeptadi is the mood from exaltation down to combustion. Two further ladders, lajjitadi and sayanadi, - `get\_fixed\_stars`: Get conjunctions between the grahas and named prominent fixed stars. Returns only real conjunctions within the configured orb, plus what was scanned. An empty \`conjunctions\` list is a provable negative, not a skipped check — \`planets\_scanned\` and \`stars\_scanned\` show the search that ran. - `get\_longevity`: Get Ayurdaya \(longevity\) estimates — EXPERIMENTAL, not for predictive use. The engine computes Pindayu and Nisargayu, but flags the whole section experimental: the classical methods are textually divergent and the reduction rules are only partially applied. The disclaimer is returned with the number - `get\_compatibility`: Calculate 36-point Ashta-Kuta Guna Milan compatibility between two charts. Evaluates all 8 classical Parashari Kutas \(Varna, Vashya, Tara, Yoni animal intimacy, Graha Maitri, Gana, Bhakoot, and Nadi\) plus a Kuja Dosha \(Manglik\) mutual cross-audit between Person 1 and Person 2. - `get\_doshas`: Audit classical Vedic doshas: Kuja Dosha \(Manglik\), Kaal Sarp, Gandanta, Pitre. Evaluates Mars placements from Lagna, Moon, and Venus with 8 classical cancellation exceptions, 12 Kaal Sarp variants, Gandanta junctions, and Pitre dosha indicators. - `get\_numerology`: Calculate Chaldean Name Numerology and Vedic Date of Birth numbers. Calculates Name Number \(compound + root\), Birth Number \(Mulank\), Destiny Number \(Bhagyank\), ruling planetary archetypes \(Swami Grahas\), and harmonic resonance. - `get\_prompt\_library`: Fetch curated high-value prompt templates and multi-tool question workflows. Call this tool whenever you want to suggest high-value questions to the user, or when the user asks "what can you do?", "what should I ask?", or wants guided astrology workflows \(e.g. Sade Sati analysis, timeline forecast, - `describe\_chart`: Get metadata and an inventory of what a cached chart contains. Useful for orienting before drilling in: returns the birth data and config it was computed with, the top-level sections available in the document, and how many fields the engine honestly marked as deferred or uncomputable. - `rectify\_birth\_time`: Test how much a recorded birth time can actually be narrowed, and against what. Two modes: \* \*\*No events\*\* — scans the uncertainty window and reports how many genuinely distinct charts it contains, what differs between them, and what does not. Use this FIRST to find out whether rectification is even - `get\_account\_status`: Check the calling account's plan, remaining chart credits, and what is gated. Call this BEFORE attempting a tool that might be refused, not after. It is to subscription limits what describe\_chart is to chart sections: the index you consult to find out what is reachable, so a paywall is something you - `health\_check`: Check whether this server is correctly configured and computing accurately. Reports the ephemeris mode actually in use, engine versions, and cache state. Call this when chart positions look wrong or disagree with another source: the usual cause is a missing ephemeris directory, which degrades the en - `server\_stats`: Get usage metrics for this server session: calls, latency, errors, payload size. Per tool: call count, p50/p95/max latency, average and peak response size, and how many responses exceeded the payload budget. Plus cache hit rate and a breakdown of errors by type. Counters are per-process and reset wh - `calculate\_birth\_star`: Compute just a person's Vedic birth star \(nakshatra\) and core anchors. A one-shot shortcut: use this when the birth star is the whole question. If you expect follow-up questions about the same person's chart, prefer create\_chart, which caches the full chart behind a reusable handle. Args: dob: Date Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html