# HinduCalendar — panchang, festivals & muhurta (remote · hinducalendar.app)

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

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `hinducalendar.app`: 58/100 (this document), [markdown](https://verifymcp.io/servers/app-hinducalendar-hinducalendar/hinducalendar.md), [page](https://verifymcp.io/servers/app-hinducalendar-hinducalendar/hinducalendar)

## Channel facts

- Endpoint: `https://hinducalendar.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http app-hinducalendar-hinducalendar https://hinducalendar.app/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-hinducalendar-hinducalendar --url https://hinducalendar.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-hinducalendar-hinducalendar:
    url: "https://hinducalendar.app/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-02 (score 58)

First indexed and scored.

## MCP tools (4)

### `get_panchang` (~448 tokens)

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

Input parameters:

- `ayanamsa` (string)
- `date` (string, required)
- `lang` (string)
- `lat` (number)
- `lon` (number)
- `tz` (string)

### `get_festival_dates` (~315 tokens)

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.

Input parameters:

- `festival`
- `lat` (number)
- `lon` (number)
- `tz_offset_hours` (number)
- `year` (integer, required)

### `get_birth_details` (~375 tokens)

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

Input parameters:

- `ayanamsa` (string)
- `lat` (number, required)
- `lon` (number, required)
- `time` (string, required)

### `get_muhurta` (~311 tokens)

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.

Input parameters:

- `lang` (string)
- `lat` (number, required)
- `lon` (number, required)
- `time` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-hinducalendar-hinducalendar/hinducalendar#diagnostics

## Score history

- 2026-08-03: 58
- 2026-08-02: 58

## Links

- Remote endpoint: https://hinducalendar.app/mcp
- Website: https://hinducalendar.app/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/app-hinducalendar-hinducalendar/hinducalendar/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-hinducalendar-hinducalendar/hinducalendar/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-hinducalendar-hinducalendar/hinducalendar