Asterwise

{
  "id": "aix_c95e9320eb",
  "name": "Asterwise",
  "operator": "(unclaimed - source: registry-official · publisher: com.asterwise)",
  "description": "Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-25",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "calendar-sync",
    "data-enrichment",
    "media-catalog",
    "sql-database"
  ],
  "protocols": {
    "mcp": "https://mcp.asterwise.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 1501,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 52,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-25T04:00:46.254Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://asterwise.com/"
    },
    {
      "label": "repository",
      "url": "https://github.com/asterwise/asterwise-mcp"
    }
  ],
  "avatar": "https://github.com/asterwise.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/asterwise"
    }
  ],
  "profile": {
    "mcp_server": "asterwise_mcp",
    "mcp_version": "1.0.1",
    "tool_count": 103,
    "tools": [
      {
        "name": "asterwise_get_natal_chart",
        "description": "Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata.\n\nWORKFLOW: BEFORE: None — this tool is standalone.\nAFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists.\n\nINPUT 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-sensitive results are then unreliable and callers must handle that — the API does not flag it.\n\nDO N"
      },
      {
        "name": "asterwise_get_divisional_chart",
        "description": "Computes divisional (varga) chart positions from BirthData; pass chart_type for one varga, or omit chart_type for all sixteen.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — anchor D1 before reading higher vargas.\nAFTER: None.\n\nINPUT CONTRACT: chart_type enum is enforced locally (Pydantic). BirthData follows the global contract.\n\nDO NOT CONFUSE WITH: asterwise_get_natal_chart — radix chart with houses and drishti, not the full varga dictionary.\nasterwise_get_chart_strength — embeds vargas inside strength metrics, different primary payload.\n\nFull output and error contract: https:/"
      },
      {
        "name": "asterwise_get_chart_strength",
        "description": "Aggregates Shadbala, Bhavbala, Vimshopaka (with per-varga contributions), embedded sixteen vargas, Ashtakavarga, karaka maps, and graha yuddha pairs from BirthData.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises houses before reading bala tables.\nAFTER: asterwise_get_yogas — optional configuration pass after strength review.\n\nINPUT CONTRACT: BirthData only; no extra toggles.\n\nDO NOT CONFUSE WITH: asterwise_get_yogas — boolean yoga catalogue, not numeric bala.\nasterwise_get_ashtakavarga — standalone AVK when strength bundle is not needed.\n\nFull output and error cont"
      },
      {
        "name": "asterwise_get_special_ascendants",
        "description": "Calls atmakaraka and ishta-devata endpoints sequentially and merges their payloads into top-level atmakaraka and ishta_devata objects for one BirthData.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — understand chart basics before devotional pointers.\nAFTER: None.\n\nINPUT 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.\n\nDO NOT CONFUSE WITH: asterwise_get_natal_chart — general chart; does not compute ishta devata workflow.\nasterwise_get_c"
      },
      {
        "name": "asterwise_get_nakshatra_details",
        "description": "Looks up static metadata for one of twenty-seven nakshatras by exact name and returns interpretive, professional, activity, and body-map reference data.\n\nWORKFLOW: BEFORE: None — this tool is standalone.\nAFTER: None.\n\nINPUT CONTRACT: nakshatra_name is forwarded raw — no local fuzzy matching or normalisation.\n\nDO NOT CONFUSE WITH: asterwise_get_natal_chart — computes birth nakshatra from time/place, not encyclopaedic copy.\nasterwise_get_dasha — uses Moon nakshatra for timing, not this lookup table.\n\nFull output and error contract: https://docs.asterwise.com/mcp/tools/get-nakshatra-details/"
      },
      {
        "name": "asterwise_check_sade_sati",
        "description": "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.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm Moon sign context.\nAFTER: asterwise_get_gochar — broader transit canvas if needed.\n\nINPUT CONTRACT: No explicit query date — API pins to current day. BirthData global contract applies.\n\nDO NOT CONFUSE WITH: asterwise_get_gochar — nine-planet daily scan including sade_sati_active flag but less Sade Sati detail than this tool.\nasterwise_get_transits — ingress/station"
      },
      {
        "name": "asterwise_get_prashna_chart",
        "description": "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.\n\nWORKFLOW: BEFORE: None — standalone for horary.\nAFTER: None.\n\nINPUT 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 enforces date/time/lat/lon/ayanamsa patterns locally.\n\nDO NOT CONFUSE WITH: asterwise_get_natal_chart — r"
      },
      {
        "name": "asterwise_get_lal_kitab_chart",
        "description": "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.\n\nWORKFLOW: BEFORE: None — standalone for Lal Kitab queries.\nAFTER: asterwise_get_lal_kitab_remedies — practical totkas aligned to this chart.\n\nINPUT CONTRACT: BirthData global contract; mixing interpretive systems in prose is a caller concern, not validated here.\n\nDO NOT CONFUSE WITH: asterwise_get_natal_chart — classical radix, not Lal Kitab lk_house logic.\nasterwis"
      },
      {
        "name": "asterwise_get_lal_kitab_remedies",
        "description": "Lists Lal Kitab style totkas per stressed planet from BirthData with priority tiers and typed action rows (remedy, donation, keep, avoid).\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_lal_kitab_chart — see chart before applying totkas.\nAFTER: None.\n\nINPUT CONTRACT: BirthData only.\n\nDO NOT CONFUSE WITH: asterwise_get_remedies — mantra/gem prescriptions, not Lal Kitab totkas.\nasterwise_get_gemstone_recommendations — classical Ratna focus, not household remedies.\n\nFull output and error contract: https://docs.asterwise.com/mcp/tools/get-lal-kitab-remedies/"
      },
      {
        "name": "asterwise_get_kp_chart",
        "description": "Builds a KP natal chart with sub-lords on grahas and twelve cusps from BirthData using the KP ayanamsa in the response.\n\nWORKFLOW: BEFORE: RECOMMENDED — cross-check birth record before trusting sub-lords.\nAFTER: asterwise_get_kp_significators — house-level significator chains.\n\nINPUT CONTRACT: ayanamsa choice is not forced locally — mismatched settings still post to upstream. time='00:00' is accepted without warning.\n\nDO NOT CONFUSE WITH: asterwise_get_natal_chart — classical bundle without KP sub-lords.\nasterwise_get_kp_ruling_planets — live moment rulers, not natal cusps.\n\nFull output and er"
      },
      {
        "name": "asterwise_get_kp_significators",
        "description": "Computes KP significator chains for all houses or one optional house from BirthData and returns house tables plus planet-tier reverse indexes.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_kp_chart — establish cusps before significators.\nAFTER: None.\n\nINPUT CONTRACT: house_number optional int; omit for all twelve. Values outside 1..12 are validated upstream only.\n\nDO NOT CONFUSE WITH: asterwise_get_kp_chart — cusps and sub-lords, not tiered significator unions.\nasterwise_get_natal_chart — classical drishti matrices differ from KP significator tiers.\n\nFull output and error contract: https://do"
      },
      {
        "name": "asterwise_get_kp_ruling_planets",
        "description": "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.\n\nWORKFLOW: BEFORE: None — this tool is standalone.\nAFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards.\n\nINPUT CONTRACT: lat and lon only; no date parameter — \"now\" is implicit on the server clock.\n\nDO NOT CONFUSE WITH: asterwise_get_kp_chart — needs BirthData and returns full natal KP cusps.\nasterwise_get_prashna_chart — horary keyword workflow, not ruling-planet snapshot.\n\nFull output and error co"
      },
      {
        "name": "asterwise_get_ashtakavarga",
        "description": "Computes full Ashtakavarga bindu matrices, trikona and ekadhipatya reductions, and sarva totals from BirthData for transit support analysis.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm chart before AVK study.\nAFTER: asterwise_get_gochar — uses AVK scores in transit rows.\n\nINPUT CONTRACT: BirthData only.\n\nDO NOT CONFUSE WITH: asterwise_get_chart_strength — primary payload is Shadbala/Vimshopaka, though it embeds AVK too.\nasterwise_get_gochar — applies AVK scores to transits rather than exposing raw matrices.\n\nFull output and error contract: https://docs.asterwise.com/mc"
      },
      {
        "name": "asterwise_get_varshaphal",
        "description": "Computes the annual Tajika-style solar return for a four-digit civil year and returns Muntha, Pancha Adhikari metrics, Tajika aspects, and varshaphal positions.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — baseline radix before annual overlay.\nAFTER: None.\n\nINPUT CONTRACT: year is a plain int sent as target_year upstream; callers must supply the true Gregorian return year, not age.\n\nDO NOT CONFUSE WITH: asterwise_get_dasha — multi-decade Vimshottari, not one solar return.\nasterwise_get_transits — ingress/station timeline, not annual Tajika chart.\n\nFull output and error contract"
      },
      {
        "name": "asterwise_get_varshaphal_saham",
        "description": "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.\n\nWORKFLOW: 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.\nAFTER: asterwise_get_varshaphal_harsha_bala — assess the Saham lord's positional happiness score to determin"
      },
      {
        "name": "asterwise_get_varshaphal_harsha_bala",
        "description": "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).\n\nWORKFLOW: 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.\nAFTER: asterwise_get_varshaphal_saham — use Harsha Bala to assess whether each Saham lord can deliver its theme with ease or difficulty.\n\nINPUT CONTRACT: Same as asterwise_get_varshaphal — BirthData plus target_year.\ntarget_ye"
      },
      {
        "name": "asterwise_get_dasha",
        "description": "Computes Vimshottari Dasha from birth data and returns hierarchical period trees plus current Maha/Antar interpretation blocks.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — establishes chart and Moon context before interpreting Dasha lords.\nAFTER: asterwise_get_dasha_transits — correlates active Dasha lords with transits for the same birth data.\n\nINPUT CONTRACT: levels (int, default 2, max 5): tree depth — 1 = Mahadasha only; 2 adds Antardasha; 3 Pratyantar; 4 Sookshma; 5 Prana (much larger payload). Response dates in periods[] use DD/MM/YYYY, not ISO. BirthData fields follow g"
      },
      {
        "name": "asterwise_get_dasha_transits",
        "description": "Combines active Vimshottari lords with today's transits and returns scored correlations plus transit longitudes and houses from Moon and Lagna.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — same birth data should be understood before interpreting houses and lords.\nAFTER: asterwise_get_gochar — optional broader transit snapshot without dasha scoring.\n\nINPUT CONTRACT: No date field — \"today\" is fixed by the API. All parameters are otherwise defined in the tool schema. BirthData follows the global contract (unknown birth time: time='00:00' accepted without detection).\n\nDO NOT CONFU"
      },
      {
        "name": "asterwise_get_char_dasha",
        "description": "Computes Char Dasha from birth data and returns sign lords as period rulers with ISO-dated Maha and Antar sequences plus karaka mappings.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises the chart before interpreting sign-based lords.\nAFTER: asterwise_get_dasha — optional Vimshottari cross-check for the same native.\n\nINPUT 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 other parameters follow the BirthData global contract.\n\nDO NOT CONFUSE WITH: asterwise_get_dasha — Vi"
      },
      {
        "name": "asterwise_get_yogini_dasha",
        "description": "Computes the eight-Yogini, 36-year Yogini Dasha cycle with two-level period trees and DD/MM/YYYY boundaries from birth data.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — establishes birth context for interpreting Yogini lords.\nAFTER: asterwise_get_dasha — optional Vimshottari comparison for the same native.\n\nINPUT 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 global contract.\n\nDO NOT CONFUSE WITH: asterwise_get_dasha — Vimshottari planet periods with data.per"
      },
      {
        "name": "asterwise_get_ashtottari_dasha",
        "description": "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.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — chart context before choosing between Ashtottari and Vimshottari.\nAFTER: asterwise_get_dasha — optional Vimshottari comparison.\n\nINPUT 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 periods are DD/MM/YYYY.\n\nDO NOT CONFUSE WITH: asterwise_get_dasha — standard 120-year Vimshottari with "
      },
      {
        "name": "asterwise_get_compatibility",
        "description": "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.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per person — understand charts before interpreting scores.\nAFTER: asterwise_get_papasamyam — optional malefic balance overlay.\n\nINPUT CONTRACT: Two BirthData objects follow the global contract (unknown midnight time accepted without flag). All scoring is computed upstream from those payloads.\n\nDO NOT CONFUSE WITH: asterwise_get_dashakoot — ten-point South Indian exte"
      },
      {
        "name": "asterwise_get_dashakoot",
        "description": "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.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart for each native — context before regional scoring.\nAFTER: asterwise_get_papasamyam — optional malefic differential.\n\nINPUT CONTRACT: Two BirthData objects per global contract.\n\nDO NOT CONFUSE WITH: asterwise_get_compatibility — North Indian 36-point Ashtakoota with different breakdown keys.\nasterwise_get_porutham — Tamil ten-porutham passed counts, not Dashakoot floats.\n"
      },
      {
        "name": "asterwise_get_papasamyam",
        "description": "Measures malefic stress from Lagna, Moon, and Venus references for each partner, compares totals, and labels compatibility level against a threshold.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_compatibility — establish baseline match quality.\nAFTER: None.\n\nINPUT CONTRACT: Two BirthData objects per global contract.\n\nDO NOT CONFUSE WITH: asterwise_get_doshas — twelve natal dosha buckets for one chart, not pairwise malefic balance.\nasterwise_get_compatibility — Guna Milan totals and vetoes, not Papa Samyam scoring.\n\nFull output and error contract: https://docs.asterwise.com/mcp/tools/get-papa"
      },
      {
        "name": "asterwise_get_porutham",
        "description": "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.\n\nWORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per native.\nAFTER: asterwise_get_thirumana_porutham — extended twelve-koota read if needed.\n\nINPUT CONTRACT: Two BirthData objects per global contract.\n\nDO NOT CONFUSE WITH: asterwise_get_thirumana_porutham — twelve poruthams including Nadi and Varna, not ten.\nasterwise_get_dashakoot — South Indian float scoring, not Tamil pass grid.\n\nFull output and error contract"
      }
    ],
    "profiled_at": "2026-09-25T04:00:46.254Z"
  },
  "unreachable": false,
  "payment_method": "oauth"
}