118 endpoints for natal charts, 5-level dasha, kundli matching, panchanga, numerology and tarot. Free 500 calls a month, no card, no expiry.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.asterwise.com
103tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.asterwise.com/mcp
Skill page: https://www.mcpbundles.com/skills/asterwise-mcp-e778770bf0
Explore capabilities (103)
read 25
Showing 25 of 103
Showing 25 of 103 tools from the public preview. Connect the server to inspect the full live tool list.
Asterwise25
Natal Chart
read
asterwise_get_natal_chart
Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata.
WORKFLOW: BEFORE: None — this tool is standalone.
AFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists.
INPUT CONTRACT: BirthData enforces date YYYY-MM-DD, time HH:MM, lat -90..90, lon -180..180, ayanamsa enum locally (Pydantic). Unknown birth time may be entered as time='00:00' without error; lagna-
Description may be truncated on the public preview.
Natal Chart — Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata.
WORKFLOW: BEFORE: None — this tool is standalone.
AFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists.
INPUT CONTRACT: BirthData enforces date YYYY-MM-DD, time HH:MM, lat -90..90, lon -180..180, ayanamsa enum locally (Pydantic). Unknown birth time may be entered as time='00:00' without error; lagna-
Divisional Chart — Computes divisional (varga) chart positions from BirthData; pass chart_type for one varga, or omit chart_type for all sixteen.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — anchor D1 before reading higher vargas.
AFTER: None.
INPUT CONTRACT: chart_type enum is enforced locally (Pydantic). BirthData follows the global contract.
DO NOT CONFUSE WITH: asterwise_get_natal_chart — radix chart with houses and drishti, not the full varga dictionary.
asterwise_get_chart_strength — embeds
Chart Strength — Aggregates Shadbala, Bhavbala, Vimshopaka (with per-varga contributions), embedded sixteen vargas, Ashtakavarga, karaka maps, and graha yuddha pairs from BirthData.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises houses before reading bala tables.
AFTER: asterwise_get_yogas — optional configuration pass after strength review.
INPUT CONTRACT: BirthData only; no extra toggles.
DO NOT CONFUSE WITH: asterwise_get_yogas — boolean yoga catalogue, not numeric bala.
asterwi
Special Ascendants — Calls atmakaraka and ishta-devata endpoints sequentially and merges their payloads into top-level atmakaraka and ishta_devata objects for one BirthData.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — understand chart basics before devotional pointers.
AFTER: None.
INPUT CONTRACT: Wrapper returns { atmakaraka: <upstream dict>, ishta_devata: <upstream dict> } — not a flat data.* root; consumers must read nested .data fields inside each branch per upstream shape.
DO NOT CONFUSE WITH
Nakshatra Details — Looks up static metadata for one of twenty-seven nakshatras by exact name and returns interpretive, professional, activity, and body-map reference data.
WORKFLOW: BEFORE: None — this tool is standalone.
AFTER: None.
INPUT CONTRACT: nakshatra_name is forwarded raw — no local fuzzy matching or normalisation.
DO NOT CONFUSE WITH: asterwise_get_natal_chart — computes birth nakshatra from time/place, not encyclopaedic copy.
asterwise_get_dasha — uses Moon nakshatra for timing, not this lookup tabl
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
118 endpoints for natal charts, 5-level dasha, kundli matching, panchanga, numerology and tarot. Free 500 calls a month, no card, no expiry.
How do I connect Asterwise to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Asterwise provide?
Operate this server?
Request removal if you do not want Asterwise listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Asterwise?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Sade Sati — Evaluates Saturn's seven-and-a-half-year Moon-sign cycle phases against natal data for the current day and returns intensity, upcoming cycles, and historical rows.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm Moon sign context.
AFTER: asterwise_get_gochar — broader transit canvas if needed.
INPUT CONTRACT: No explicit query date — API pins to current day. BirthData global contract applies.
DO NOT CONFUSE WITH: asterwise_get_gochar — nine-planet daily scan including sade
Prashna Chart — Casts a Prashna chart for the query instant using supplied date, time, place, and a single-topic keyword, then returns houses, Moon diagnostics, verdict, and cusps.
WORKFLOW: BEFORE: None — standalone for horary.
AFTER: None.
INPUT CONTRACT: question must be exactly one of: self, wealth, siblings, property, children, health, marriage, death, travel, career, gains, loss. Full sentences are not validated locally and are rejected upstream → MCP INTERNAL_ERROR at the tool layer. PrashnaInput enfor
Lal Kitab Chart — Produces the Lal Kitab house and planet schema plus Rin (debt) flags from BirthData using Lal Kitab placement rules. Lal Kitab uses a distinct astrological system from standard Vedic computation, with its own house-based remedies.
WORKFLOW: BEFORE: None — standalone for Lal Kitab queries.
AFTER: asterwise_get_lal_kitab_remedies — practical totkas aligned to this chart.
INPUT CONTRACT: BirthData global contract; mixing interpretive systems in prose is a caller concern, not validated here.
DO N
Lal Kitab Remedies — Lists Lal Kitab style totkas per stressed planet from BirthData with priority tiers and typed action rows (remedy, donation, keep, avoid).
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_lal_kitab_chart — see chart before applying totkas.
AFTER: None.
INPUT CONTRACT: BirthData only.
DO NOT CONFUSE WITH: asterwise_get_remedies — mantra/gem prescriptions, not Lal Kitab totkas.
asterwise_get_gemstone_recommendations — classical Ratna focus, not household remedies.
Full output and error contract:
KP Chart — Builds a KP natal chart with sub-lords on grahas and twelve cusps from BirthData using the KP ayanamsa in the response.
WORKFLOW: BEFORE: RECOMMENDED — cross-check birth record before trusting sub-lords.
AFTER: asterwise_get_kp_significators — house-level significator chains.
INPUT CONTRACT: ayanamsa choice is not forced locally — mismatched settings still post to upstream. time='00:00' is accepted without warning.
DO NOT CONFUSE WITH: asterwise_get_natal_chart — classical bundle without KP s
KP Significators — Computes KP significator chains for all houses or one optional house from BirthData and returns house tables plus planet-tier reverse indexes.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_kp_chart — establish cusps before significators.
AFTER: None.
INPUT CONTRACT: house_number optional int; omit for all twelve. Values outside 1..12 are validated upstream only.
DO NOT CONFUSE WITH: asterwise_get_kp_chart — cusps and sub-lords, not tiered significator unions.
asterwise_get_natal_chart — class
KP Ruling Planets — Computes KP ruling planets for the instantaneous chart at lat/lon with no birth data and returns day lord, Moon/Ascendant lord chains, and a deduplicated ruling_planets list.
WORKFLOW: BEFORE: None — this tool is standalone.
AFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards.
INPUT CONTRACT: lat and lon only; no date parameter — "now" is implicit on the server clock.
DO NOT CONFUSE WITH: asterwise_get_kp_chart — needs BirthData and returns full natal KP cusps.
asterwis
Ashtakavarga — Computes full Ashtakavarga bindu matrices, trikona and ekadhipatya reductions, and sarva totals from BirthData for transit support analysis.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm chart before AVK study.
AFTER: asterwise_get_gochar — uses AVK scores in transit rows.
INPUT CONTRACT: BirthData only.
DO NOT CONFUSE WITH: asterwise_get_chart_strength — primary payload is Shadbala/Vimshopaka, though it embeds AVK too.
asterwise_get_gochar — applies AVK scores to transi
Varshaphal — Computes the annual Tajika-style solar return for a four-digit civil year and returns Muntha, Pancha Adhikari metrics, Tajika aspects, and varshaphal positions.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — baseline radix before annual overlay.
AFTER: None.
INPUT CONTRACT: year is a plain int sent as target_year upstream; callers must supply the true Gregorian return year, not age.
DO NOT CONFUSE WITH: asterwise_get_dasha — multi-decade Vimshottari, not one solar return.
asterwi
Varshaphal Saham — Computes all 10 Tajika Saham (sensitive points) for a Varshaphal solar return chart. Sahams are the Tajika equivalent of Arabic Parts — mathematically derived zodiac points that focus the annual horoscope on specific life themes.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_varshaphal — understand the base solar return chart (year lord, Muntha, Varsha Ascendant) before interpreting Saham lords. The Saham is meaningless without knowing which house it occupies from the Varsha Ascendant.
AFTER: a
Varshaphal Harsha Bala — Computes Harsha Bala (positional happiness score) for all 7 classical planets in a Varshaphal solar return chart. Maximum 20 per planet (4 components × 5 points each).
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_varshaphal — identify the Year Lord (Varsha Pati) before interpreting Harsha Bala. The Year Lord's Harsha Bala is the most actionable number in this response.
AFTER: asterwise_get_varshaphal_saham — use Harsha Bala to assess whether each Saham lord can deliver its theme with ease or d
Vimshottari Dasha — Computes Vimshottari Dasha from birth data and returns hierarchical period trees plus current Maha/Antar interpretation blocks.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — establishes chart and Moon context before interpreting Dasha lords.
AFTER: asterwise_get_dasha_transits — correlates active Dasha lords with transits for the same birth data.
INPUT CONTRACT: levels (int, default 2, max 5): tree depth — 1 = Mahadasha only; 2 adds Antardasha; 3 Pratyantar; 4 Sookshma; 5 Prana (
Dasha Transits — Combines active Vimshottari lords with today's transits and returns scored correlations plus transit longitudes and houses from Moon and Lagna.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — same birth data should be understood before interpreting houses and lords.
AFTER: asterwise_get_gochar — optional broader transit snapshot without dasha scoring.
INPUT CONTRACT: No date field — "today" is fixed by the API. All parameters are otherwise defined in the tool schema. BirthData foll
Char Dasha — Computes Char Dasha from birth data and returns sign lords as period rulers with ISO-dated Maha and Antar sequences plus karaka mappings.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises the chart before interpreting sign-based lords.
AFTER: asterwise_get_dasha — optional Vimshottari cross-check for the same native.
INPUT CONTRACT: Period start_date and end_date in data.periods[] are YYYY-MM-DD (ISO), unlike asterwise_get_dasha which uses DD/MM/YYYY in its tree. All o
Yogini Dasha — Computes the eight-Yogini, 36-year Yogini Dasha cycle with two-level period trees and DD/MM/YYYY boundaries from birth data.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — establishes birth context for interpreting Yogini lords.
AFTER: asterwise_get_dasha — optional Vimshottari comparison for the same native.
INPUT CONTRACT: Tree lives at data.periods.root[] — agents must not expect a top-level data.periods array. Calendar strings in periods use DD/MM/YYYY. BirthData follows the g
Ashtottari Dasha — Computes the 108-year Ashtottari Dasha tree with configurable depth (levels 1–5) and returns periods under data.periods.root with DD/MM/YYYY dates.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — chart context before choosing between Ashtottari and Vimshottari.
AFTER: asterwise_get_dasha — optional Vimshottari comparison.
INPUT CONTRACT: levels: same as asterwise_get_dasha (1–5), enforced locally before the API call. Periods use data.periods.root[], not data.periods[]. Dates in per
Ashtakoota Compatibility — Scores North Indian Ashtakoota (36-point Guna Milan) for two charts and returns koota breakdown, dosha flags, classical vetoes, mangal cross-check, and narrative guidance.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per person — understand charts before interpreting scores.
AFTER: asterwise_get_papasamyam — optional malefic balance overlay.
INPUT CONTRACT: Two BirthData objects follow the global contract (unknown midnight time accepted without flag). All scoring is computed upstr
Dashakoot — Computes the ten-koota Dashakoot grid for two charts, converts it to a ten-point score with percentage, and exposes boolean dosha flags plus supplementary diagnostics.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart for each native — context before regional scoring.
AFTER: asterwise_get_papasamyam — optional malefic differential.
INPUT CONTRACT: Two BirthData objects per global contract.
DO NOT CONFUSE WITH: asterwise_get_compatibility — North Indian 36-point Ashtakoota with differe
Papasamyam — Measures malefic stress from Lagna, Moon, and Venus references for each partner, compares totals, and labels compatibility level against a threshold.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_compatibility — establish baseline match quality.
AFTER: None.
INPUT CONTRACT: Two BirthData objects per global contract.
DO NOT CONFUSE WITH: asterwise_get_doshas — twelve natal dosha buckets for one chart, not pairwise malefic balance.
asterwise_get_compatibility — Guna Milan totals and vetoes, not
Porutham — Runs the Tamil ten-porutham checklist for two charts, counts passes out of ten, surfaces Rajju/Vedha classical condition booleans, and returns per-porutham evidence objects.
WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per native.
AFTER: asterwise_get_thirumana_porutham — extended twelve-koota read if needed.
INPUT CONTRACT: Two BirthData objects per global contract.
DO NOT CONFUSE WITH: asterwise_get_thirumana_porutham — twelve poruthams including Nadi and Varna, not ten.
asterw
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 103 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Asterwise require?
Asterwise may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.