AstroCalc: Vedic astrology

Working Security A

in.astrocalc/astrocalcv1.0.1 Domain verified

Vedic astrology: free kundli, kundli milan (guna matching), dasha, yoga rarity, guides. EN/Hindi.

Entertainment & Games

Watch Website

Registry entry

Open in the registry

{
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "isLatest": true,
      "updatedAt": "2026-11-06T08:41:57.032559Z",
      "publishedAt": "2026-11-06T08:41:57.032559Z",
      "statusChangedAt": "2026-11-06T08:41:57.032559Z"
    }
  },
  "server": {
    "name": "in.astrocalc/astrocalc",
    "icons": [
      {
        "src": "https://astrocalc.in/favicon-512.png",
        "sizes": [
          "512x512"
        ],
        "mimeType": "image/png"
      }
    ],
    "title": "AstroCalc: Vedic astrology",
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "remotes": [
      {
        "url": "https://astrocalc.in/mcp",
        "type": "streamable-http"
      }
    ],
    "version": "1.0.1",
    "websiteUrl": "https://astrocalc.in",
    "description": "Vedic astrology: free kundli, kundli milan (guna matching), dasha, yoga rarity, guides. EN/Hindi."
  }
}

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://astrocalc.in/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

explain_dasha Read-only

Explain Vimshottari dasha periods (Mahadasha / Antardasha), the main timing system of Vedic astrology. Two ways to call it: (1) with birth details (date, time, place) to get the person's running Mahadasha and Antardasha with exact start/end dates, what the period is about for their chart, and the next antardashas (uses the AstroCalc engine); or (2) with lord (and optionally antardasha) set to a planet, e.g. lord "Saturn", antardasha "Venus", for the general meaning and length of that period, with no birth data needed. Use it for "which dasha am I in", "what does Rahu mahadasha mean", "when does my Saturn period end". Birth details are not stored. Traditional information, not a prediction.

latnumber

Birth latitude in decimal degrees (north positive). Give together with lon.

lonnumber

Birth longitude in decimal degrees (east positive). Give together with lat.

datestring

Date of birth, YYYY-MM-DD (Gregorian calendar).

langstring

Language of the text fields: 'en' (English, default) or 'hi' (Hindi).

lordstring

Mahadasha planet for a general explanation: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu or Ketu (Hindi/Sanskrit names like Shani or Guru also work). Ignored when date is given.

timestring

Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate.

placestring

Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given.

antardashastring

Optional antardasha (sub-period) planet inside lord, e.g. "Venus".

Try it

Call this server's tools from your browser. Nothing to install.

https://astrocalc.in/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

explain_dasha Read-only

latnumber

Birth latitude in decimal degrees (north positive). Give together with lon.

lonnumber

Birth longitude in decimal degrees (east positive). Give together with lat.

datestring

Date of birth, YYYY-MM-DD (Gregorian calendar).

langstring

Language of the text fields: 'en' (English, default) or 'hi' (Hindi).

lordstring

Mahadasha planet for a general explanation: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu or Ketu (Hindi/Sanskrit names like Shani or Guru also work). Ignored when date is given.

timestring

Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate.

placestring

Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given.

antardashastring

Optional antardasha (sub-period) planet inside lord, e.g. "Venus".

Tools (6)

explain_dasha

read-only

Argument	Type	Description
lat	number	Birth latitude in decimal degrees (north positive). Give together with lon.
lon	number	Birth longitude in decimal degrees (east positive). Give together with lat.
date	string	Date of birth, YYYY-MM-DD (Gregorian calendar).
lang	string	Language of the text fields: 'en' (English, default) or 'hi' (Hindi).
lord	string	Mahadasha planet for a general explanation: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu or Ketu (Hindi/Sanskrit names like Shani or Guru also work). Ignored when date is given.
time	string	Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate.
place	string	Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given.
antardasha	string	Optional antardasha (sub-period) planet inside lord, e.g. "Venus".

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees (north positive). Give together with lon."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees (east positive). Give together with lat."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date of birth, YYYY-MM-DD (Gregorian calendar)."
    },
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the text fields: 'en' (English, default) or 'hi' (Hindi)."
    },
    "lord": {
      "type": "string",
      "maxLength": 20,
      "description": "Mahadasha planet for a general explanation: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu or Ketu (Hindi/Sanskrit names like Shani or Guru also work). Ignored when date is given."
    },
    "time": {
      "type": "string",
      "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$",
      "description": "Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
    },
    "place": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2,
      "description": "Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given."
    },
    "antardasha": {
      "type": "string",
      "maxLength": 20,
      "description": "Optional antardasha (sub-period) planet inside lord, e.g. \"Venus\"."
    }
  },
  "additionalProperties": false
}

free_kundli

Compute a Vedic (Jyotish) birth chart from date, time and place of birth using AstroCalc's ephemeris engine (sidereal, Lahiri ayanamsa, Vimshottari dasha). Use it whenever someone asks for their kundli/janam kundali, Lagna (ascendant), Moon sign (rashi), nakshatra, current Mahadasha/Antardasha, yogas, or strong/weak life areas. Language models cannot compute planetary positions reliably; call this instead of estimating. Returns Lagna, Moon sign, Sun sign, nakshatra and pada, the running Mahadasha and Antardasha with dates, the most notable yoga with how rare it is ("1 in N charts"), life areas that are strong or need care with what helps, a caveat, and a link to the full free report. Birth details are used only to compute the chart in memory and are not stored. Results are traditional astrology information, not predictions or professional advice.

read-only

