Kaalshodh — Indian astronomy time machine

Observatory-grade Indian astronomy, years -5000..+5000: positions, eclipses, panchang date search.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Observatory-grade Indian astronomy, years -5000..+5000: positions, eclipses, panchang date search.

    How to connect

    How to connect Kaalshodh — Indian astronomy time machine to Claude

    The server address to paste into Claude settings:

    https://kaalshodh.com/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect Kaalshodh — Indian astronomy time machine to ChatGPT

    The server address to paste into ChatGPT settings:

    https://kaalshodh.com/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect Kaalshodh — Indian astronomy time machine to Cursor

    The server address to paste into Cursor settings:

    https://kaalshodh.com/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (5)

    Raw names from tools/list. Only developers need these.

    get_astro_events Return precomputed astronomical events between start_date and end_date — any range within years -5000..+5000 (eclipses -1999..3000), instant. Events are global (location-independent) and served from binary-searched lookup tables — no live ephemeris computation. Example questions: "planetary events this month", "solar eclipses in the 12th century", "when was Shani retrograde in 1500 BCE?", "adhik maas years this decade". Ritu/ayana changes are Sayan sankrantis: Surya entering Meena=Vasanta, Vrishabha=Grishma, Karka=Varsha (=Dakshinayan start, = solstice), Kanya=Sharada, Vrishchika=Hemanta, Makara=Shishira (=Uttarayan start, = solstice) — query event_types=["sankranti"] with ayanamsa="Sayan". Args: start_date: Start date inclusive, YYYY-MM-DD (e.g. "2026-01-01"); negative years allowed (e.g. "-3101-01-01") end_date: End date inclusive, YYYY-MM-DD (e.g. "2026-12-31") ayanamsa: "Lahiri" (Vedic sidereal, default) or "Sayan" (tropical/Western) grah: Optional planet filter. One of: Surya, Chandra, Mangala, Budha, Guru, Shukra, Shani, Rahu, Ketu event_types: Optional list of event type filters. Valid values: "transit" – Mangala..Ketu change rashi (NOT Surya/Chandra) "sankranti" – Surya changes rashi (~monthly) "moon_transit" – Chandra changes rashi (~monthly) "full_moon" – Purnima (Moon at 180° elongation) "new_moon" – Amavasya (Moon at 0° elongation) "retrograde_start" – planet turns retrograde "retrograde_end" – planet resumes direct motion "equinox" – Vernal or Autumnal equinox (Sayan Surya) "solstice" – Summer or Winter solstice (Sayan Surya) "asta_start" – planet enters c
    get_nearest_event Return the nearest occurrence of one event type before or after a date — walks outward from any date in years -5000..+5000, instant. Ideal for questions like "when is the next Kumbh Mela?", "when does Guru go retrograde next?", "when is Makara Sankranti?" or "when was the last total solar eclipse before 1500 CE?" without scanning a whole range. Args: event_type: One of the values listed in get_astro_events (e.g. "kumbh_mela", "solar_eclipse", "adhik_maas", "sankranti"). from_date: Reference date, YYYY-MM-DD (BC years like "-0500-01-01" allowed). direction: "next" (first after from_date) or "prev" (last before). ayanamsa: "Lahiri" (default) or "Sayan". grah: Optional grah filter for grah-specific event types. location: Optional Kumbh Mela location (Haridwar/Prayagraj/Ujjain/Nashik). Returns: Dict with event_type, direction, from_date, ayanamsa, valid_range, and `event` (null if the reference date is outside the data range).
    get_planetary_positions Return the rashi (zodiac sign) and retrograde status of the 9 grahas at any instant in years -5000..+5000, plus the paksha (lunar fortnight). Served from precomputed lookup tables — O(log n), instant even for "where was Shani on this day in 3102 BCE?". Example questions: "which planets are retrograde right now?", "what sign was Guru in when I was born?", "sky snapshot for 500 CE". Args: time: ISO 8601 UTC datetime (e.g. "2026-03-22T12:00:00Z"). Negative years allowed (e.g. "-3101-02-18T00:00:00Z"). Defaults to now. ayanamsa: "Lahiri" (Vedic sidereal, default) or "Sayan" (tropical). grah: Optional single planet (Surya, Chandra, Mangala, Budha, Guru, Shukra, Shani, Rahu, Ketu) — returns just that one. Returns: Dict with time, ayanamsa, paksha (Shukla/Krishna), and grahas mapping each planet to its rashi name and retrograde status (or the single grah's status when `grah` is given).
    find_matching_dates Search up to 10,000 years (-5000..+5000) for every date whose sunrise panchang matches the given constraints — instant, from precomputed tables. This answers questions no LLM can: dating inscriptions and historical events, Hindu→Gregorian conversion, recurrence questions. Example questions: - "An inscription says Kartika Shukla 5, Thursday, in the 1200s CE — which dates fit?" → masa=Kartika, paksha=Shukla, tithi=5, vaar=Thursday, range 1200..1300. - "Convert Vikram Samvat 1680 Kartik Shukla 5 to a Gregorian date" → same constraints over the matching Gregorian years (VS ≈ year+57); check vikram_samvat in the results. - "When does my janma-tithi (Shravana Krishna Ashtami) fall in 2027?" - "Which years this century does Diwali (Kartika Amavasya) fall on a Sunday?" - "Full moon in Chitra nakshatra in the 5th century BCE" → tithi=Purnima, nakshatra=Chitra, range -0500..-0400. Give at least one of tithi/nakshatra/masa. All names fuzzy-match ("Ekadashi", "ekadasi", or the number 11 all work). Args: start_date, end_date: YYYY-MM-DD; negative years allowed ("-0500-01-01"). Wide ranges are fine — results are capped. tithi: Name or number 1..30 (1..15 Shukla, 16..30 Krishna; Purnima=15, Amavasya=30). A bare name like "Ekadashi" matches both pakshas unless paksha is given. paksha: "Shukla" (waxing) or "Krishna" (waning). nakshatra: Name or number 1..27 (Ashwini=1 .. Revati=27). This is the MOON's nakshatra at sunrise. masa: Amavasyant Hindu month name or number 1..12 (Chaitra=1 .. Phalguna=12). vaar: Weekday — English ("Thursday") or Vedic ("Guruvara"). tz_offset_hours: Local offset for civil-day assignment (default 5.5 = India). max_results: Cap (≤200); response flags truncation. Returns ma
    find_copresence Find every window when the given planets occupy the same rashi (sign) simultaneously — conjunction-class questions over ±5000 years, instant. Example questions: "when are Guru and Shani next together in Kumbha?" (the ~60-year social-cycle conjunction), "when were Guru, Shani and Mangala last in one sign?", "were all planets really in one rashi at the Kali Yuga epoch (Feb 3102 BCE)?", "great conjunctions in the 1st millennium". Resolution is the rashi (30°) — for exact-degree conjunctions treat these windows as candidates. Including Chandra gives many short (~2 day) windows; omit it for long-period questions. Args: grahas: Two or more of: Surya, Chandra, Mangala, Budha, Guru, Shukra, Shani, Rahu, Ketu. start_date, end_date: YYYY-MM-DD, negative years allowed. rashi: Optional sign filter — Vedic (Mesh..Meen) or western (Aries..Pisces) name, or 1..12. Omit = any shared sign. ayanamsa: "Lahiri" (default) or "Sayan". max_results: Cap (≤100); response flags truncation.