HinduCalendar — panchang, festivals & muhurta
REMOTE · HINDUCALENDAR.APP · SCANNED AUG 3
Daily panchang, festivals, muhurta and birth details, identical to the HinduCalendar Android app.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1767 tokens (~441/item across 4 items; 4 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · hinducalendar.app
claude mcp add --transport http app-hinducalendar-hinducalendar https://hinducalendar.app/mcp
[mcp_servers.app-hinducalendar-hinducalendar] url = "https://hinducalendar.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-hinducalendar-hinducalendar": {
"type": "remote",
"url": "https://hinducalendar.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-hinducalendar-hinducalendar --url https://hinducalendar.app/mcp --transport streamable-http
mcp_servers:
app-hinducalendar-hinducalendar:
url: "https://hinducalendar.app/mcp" {
"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.
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.
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Aug 26 58
First indexed and scored.
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 3 Aug 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 |
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 |
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 |
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.
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | — |
| lat | number | yes | — |
| lon | number | yes | — |
| time | string | yes | — |
No output schema declared.
No examples provided.
get_festival_dates ~315
Exact dates of major Hindu festivals for any year, computed live from the tithi rules by the same engine the HinduCalendar app uses — never guess a festival date, always use this. Covers: Diwali (Deepavali), Holi, Navaratri endpoints (Mahanavami, Vijayadashami), Krishna Janmashtami, Ganesh Chaturthi, Rama Navami, Maha Shivaratri, Raksha Bandhan, Dhanteras, Chhath, Vasant Panchami, Gudi Padwa, Akshaya Tritiya, Buddha Purnima, Guru Purnima, and more. Each result carries its panchang rule (masa + paksha + tithi). Example questions: "when is Diwali in 2027?", "what date was Holi in 1962?", "list all festivals in 2026". Args: year: Gregorian year. festival: Optional name filter (e.g. "Diwali", "holi", "janmashtami") — fuzzy matched. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| festival | — | — | — |
| lat | number | — | — |
| lon | number | — | — |
| tz_offset_hours | number | — | — |
| year | integer | yes | — |
No output schema declared.
No examples provided.
get_muhurta ~311
Return the muhurta details active at a given time and location, exactly as the HinduCalendar app computes them: - 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) 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. 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". Returns: Dict with sunrise, sunset, current_lagna, current_choghadiya, current_hora, and ongoing_muhurtas.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | — | — |
| lat | number | yes | — |
| lon | number | yes | — |
| time | string | yes | — |
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".
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | — |
| date | string | yes | — |
| lang | string | — | — |
| lat | number | — | — |
| lon | number | — | — |
| tz | string | — | — |
No output schema declared.
No examples provided.