HinduCalendar — panchang, festivals & muhurta MCP server
app.hinducalendar/hinducalendarhinducalendar.appstreamable-httpv1.1.0Scanned
Daily panchang, festivals, muhurta and birth details, identical to the HinduCalendar Android app.
5 tools: 5 only read.
- Reads private data · 1
- 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.
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 HinduCalendar — panchang, festivals & muhurta MCP server can do
The HinduCalendar — panchang, festivals & muhurta MCP server is published by hinducalendar.app, 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.
1 tool reads private data (get_muhurta).
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 12, 2026, version 1.1.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
get_birth_detailsReturn birth star (nakshatra), birth name syllable (naam akshar / pada), Chandra rashi (Moon sign), and Lagna rashi (ascendant sign) for a child born at the given time and location…No findings
Why it is in this group
- The name "get_birth_details" says "get": a word for reading.
Description, as the server wrote it Return birth star (nakshatra), birth name syllable (naam akshar / pada), Chandra rashi (Moon sign), and Lagna rashi (ascendant sign) for a child born at the given time and location — all from the app's own engine, so they match the HinduCalendar app's kundali exactly. Args: time: ISO 8601 datetime of birth (e.g. "2025-08-15T10:30:00Z"). Include timezone offset if known (e.g. "2025-08-15T10:30:00+05:30"). lat: Latitude of birth place in decimal degrees (e.g. 28.6139 for Delhi). lon: Longitude of birth place in decimal degrees (e.g. 77.2090 for Delhi). ayanamsa: "Lahiri" (Vedic sidereal, default) or "Sayan" (tropical). Returns: Dict with: - time (ISO) - ayanamsa - nakshatra: { index (1–27), name } - pada: { index (1–4), overall_index (1–108), naam_akshar (birth name syllable) } - chandra_rashi: { index (1–12), name } ← Moon sign - lagna_rashi: { index (1–12), name } ← Ascendant sign Plus a rendered South Indian kundali chart (PNG image).
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
- title: Birth details & kundali
get_festival_datesExact dates of major Hindu festivals for any year, computed live by the same engine the HinduCalendar app uses — never guess a festival date, always use this.1 finding
Why it is in this group
- The name "get_festival_dates" says "get": a word for reading.
Findings
- Info
The description is 2,301 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ft by location; for a user's city pass their coordinates."
Description, as the server wrote it Exact dates of major Hindu festivals for any year, computed live by the same engine the HinduCalendar app uses — never guess a festival date, always use this. Covers the tithi-anchored festivals (Diwali, Holi, Krishna Janmashtami, Ganesh Chaturthi, Rama Navami, Maha Shivaratri, Raksha Bandhan, Dhanteras, Karva Chauth, Chhath, Vasant Panchami, Gudi Padwa, Akshaya Tritiya, the purnimas, Navratri from Ghatasthapana through Vijayadashami) *and* the ones no tithi rule can express: solar ingresses (Makar Sankranti — also Pongal, Uttarayan, Maghi; Mesha Sankranti — also Vishu, Baisakhi, Puthandu), nakshatra-dated observances (Onam, the Jyeshtha Gauri triad), weekday series (Shravan Somwar, Mangala Gauri), and the Puri Jagannath sequence (Snana Yatra, Rath Yatra, Hera Panchami, Bahuda Yatra, Suna Besha, Niladri Bije). Every result carries `date` and a plain-language `rule` saying how that date is fixed, usually with a `why` explaining it, plus regions, traditions, cluster and related festivals where they are recorded. Tithi-anchored festivals also carry `masa`/`paksha`/`tithi`; solar and nakshatra ones do not, because they have none. Two results are not single days: • one that recurs within the year (Shravan Somwar is four or five Mondays) carries `dates` with every occurrence — `date` is the first; • a multi-day observance (Ganeshotsav, Navratri) carries `end_date` and `days`. Example questions: "when is Diwali in 2027?", "what date was Holi in 1962?", "list all festivals in 2026", "when is Onam?", "which Mondays are Shravan Somwar this year?". Args: year: Gregorian year. festival: Optional name filter — fuzzy, and matches popular and regional aliases plus Devanagari ("Diwali", "Dussehra", "Rakhi", "Pongal", "Vishu", "दिवाली"). A sequence name ("Navratri", "Ganeshotsav", "Rath Yatra") returns every festival in that sequence. lat, lon, tz_offset_hours: Location (default Ujjain, the canonical reference). Festival days can shift by location; for a user's city pass their coordinates.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
- title: Festival dates
get_muhurat_windowsDated windows of the auspicious muhurta yogas and the observance periods — the "when are the vivah muhurats in 2026?" and "when is Chaturmas?" family.1 finding
Why it is in this group
- The name "get_muhurat_windows" says "get": a word for reading.
Findings
- Info
The description is 2,098 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...th location. lang: Language for names — "en" (default) or "hi"."
Description, as the server wrote it Dated windows of the auspicious muhurta yogas and the observance periods — the "when are the vivah muhurats in 2026?" and "when is Chaturmas?" family. Computed live by panchang-core's MuhurtaFinder, the same engine behind the app's Muhurta Finder and the hinducalendar.app muhurat pages. Twenty presets in two categories: • yoga — Sarvarth Siddhi, Amrit Siddhi, Guru Pushya, Ravi Pushya, Ravi, Dwipushkar, Tripushkar, Siddha, Amrita, Vivaah Muhurat. Intra-day windows, often several a week. • period — Chaitra / Sharad / Gupta Navratri (Ashadha and Magha), Chaturmas, Pitru Paksha, Holashtak, Panchak, Gand Mool, Kharmas. Multi-day observances and blackout spans. Each window has a `start` and `end` in ISO 8601 carrying the requested place's UTC offset ("2026-01-14T15:05:00+05:30"), so they read directly as the local time the muhurat is kept by. Asking for everything in a year matches ~600 windows, so an unnarrowed request answers with per-preset counts and says so (`windows_omitted`). Name a muhurat or pass a month to get the actual times — a single named muhurat always returns its windows in full. Example questions: "vivah muhurat dates in 2026", "when is Pitru Paksha this year?", "Sarvarth Siddhi yoga in November 2026", "when does Chaturmas start?", "list the Panchak periods in 2027", "is there a Guru Pushya yoga next month?". Args: year: Gregorian year. muhurat: Optional name filter — fuzzy, matches slug, English and Hindi names ("vivaah", "sarvarth siddhi", "गुरु पुष्य"). category: Optional — "yoga" or "period". month: Optional 1..12, to narrow within the year. lat, lon, tz_offset_hours: Location (default Ujjain, the canonical reference). These windows are rise/set and panchang dependent, so they do shift with location. lang: Language for names — "en" (default) or "hi".
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
- title: Muhurat windows
get_muhurtaMuhurta for a moment and place, exactly as the HinduCalendar app computes it — and, with full_day=True, the whole day's grid.Reads private dataNo findings
Why it is in this group
- The name "get_muhurta" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "calendar": it reads calendars.
Description, as the server wrote it Muhurta for a moment and place, exactly as the HinduCalendar app computes it — and, with full_day=True, the whole day's grid. By default returns only what is ACTIVE at the instant given: - Current lagna (ascendant sign active at that moment) - Current choghadiya (day or night slot) - Current hora (planetary hour) - Any ongoing special muhurtas (Rahu Kalam, Yama Ghanta, Guli Kalam, Abhijit, Dur Muhurt, Pradosh, Varjyam, Panchak, Gandmool) Set full_day=True to also get every window of the panchang day (sunrise to next sunrise) containing that instant — the complete choghadiya and hora grids (day and night), all lagna periods, and every special muhurta with its start and end. Use it for "when is Rahu Kalam today?", "list today's choghadiya", "when is Abhijit muhurat?" — questions the instant-only view cannot answer without guessing the time. Sunrise/sunset, lagna transitions and every special muhurta come from panchang-core (the app's engine); choghadiya/hora are pure rise/set arithmetic driven by the engine's times and weekday. For multi-day observance periods and auspicious-yoga windows (Vivaah muhurat, Sarvarth Siddhi, Pitru Paksha, Chaturmas, Panchak…) use get_muhurat_windows instead — this tool covers a single day. Args: time: ISO 8601 datetime (e.g. "2025-08-15T10:30:00+05:30"). If no timezone is given, UTC is assumed. lat: Latitude in decimal degrees. lon: Longitude in decimal degrees. lang: Language for names — "en" (default) or "hi". full_day: Include the whole day's grids, not just what is active now. Returns: Dict with sunrise, sunset, current_lagna, current_choghadiya, current_hora, and ongoing_muhurtas — plus choghadiya, hora, lagna and muhurtas when full_day is set.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
- title: Muhurta timings
get_panchangFull daily panchang for a date and place — computed by the same panchang-core engine the HinduCalendar Android app ships, so the values are identical to the app (not an approximati…No findings
Why it is in this group
- The name "get_panchang" says "get": a word for reading.
Description, as the server wrote it Full daily panchang for a date and place — computed by the same panchang-core engine the HinduCalendar Android app ships, so the values are identical to the app (not an approximation). Returns the five limbs at sunrise (tithi, nakshatra, yoga, karana, vaar) each with its END TIME, paksha, lunar month in both amavasyant and purnimant conventions (with adhik maas flag), Vikram/Shaka/Kali/Gujarati samvat years, samvatsara names, ritu (season), ayana (Uttarayan/ Dakshinayan), sun/moon rashi with next-transit time, and sunrise/sunset/ moonrise/moonset. This is also the Gregorian→Hindu date converter: the masa + paksha + tithi + samvat fields ARE the Hindu date. (For Hindu→Gregorian, use the Kaalshodh MCP server's find_matching_dates.) Example questions: "what is the tithi today in Delhi?", "when does Ekadashi end tomorrow?", "what is today's date in Vikram Samvat?", "which Hindu month is it?". Args: date: Gregorian date, YYYY-MM-DD. Default location is Ujjain; pass lat/lon/tz for other places. lat, lon: Location in decimal degrees. tz: IANA timezone name ("Asia/Kolkata") or a numeric UTC offset in hours ("5.5"). ayanamsa: "Lahiri" (default) or "Sayan". lang: Language for names — "en", "hi", and the app languages (mr, gu, bn, ta, te, kn, ml, sa) plus "en-iast".
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
- title: Daily panchang
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 untrusted-input or outbound.
- Reads private data1
- 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.
Looked at Nov 20, 2026, 18:29 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.
The description is 2,301 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ft by location; for a user's city pass their coordinates."
The description is 2,098 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...th location. lang: Language for names — "en" (default) or "hi"."
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.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hinducalendar https://hinducalendar.app/mcpclaude mcp add --transport http hinducalendar https://hinducalendar.app/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__hinducalendar__get_panchang",
"mcp__hinducalendar__get_festival_dates",
"mcp__hinducalendar__get_muhurat_windows",
"mcp__hinducalendar__get_birth_details",
"mcp__hinducalendar__get_muhurta"
],
"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 hinducalendar. Review it before you use it.
Capability tags behind 1 rule
- mcp__hinducalendar__get_muhurta private-data
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/app.hinducalendar/hinducalendar/verify?hash=2ee5e0e44f23ca8b2bf79d91e417ae8f39048b60045f590636d65c64c55e85d7" | jq -e '.changed == false'Pinned hash 2ee5e0e44f23, from Nov 12, 2026, 01:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.hinducalendar/hinducalendar/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.hinducalendar/hinducalendar)Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.
HinduCalendar — panchang, festivals & muhurta MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the HinduCalendar — panchang, festivals & muhurta 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 HinduCalendar — panchang, festivals & muhurta MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the HinduCalendar — panchang, festivals & muhurta 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 HinduCalendar — panchang, festivals & muhurta MCP server have?
- 5 tools: 5 read. get_panchang, get_festival_dates, get_muhurat_windows, get_birth_details and get_muhurta.
Does the HinduCalendar — panchang, festivals & muhurta MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the HinduCalendar — panchang, festivals & muhurta MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the HinduCalendar — panchang, festivals & muhurta MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.