Birthstar Vedic Astrology MCP
30 Vedic Jyotish tools: natal charts, dashas, yogas, nakshatras. Swiss Ephemeris.
| Endpoint | https://mcp.birthstar.ai/mcp (streamable-http) |
|---|---|
| Registry version | 1.29.1 |
| Now | 30 tools · grade C (76) · pin ts_9fa56230eeda70e43c6d3fe9bb5d9c45 · protocol 2025-06-18 |
| First / last listed | 2026-10-31 00:49 UTC / 2026-10-31 00:49 UTC |
| Grade over time | 2026-10-31: C (76), 30 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: create_chart get_grahas get_houses get_current_dasha get_dasha_periods get_timeline get_lagna_points get_panchanga get_yogas get_varga get_vimsopaka get_strengths get_ashtakavarga get_aspects get_karakas get_transits get_day_periods get_avasthas get_fixed_stars get_longevity get_compatibility get_doshas get_numerology get_prompt_library describe_chart rectify_birth_time get_account_status health_check server_stats calculate_birth_star
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 it.
Args:
dob: Date of birth, YYYY-MM-DD (proleptic Gregorian).
params: dob*, tob*, tz*, lat*, lon*, ayanamsha, house_system, node_type, transit_date |
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: "basic" (default) or "full". Full adds the KP sub-lo params: chart_id*, planets, detail |
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 does. "kp_cusps" — Placidus cusps with sub-lor params: chart_id*, method |
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 baked into the chart
when it was computed, not against today's date at call time params: chart_id* |
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 create_chart.
system: vimshottari (default), yogini, ashtottari, or params: chart_id*, system, within |
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 this
period change", "when does Saturn cross my Moon". get_dasha_periods answers
params: chart_id*, start_date*, end_date*, systems, types, include_samples, step |
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 under
`not_computed` with a reason rather than guessed.
params: chart_id* |
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.
params: chart_id* |
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.
params: chart_id* |
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 not.
Returns the varga ascendant and each planet' params: chart_id*, varga |
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 interpretive
band. The score is the classical quantity; the band labels are a convention
params: chart_id* |
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 the planet clears its own bar) and `rank_by_ratio`
when saying a planet is str params: chart_id*, detail |
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:
chart_id: Handle returned by create_chart.
planet: Restrict the per-p params: chart_id*, planet, include_sodhana |
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: Handle returned by create_chart.
planet: Restrict graha drishti to params: chart_id*, planet, include_argala |
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 counted in reverse, so its `effective_degrees` will
differ from its actual positi params: chart_id* |
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 chart's `as_of` date, which is the
transit_date it was created with — not today params: chart_id* |
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 answer "when is Rahu kala today" — that needs a chart created
for today's date. params: chart_id* |
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, are deliberately NOT computed —
their conditions are school-divergent — and a params: chart_id*, planets |
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.
params: chart_id* |
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 numbers and must be passed on to the reader, not dropped.
Do not present these as a params: chart_id* |
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.
params: chart_id_1*, chart_id_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.
params: chart_id* |
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.
params: name*, dob |
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,
dasha transitions, chart strength, school comparisons, timing windows).
Args:
params: category, include_full_templates |
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.
params: chart_id* |
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
worth attempting.
* **With events** — scores each candidate against params: dob*, tob*, tz*, lat*, lon*, events, half_width_minutes, step_minutes, ayanamsha |
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 can
plan around rather than something you discover by hitting it.
`credits_re params: none |
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 engine to an approximation without failing.
`status` is "ok" when the Swiss ephe params: none |
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 when the client restarts the server.
params: none |
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 of birth, YYYY-MM-DD (proleptic Gregorian).
tob: Time of birth, HH params: dob*, tob*, tz*, lat*, lon*, ayanamsha |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.