Argument	Type	Description
lat	number	Birth latitude in decimal degrees (north positive). Give together with lon.
lon	number	Birth longitude in decimal degrees (east positive). Give together with lat.
date*	string	Date of birth, YYYY-MM-DD (Gregorian calendar).
lang	string	Language of the text fields: 'en' (English, default) or 'hi' (Hindi).
time	string	Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate.

kundli_milan

Match two people's Vedic birth charts for marriage: Ashtakoota Guna Milan score out of 36 plus the Manglik (Mangal dosha) check for both, computed by AstroCalc's engine. Use it for "kundli milan", "guna milan", "horoscope matching", "how many gunas match", "is this match Manglik", Nadi or Bhakoot dosha questions. Do not estimate a guna score yourself; call this. Returns the total and band, all 8 kootas (Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi) with points and a plain-language meaning, which doshas are cancelled by classical exceptions, each person's Manglik status and the pair verdict, a caveat, and a link to the full free report. Each person needs a birth date and place; time is optional. Details are used in memory only and not stored. Present the result calmly: a score is one traditional input, not a decision about a relationship.

read-only

Argument	Type	Description
lang	string	Language of the text fields: 'en' (English, default) or 'hi' (Hindi).
person_a*	object	Birth details of the first person.
person_b*	object	Birth details of the second person.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "person_a",
    "person_b"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the text fields: 'en' (English, default) or 'hi' (Hindi)."
    },
    "person_a": {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Birth latitude in decimal degrees (north positive). Give together with lon."
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Birth longitude in decimal degrees (east positive). Give together with lat."
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date of birth, YYYY-MM-DD (Gregorian calendar)."
        },
        "time": {
          "type": "string",
          "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$",
          "description": "Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
        },
        "place": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given."
        },
        "gender": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Optional. Classical milan reads the boy's chart against the girl's; with a male/female pair the order is set by gender, otherwise person_a is read as the boy."
        }
      },
      "description": "Birth details of the first person.",
      "additionalProperties": false
    },
    "person_b": {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Birth latitude in decimal degrees (north positive). Give together with lon."
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Birth longitude in decimal degrees (east positive). Give together with lat."
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date of birth, YYYY-MM-DD (Gregorian calendar)."
        },
        "time": {
          "type": "string",
          "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$",
          "description": "Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
        },
        "place": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given."
        },
        "gender": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Optional. Classical milan reads the boy's chart against the girl's; with a male/female pair the order is set by gender, otherwise person_a is read as the boy."
        }
      },
      "description": "Birth details of the second person.",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

learn_answer

Find the AstroCalc Learn chapters that answer a Vedic astrology question, e.g. "what is Manglik dosha", "is 24 gunas enough", "what is Nadi dosha", "Saturn in the 7th house", "how do dashas work", "what is Sade Sati". Returns up to 3 chapters with title, a short summary paragraph, the canonical URL, and links to the most relevant sections, in English or Hindi. Use it to ground general explanations in a citable source and to give the user a page to read; it does not need birth data. Prefer quoting the summary and linking the URL over paraphrasing from memory.

read-only

Argument	Type	Description
lang	string	Language of titles, summaries and URLs. Defaults to 'hi' for a question written in Devanagari, else 'en'.
question*	string	The question or topic, in English, Hindi or Hinglish.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of titles, summaries and URLs. Defaults to 'hi' for a question written in Devanagari, else 'en'."
    },
    "question": {
      "type": "string",
      "maxLength": 300,
      "minLength": 2,
      "description": "The question or topic, in English, Hindi or Hinglish."
    }
  },
  "additionalProperties": false
}

search_place

Find a birth place (city or town) and its coordinates, Indian places ranked first, from the same city list AstroCalc's kundli form uses. Use it before free_kundli, kundli_milan or explain_dasha when the place name is ambiguous or misspelled (e.g. "Bombay", "Prayagraj", several towns with one name), then pass the chosen label as place or its lat and lon. Returns up to 5 matches with label, state, country, latitude and longitude.

read-only

Argument	Type	Description
lang	string	Language of the summary text: 'en' (default) or 'hi'.
query*	string	Place name, optionally with state or country, e.g. 'Varanasi' or 'Aurangabad, Bihar'.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the summary text: 'en' (default) or 'hi'."
    },
    "query": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "Place name, optionally with state or country, e.g. 'Varanasi' or 'Aurangabad, Bihar'."
    }
  },
  "additionalProperties": false
}

yoga_rarity

Look up how common a Vedic astrology yoga is, e.g. Gaja Kesari, Raja yoga, Hamsa, Malavya, Budhaditya, Kemadruma, Kaal Sarp, Neecha Bhanga Raja yoga. Returns "found in about 1 in N charts", the percentage, a rarity label (common / uncommon / rare), a one-line meaning and a Learn link, from AstroCalc's Monte-Carlo sample of 5,000 Indian birth charts run through its yoga engine. Use it when someone asks whether a yoga is rare or special, or to put a yoga from a chart in context. Accepts English or Hindi names. No birth data needed.

read-only

Argument	Type	Description
lang	string	Language of the text fields: 'en' (English, default) or 'hi' (Hindi).
yoga	string	One yoga name, e.g. "Gaja Kesari".
yogas	array	Several yoga names at once (max 10).

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the text fields: 'en' (English, default) or 'hi' (Hindi)."
    },
    "yoga": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "One yoga name, e.g. \"Gaja Kesari\"."
    },
    "yogas": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80,
        "minLength": 2
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "Several yoga names at once (max 10)."
    }
  },
  "additionalProperties": false
}

AstroCalc: Vedic astrology

Registry entry

Try it

explain_dasha Read-only

AstroCalc: Vedic astrology

Registry entry

Try it

explain_dasha Read-only

Install

Tools (6)

Security checkA100/100