Skip to content

Jyotish — Vedic astrology for AI agents

by entradox · remote · no sign-in to list tools · v1.0.0 · published by GitHub user entradox

Vedic astrology for AI agents: chart facts, panchang windows, and Guna Milan compatibility.

Changes · 2

8 tools: 2 change things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http ai-jyotish-bot https://jyotish-mcp-production.up.railway.app/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 2Claude Code: ask
  • ask_jyotishGrounded synthesis answer to a question, computed from the birth chart through the same accuracy-gated path as the retail chat endpoint (chart-anchor check and rewrite retry inside…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Grounded synthesis answer to a question, computed from the birth chart through the same accuracy-gated path as the retail chat endpoint (chart-anchor check and rewrite retry inside run_reading). The response envelope carries citation_status and accuracy-gate notes. lang: en or hi (default en).
  • guna_milanVedic compatibility (Guna Milan / Ashtakoota) between two people, 36 points across eight kootas: varna, vashya, tara, yoni, graha_maitri, gana, bhakoot, nadi.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Vedic compatibility (Guna Milan / Ashtakoota) between two people, 36 points across eight kootas: varna, vashya, tara, yoni, graha_maitri, gana, bhakoot, nadi. Moon nakshatra and rashi for each native are computed from their birth data through the same chart engine as get_chart_facts — do not pass nakshatra/rashi yourself. Deterministic, no LLM. Each koota carries its score, its maximum, and a plain-language reason, so the result is auditable rather than a bare number.
Only reads 6Claude Code: allow
  • get_chart_factsDeterministic Vedic chart facts for birth data: lagna, Moon sign/nakshatra, current dasha, planets in houses, house lords, dignities, combustions, D9/D10 ascendants, Sade Sati stan…No findings

    Why it is in this group

    • The name "get_chart_facts" says "get": a word for reading.
    Description, as the server wrote it
    Deterministic Vedic chart facts for birth data: lagna, Moon sign/nakshatra, current dasha, planets in houses, house lords, dignities, combustions, D9/D10 ascendants, Sade Sati standing, yogas with classical-text citations, dasha timeline. Pure computation, no LLM. Same output as POST /api/b2b/chart-facts.
  • get_dashaVimshottari dasha standing and full timeline for birth data: current maha / antar / pratyantar dasha plus every maha-dasha period with start and end dates.No findings

    Why it is in this group

    • The name "get_dasha" says "get": a word for reading.
    Description, as the server wrote it
    Vimshottari dasha standing and full timeline for birth data: current maha / antar / pratyantar dasha plus every maha-dasha period with start and end dates. Deterministic, no LLM. Same compute path as POST /api/b2b/dasha.
  • get_doshasDosha screen for birth data: Manglik standing under both conventions (Moon and Lagna), Kaal Sarp detection, Sade Sati phase, and extra classical yogas.No findings

    Why it is in this group

    • The name "get_doshas" says "get": a word for reading.
    Description, as the server wrote it
    Dosha screen for birth data: Manglik standing under both conventions (Moon and Lagna), Kaal Sarp detection, Sade Sati phase, and extra classical yogas. Deterministic, no LLM. lang: en or hi (default en). Same compute path as POST /api/b2b/doshas.
  • get_forecastStructured personalized forecast for birth data — per-area tones, day calendar, ingresses, dasha standing.No findings

    Why it is in this group

    • The name "get_forecast" says "get": a word for reading.
    Description, as the server wrote it
    Structured personalized forecast for birth data — per-area tones, day calendar, ingresses, dasha standing. period: daily (optional date), weekly, monthly (optional year+month), or yearly (optional year). Deterministic engine output, no LLM narration. lang: en or hi (default en). Same compute path as POST /api/b2b/forecast.
  • get_panchangUse when a user asks about the Hindu calendar day for a location — tithi, paksha, nakshatra, yoga, karana, vara and its lord, sunrise and sunset, plus Rahu Kaal, Yamaganda, Gulika …No findings

    Why it is in this group

    • The name "get_panchang" says "get": a word for reading.
    Description, as the server wrote it
    Use when a user asks about the Hindu calendar day for a location — tithi, paksha, nakshatra, yoga, karana, vara and its lord, sunrise and sunset, plus Rahu Kaal, Yamaganda, Gulika Kaal and the Choghadiya day/night windows. Needs only a place and a date, so it works without anyone's birth details. Deterministic computation, no LLM. Same compute path as GET /api/panchang.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • get_vargaDivisional chart (varga) placements for birth data — all sixteen supported divisions d1,d2,d3,d4,d7,d9,d10,d12,d16,d20,d24,d27,d30,d40,d45,d60.No findings

    Why it is in this group

    • The name "get_varga" says "get": a word for reading.
    Description, as the server wrote it
    Divisional chart (varga) placements for birth data — all sixteen supported divisions d1,d2,d3,d4,d7,d9,d10,d12,d16,d20,d24,d27,d30,d40,d45,d60. Deterministic, no LLM. Same compute path as POST /api/b2b/varga.

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.

Install

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

claude mcp add --transport http ai-jyotish-bot https://jyotish-mcp-production.up.railway.app/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ai-jyotish-bot__get_chart_facts",
      "mcp__ai-jyotish-bot__get_panchang",
      "mcp__ai-jyotish-bot__get_varga",
      "mcp__ai-jyotish-bot__get_dasha",
      "mcp__ai-jyotish-bot__get_doshas",
      "mcp__ai-jyotish-bot__get_forecast"
    ],
    "ask": [
      "mcp__ai-jyotish-bot__ask_jyotish",
      "mcp__ai-jyotish-bot__guna_milan"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as ai-jyotish-bot. Review it before you use it.