Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HinduCalendar — panchang, festivals & muhurta

REMOTE · HINDUCALENDAR.APP · SCANNED SEP 25

Daily panchang, festivals, muhurta and birth details, identical to the HinduCalendar Android app.

0 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3034 tokens (~606/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the HinduCalendar — panchang, festivals & muhurta MCP server?

HinduCalendar — panchang, festivals & muhurta is a hosted endpoint at https://hinducalendar.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · hinducalendar.app

# add to Claude Code
claude mcp add --transport http app-hinducalendar-hinducalendar 'https://hinducalendar.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "app-hinducalendar-hinducalendar": {
      "url": "https://hinducalendar.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-hinducalendar-hinducalendar": {
      "type": "http",
      "url": "https://hinducalendar.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.app-hinducalendar-hinducalendar]
url = "https://hinducalendar.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-hinducalendar-hinducalendar": {
      "type": "remote",
      "url": "https://hinducalendar.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-hinducalendar-hinducalendar --url 'https://hinducalendar.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-hinducalendar-hinducalendar:
    url: "https://hinducalendar.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-hinducalendar-hinducalendar": {
      "Transport": "http",
      "Url": "https://hinducalendar.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add app-hinducalendar-hinducalendar -t streamable-http -u 'https://hinducalendar.app/mcp'
// mcp.json
{
  "mcpServers": {
    "app-hinducalendar-hinducalendar": {
      "type": "http",
      "url": "https://hinducalendar.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Sept 26 0
    • Stability: 0.97 → pass security
  • 31 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_festival_dates” rewrote its description, which is the text the model reads security
    • Tool “get_muhurta” rewrote its description, which is the text the model reads security
    • Schema quality: 441 → 606 ▼ functional
    • New tool “get_muhurat_windows” functional
    • “get_muhurta” added an optional parameter “full_day” cosmetic
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://hinducalendar.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hinducalendar.app CN=WR3,O=Google Trust Services,C=US 1 Aug 2026 30 Oct 2026 RSA 2048 SHA256-RSA 1e86ae8c14fd44360a3b6ac26f990b09
SANs: hinducalendar.app, www.hinducalendar.app, kaalshodh.com, gol.kaalshodh.com, mandal.kaalshodh.com, kaalshodh.in
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of hinducalendar.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
hinducalendar.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31556926

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hinducalendar.app/mcp Verified 200
http (plaintext) http://hinducalendar.app/mcp HTTPS enforced 301 https://hinducalendar.app/mcp
MCP tools · 5 exposed · ~2,644 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_birth_details ~375

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).

NameTypeReqDescription
ayanamsastring––
latnumberyes–
lonnumberyes–
timestringyes–

No output schema declared.

No examples provided.

get_festival_dates ~653

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",…

NameTypeReqDescription
festival–––
latnumber––
lonnumber––
tz_offset_hoursnumber––
yearintegeryes–

No output schema declared.

No examples provided.

get_muhurat_windows ~619

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…

NameTypeReqDescription
category–––
langstring––
latnumber––
lonnumber––
month–––
muhurat–––
tz_offset_hoursnumber––
yearintegeryes–

No output schema declared.

No examples provided.

get_muhurta ~549

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.

NameTypeReqDescription
full_dayboolean––
langstring––
latnumberyes–
lonnumberyes–
timestringyes–

No output schema declared.

No examples provided.

get_panchang ~448

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".

NameTypeReqDescription
ayanamsastring––
datestringyes–
langstring––
latnumber––
lonnumber––
tzstring––

No output schema declared.

No examples provided.

Common questions

What is the HinduCalendar — panchang, festivals & muhurta MCP server?

HinduCalendar — panchang, festivals & muhurta is an MCP server listed in the public MCP registry as app.hinducalendar/hinducalendar. Daily panchang, festivals, muhurta and birth details, identical to the HinduCalendar Android app. This page covers its hosted endpoint (https://hinducalendar.app/mcp).

Is the HinduCalendar — panchang, festivals & muhurta MCP server safe to use?

HinduCalendar — panchang, festivals & muhurta scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the HinduCalendar — panchang, festivals & muhurta MCP server expose?

HinduCalendar — panchang, festivals & muhurta exposes 5 tools: get_panchang, get_festival_dates, get_muhurat_windows, get_birth_details, get_muhurta. Their descriptions and schemas cost roughly 2,644 tokens of context every time the server is loaded.

Does the HinduCalendar — panchang, festivals & muhurta MCP server require authentication?

No. We connected to HinduCalendar — panchang, festivals & muhurta without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the HinduCalendar — panchang, festivals & muhurta MCP server still maintained?

HinduCalendar — panchang, festivals & muhurta is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.