Skip to content

Astrodai Vedic Astrology & Ephemeris Engine

io.github.tanudai/astrodaitanudaistreamable-httpv1.0.0Scanned

Vedic astrology and ephemeris engine calibrated to Swiss Ephemeris and Jagannatha Hora.

6 tools: 5 change things and 1 only read.

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

Anlyon alternative

5 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 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 →

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.

6 tools

Changes things 5Claude Code: ask
  • birth_time_checkHow sensitive the chart is to the recorded birth time, in plain language: minutes earlier or later until the rising sign changes, the same for the Moon nakshatra quarter (pada) and…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How sensitive the chart is to the recorded birth time, in plain language: minutes earlier or later until the rising sign changes, the same for the Moon nakshatra quarter (pada) and the D9 and D10 rising signs, and how many days the life chapter dates move per minute of birth time. It does not correct the birth time. Birth details are used only to calculate this answer and are not stored.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • chart_overviewA short plain-language summary of the sidereal birth chart (True Chitrapaksha ayanamsa): the rising sign, the Moon sign and nakshatra and the Sun sign, each with a one-line meaning…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    A short plain-language summary of the sidereal birth chart (True Chitrapaksha ayanamsa): the rising sign, the Moon sign and nakshatra and the Sun sign, each with a one-line meaning, and the running Vimshottari life chapter and sub-chapter (month and year). Up to 3 answers per chart every 6 hours, shared with life_area and current_chapter. Birth details are used only to calculate this answer; a one-way code is kept for 6 hours to apply fair-use limits.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: false
  • current_chapterThe Vimshottari life chapter (mahadasha) and sub-chapter (antardasha) running today, with month and year, in plain language: what their planets stand for, the houses they sit in an…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The Vimshottari life chapter (mahadasha) and sub-chapter (antardasha) running today, with month and year, in plain language: what their planets stand for, the houses they sit in and guide, the life areas they touch, and when the next sub-chapter starts. Finer periods are not included. Up to 3 answers per chart every 6 hours, shared with chart_overview and life_area. Birth details are used only to calculate this answer; a one-way code is kept for 6 hours to apply fair-use limits.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: false
  • life_areaPlain-language findings from the birth chart for one area of life: how strong the area's main house is, the planet that guides it and where it sits, the other houses and planets fo…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Plain-language findings from the birth chart for one area of life: how strong the area's main house is, the planet that guides it and where it sits, the other houses and planets for the area, support from planets (strong, mixed or needs effort), and whether the running life chapter touches the area. Areas: career, relationships, wealth, home_property, children, education, foreign_settlement, spiritual_growth. Health is not covered. Up to 3 answers per chart every 6 hours, shared with chart_overview and current_chapter. Birth details are used only to calculate this answer; a one-way code is kept for 6 hours to apply fair-use limits.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • panchangWeekday, tithi, paksha, nakshatra, yoga and karana for a date and place, calculated at 12:00 local time unless a time is given.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Weekday, tithi, paksha, nakshatra, yoga and karana for a date and place, calculated at 12:00 local time unless a time is given. Sunrise, sunset and Rahu kalam are not included. Birth details are used only to calculate this answer and are not stored.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • find_birthplaceLook up a town in the Astrodai atlas (towns above about 15,000 people; places at or beyond 66 degrees latitude are not supported).No findings

    Why it is in this group

    • The name "find_birthplace" says "find": a word for reading.
    Description, as the server wrote it
    Look up a town in the Astrodai atlas (towns above about 15,000 people; places at or beyond 66 degrees latitude are not supported). Returns up to 5 candidates, each with a place_token for the other tools. Add the region or country after a comma to narrow the search. If nothing matches, try the nearest larger town.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true

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 private-data or untrusted-input or outbound.

Reads private data0
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.

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http astrodai https://astrodai.com/mcp
claude mcp add --transport http astrodai https://astrodai.com/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__astrodai__find_birthplace"
    ],
    "ask": [
      "mcp__astrodai__chart_overview",
      "mcp__astrodai__life_area",
      "mcp__astrodai__current_chapter",
      "mcp__astrodai__birth_time_check",
      "mcp__astrodai__panchang"
    ],
    "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 astrodai. Review it before you use it.

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://anlyon.dev/api/v1/servers/io.github.tanudai/astrodai/verify?hash=68237d40057fcd0380c031b35daa13c71911d746328a309b0133b6e718edb1e7" | jq -e '.changed == false'

Pinned hash 68237d40057f, from Nov 3, 2026, 22:18 UTC.

Watch

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

https://anlyon.dev/servers/io.github.tanudai/astrodai/changes.xml

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

Badge

anlyon.dev badge for io.github.tanudai/astrodai
[![anlyon.dev](https://anlyon.dev/badge/io.github.tanudai/astrodai.svg)](https://anlyon.dev/servers/io.github.tanudai/astrodai)

Source: MCP Registry · repository. Synced Nov 3, 2026, 22:18 UTC.