Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Birthstar Vedic Astrology is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
30 Vedic Jyotish tools: natal charts, dashas, yogas, nakshatras. Swiss Ephemeris.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http birthstar-vedic-astrology-mcp https://mcp.birthstar.ai/mcp
# 2 — ask your agent for something these tools do
# create_chart, get_grahas, get_houses and 27 more
Birthstar Vedic Astrology costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http birthstar-vedic-astrology-mcp https://mcp.birthstar.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
30 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 it. Args: dob: Date of birth, YYYY-MM-DD (proleptic Gregorian).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dob | string | yes | — |
| tob | string | yes | — |
| tz | string | yes | — |
| lat | number | yes | — |
| lon | number | yes | — |
| ayanamsha | string | no | — |
| house_system | string | no | — |
| node_type | string | no | — |
| transit_date | no | — |
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: "basic" (default) or "full". Full adds the KP sub-lo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| planets | no | — | |
| detail | string | no | — |
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 does. "kp_cusps" — Placidus cusps with sub-lor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| method | string | no | — |
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 baked into the chart when it was computed, not against today's date at call time
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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 create_chart. system: vimshottari (default), yogini, ashtottari, or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| system | string | no | — |
| within | no | — |
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 this period change", "when does Saturn cross my Moon". get_dasha_periods answers
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| start_date | string | yes | — |
| end_date | string | yes | — |
| systems | no | — | |
| types | no | — | |
| include_samples | boolean | no | — |
| step | string | no | — |
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 under not_computed with a reason rather than guessed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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 not. Returns the varga ascendant and each planet'
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| varga | string | no | — |
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 interpretive band. The score is the classical quantity; the band labels are a convention
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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 the planet clears its own bar) and rank_by_ratio when saying a planet is str
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| detail | string | no | — |
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: chart_id: Handle returned by create_chart. planet: Restrict the per-p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| planet | no | — | |
| include_sodhana | boolean | no | — |
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: Handle returned by create_chart. planet: Restrict graha drishti to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| planet | no | — | |
| include_argala | boolean | no | — |
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 counted in reverse, so its effective_degrees will differ from its actual positi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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 chart's as_of date, which is the transit_date it was created with — not today
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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 answer "when is Rahu kala today" — that needs a chart created for today's date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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, are deliberately NOT computed — their conditions are school-divergent — and a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
| planets | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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 numbers and must be passed on to the reader, not dropped. Do not present these as a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id_1 | string | yes | — |
| chart_id_2 | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| dob | string | no | — |
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, dasha transitions, chart strength, school comparisons, timing windows). Args:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | no | — | |
| include_full_templates | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | yes | — |
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 worth attempting. * With events — scores each candidate against
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dob | string | yes | — |
| tob | string | yes | — |
| tz | string | yes | — |
| lat | number | yes | — |
| lon | number | yes | — |
| events | no | — | |
| half_width_minutes | integer | no | — |
| step_minutes | integer | no | — |
| ayanamsha | string | no | — |
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 can plan around rather than something you discover by hitting it. `credits_re
No parameter schema on file.
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 engine to an approximation without failing. status is "ok" when the Swiss ephe
No parameter schema on file.
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 when the client restarts the server.
No parameter schema on file.
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 of birth, YYYY-MM-DD (proleptic Gregorian). tob: Time of birth, HH
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dob | string | yes | — |
| tob | string | yes | — |
| tz | string | yes | — |
| lat | number | yes | — |
| lon | number | yes | — |
| ayanamsha | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Birthstar Vedic Astrology or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.29.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Birthstar Vedic Astrology can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.