Skip to content

Kaalshodh — Indian astronomy time machine MCP server

com.kaalshodh/kaalshodhkaalshodh.comstreamable-httpv1.0.0Scanned

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

5 tools: 5 only read.

Tools: 0 delete, 0 irreversible, 0 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Kaalshodh — Indian astronomy time machine MCP server can do

The Kaalshodh — Indian astronomy time machine MCP server is published by kaalshodh.com, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Only reads 5Show 5 read-only tools
  • find_copresenceFind every window when the given planets occupy the same rashi (sign) simultaneously — conjunction-class questions over ±5000 years, instant.No findings

    Why it is in this group

    • The name "find_copresence" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Find planetary copresence
  • find_matching_datesSearch up to 10,000 years (-5000..+5000) for every date whose sunrise panchang matches the given constraints — instant, from precomputed tables.1 finding

    Why it is in this group

    • The name "find_matching_dates" says "find": a word for reading.

    Findings

    • Info

      The description is 2,322 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...tched date, certify it with the HinduCalendar MCP server's get_panchang."

      What this check looks for
    Description, as the server wrote it
    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 matched dates each with its full sunrise panchang (tithi, nakshatra, masa with adhik flag, vikram samvat, weekday). Ayanamsa is Lahiri. Dates are proleptic Gregorian, astronomical year numbering. For an app-exact panchang of any matched date, certify it with the HinduCalendar MCP server's get_panchang.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Search dates by panchang
  • get_astro_eventsReturn precomputed astronomical events between start_date and end_date — any range within years -5000..+5000 (eclipses -1999..3000), instant.1 finding

    Why it is in this group

    • The name "get_astro_events" says "get": a word for reading.

    Findings

    • Info

      The description is 3,008 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...o, and (for intervals) end_time, duration_days, plus a details dict."

      What this check looks for
    Description, as the server wrote it
    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 combust zone (Grah Asta) "asta_end" – planet exits combust zone (Uday) "solar_eclipse" – solar eclipse (catalog, years -1999..3000) "lunar_eclipse" – lunar eclipse (catalog, years -1999..3000) "kaal_sarp" – Kaal Sarp window (interval) "adhik_maas" – intercalary Hindu month (interval) "kshay_maas" – lost Hindu month (interval) "kumbh_mela" – Kumbh Mela window (interval) The max range is set by the densest requested type: 3 years by default, up to 1000 years for sparse-only queries (kumbh, maas). Interval events also carry end_time, duration_days, and type-specific details. Returns: Dict with keys: start_date, end_date, ayanamsa, count, events (list). Each event has: time (UTC ISO), event_type, grah, from, to, and (for intervals) end_time, duration_days, plus a details dict.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Find astronomical events
  • get_nearest_eventReturn the nearest occurrence of one event type before or after a date — walks outward from any date in years -5000..+5000, instant.No findings

    Why it is in this group

    • The name "get_nearest_event" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Nearest event occurrence
  • get_planetary_positionsReturn the rashi (zodiac sign) and retrograde status of the 9 grahas at any instant in years -5000..+5000, plus the paksha (lunar fortnight).No findings

    Why it is in this group

    • The name "get_planetary_positions" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Planetary positions

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

2 info
  • The description is 3,008 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...o, and (for intervals) end_time, duration_days, plus a details dict."

    What this check looks for
  • The description is 2,322 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...tched date, certify it with the HinduCalendar MCP server's get_panchang."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http kaalshodh https://kaalshodh.com/mcp
claude mcp add --transport http kaalshodh https://kaalshodh.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__kaalshodh__get_astro_events",
      "mcp__kaalshodh__get_nearest_event",
      "mcp__kaalshodh__get_planetary_positions",
      "mcp__kaalshodh__find_matching_dates",
      "mcp__kaalshodh__find_copresence"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kaalshodh. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.kaalshodh/kaalshodh/verify?hash=faf03b2c6c44073991f815f456c571388327e506b739a26e3843a3dd544aba4d" | jq -e '.changed == false'

Pinned hash faf03b2c6c44, from Nov 13, 2026, 14:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.kaalshodh/kaalshodh/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.kaalshodh/kaalshodh
[![Anlyon Radar](https://radar.anlyon.com/badge/com.kaalshodh/kaalshodh.svg)](https://radar.anlyon.com/servers/com.kaalshodh/kaalshodh)

Source: MCP Registry. Synced Oct 21, 2026, 17:57 UTC.

Kaalshodh — Indian astronomy time machine MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Kaalshodh — Indian astronomy time machine MCP server safe?

No scan can promise that. What its definitions show: 5 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Kaalshodh — Indian astronomy time machine MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Kaalshodh — Indian astronomy time machine MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Kaalshodh — Indian astronomy time machine MCP server have?

5 tools: 5 read. get_astro_events, get_nearest_event, get_planetary_positions, find_matching_dates and find_copresence.

Does the Kaalshodh — Indian astronomy time machine MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Kaalshodh — Indian astronomy time machine MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Kaalshodh — Indian astronomy time machine MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.