Kundlit Vedic Astrology
v1.5.0Free Vedic astrology: panchang, kundali, transits, matching, doshas, eclipses, numerology
Endpoint health
online- Last checked
- 11/20/2026, 7:16:20 AM
- Latency
- 74 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.kundlit%2Fastro
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.kundlit/astro": {
"url": "https://kundlit.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
17 shown · authentication unknown
Kaal Sarp dosha check
check_kaal_sarp
Returns a yes/no Kaal Sarp dosha verdict for ONE birth chart -- the condition where the seven classical grahas all fall on one side of the Rahu-Ketu axis -- plus which of the twelve named types it is (Anant, Kulik, Vasuki, Shankhpal and the rest), whether the hemming is full or partial, the houses involved, and a plain explanation of the finding. Use this for 'do I have kaal sarp dosh' questions. It is a different dosha from the Mars one (check_manglik) and from marriage-pair doshas (get_kundli_match); ask for each separately. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa); no writes, no auth, at least 30 requests/min/IP per server instance, plus a shared engine budget of at least 60/min/IP across all engine-backed tools. Needs an exact birth time -- partial hemming can flip with a few minutes' error.
Schema valid · SHA-256 b16d3d795933…
View input schema
{ "type": "object", "properties": { "birth_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Birth date in the Gregorian calendar as YYYY-MM-DD, e.g. 1992-03-14. Years 1200-2400 only, and it must be a real calendar date (2023-02-29 is rejected)." }, "birth_time": { "type": "string", "pattern": "^\\d{2}:\\d{2}$", "description": "Birth time on the local clock at the birth place, HH:MM in 24-hour format (00:00-23:59), e.g. 06:45 or 18:20. Not UTC. Required and not defaulted: the ascendant moves about one degree every four minutes, so a guessed time gives a guessed chart." }, "place": { "description": "Place as free text, \"City, State, Country\" -- e.g. \"Jaipur, Rajasthan, India\". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead.", "type": "string", "minLength": 1, "maxLength": 160 }, "latitude": { "description": "Latitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too.", "type": "number", "minimum": -90, "maximum": 90 }, "longitude": { "description": "Longitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted.", "type": "number", "minimum": -180, "maximum": 180 }, "timezone": { "description": "IANA timezone name, e.g. \"Asia/Kolkata\" or \"America/New_York\" (never an offset like \"+05:30\"). Required when latitude/longitude are used; ignored when `place` is given.", "type": "string", "minLength": 1, "maxLength": 64 } }, "required": [ "birth_date", "birth_time" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://kundlit.com/api/mcp