Skip to content

Jyotish — Vedic astrology for AI agents MCP server

io.github.entradox/ai-jyotish-botentradoxstreamable-httpv1.0.0Scanned

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

8 tools: 2 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Jyotish — Vedic astrology for AI agents MCP server can do

The Jyotish — Vedic astrology for AI agents MCP server is published by the GitHub account entradox. It has 8 tools. It can create or change data (2 tools: ask_jyotish and guna_milan), but cannot delete data. 6 tools only read.

2 tools read private data (get_panchang and get_forecast).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 1.0.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.

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 6Show 6 read-only tools
  • 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.Reads private dataNo findings

    Why it is in this group

    • The name "get_forecast" 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
    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 …Reads private dataNo findings

    Why it is in this group

    • The name "get_panchang" 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
    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.

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

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:04 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
404
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: initialize answered HTTP 404.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai-jyotish-bot. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ai-jyotish-bot__get_panchang private-data
  • mcp__ai-jyotish-bot__get_forecast 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/io.github.entradox/ai-jyotish-bot/verify?hash=eb167f22a4d39c8b2aea18275859fe5eb557ca17f244487bdfd4717757ea48b1" | jq -e '.changed == false'

Pinned hash eb167f22a4d3, from Oct 21, 2026, 19:22 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.entradox/ai-jyotish-bot/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.entradox/ai-jyotish-bot
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.entradox/ai-jyotish-bot.svg)](https://radar.anlyon.com/servers/io.github.entradox/ai-jyotish-bot)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:33 UTC.

Jyotish — Vedic astrology for AI agents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Jyotish — Vedic astrology for AI agents MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Jyotish — Vedic astrology for AI agents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Jyotish — Vedic astrology for AI agents 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 Jyotish — Vedic astrology for AI agents MCP server have?

8 tools: 2 write, 6 read. ask_jyotish, guna_milan, get_chart_facts, get_panchang, get_varga, get_dasha, get_doshas and get_forecast.

Does the Jyotish — Vedic astrology for AI agents MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Jyotish — Vedic astrology for AI agents MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Jyotish — Vedic astrology for AI agents MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.