Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.
Return sunrise, sunset, tithi, nakshatra, yoga, karana and vara for a date. Panchang elements are read at local sunrise. The result includes each element's start and end time in the requested location's local time.
A call is made on an account that has subscribed to it, which is why this one asks who you are first.
What it does
astro-mcp gives AI assistants a reliable Vedic astrology layer. Ask for the panchang for any date and place and get sunrise and sunset, vara, tithi, nakshatra, yoga and karana with exact start and end times.
Cast a D1 birth chart with lagna, planets, signs, degrees, nakshatras, padas, whole-sign houses and retrograde state. Get the Vimshottari mahadasha timeline, the balance at birth, and the mahadasha/antardasha running on any date. The muhurta tool returns Abhijit and Brahma muhurta, Rahu kaalam, Yamagandam, Gulika and Durmuhurtam for the day.
Built on PyJHora and the Swiss Ephemeris with Lahiri ayanamsa and Drik ganita. It defaults to Varanasi but accepts any latitude, longitude and timezone. Useful for daily planning, muhurta selection, birth-chart study and astrology agents. All calculations run in the server — no third-party astrology API. Open source under AGPL-3.0.
Quickstart
# 1 — buy it first ($5 a month): mcprush.com/checkout?server=ompurwar-astro-mcp
# a key alone is not enough: the gateway refuses every call until it is bought
# 2 — sign in with a key of the account that bought it: npx mcprush@latest login
# the key is at mcprush.com/dashboard#access
# 3 — install
npx mcprush@latest add ompurwar/astro-mcp
# 4 — ask your agent for something these tools do
# get_panchang, get_kundli, get_dashas and 1 more
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on infrastructure we host behind our gateway, and what you install is the connection to it.
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add ompurwar/astro-mcp write the entry with the key for you; --scope user makes it available in every project. The first connection after a quiet spell starts the server, which takes up to a minute: if your client says it failed to connect, reconnect after that (/mcp in Claude Code).
Buy it first — $5 a month. A key alone is not enough: until this account has bought it, the gateway refuses every call. Subscribe, then use a key of the account that bought it.
claude mcp add --transport http --scope user ompurwar-astro-mcp https://mcprush.com/gw/ompurwar-astro-mcp/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing at the gateway. The server itself runs on infrastructure we host, so nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Return sunrise, sunset, tithi, nakshatra, yoga, karana and vara for a date. Panchang elements are read at local sunrise. The result includes each element's start and end time in the requested location's local time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Local date in YYYY-MM-DD format. |
| latitude | number | no | Latitude in degrees; north is positive. |
| longitude | number | no | Longitude in degrees; east is positive. |
| timezone | no | IANA timezone name (e.g. Asia/Kolkata) or a fixed UTC offset in hours (e.g. 5.5). | |
| location_name | string | no | Display name for the location. |
Return the D1 birth chart for a local date, time and place. Includes the lagna and each planet's sign, degree, nakshatra, pada, whole-sign house and retrograde state. Uses Lahiri ayanamsa.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Local birth date in YYYY-MM-DD format. |
| time | string | yes | Local birth time in 24-hour HH:MM format. |
| latitude | number | no | Latitude in degrees; north is positive. |
| longitude | number | no | Longitude in degrees; east is positive. |
| timezone | no | IANA timezone name (e.g. Asia/Kolkata) or a fixed UTC offset in hours (e.g. 5.5). | |
| location_name | string | no | Display name for the location. |
Return the Vimshottari mahadasha timeline and the running periods. Includes the mahadasha balance at birth and the mahadasha/antardasha running on as_of. Uses Lahiri ayanamsa.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Local birth date in YYYY-MM-DD format. |
| time | string | yes | Local birth time in 24-hour HH:MM format. |
| latitude | number | no | Latitude in degrees; north is positive. |
| longitude | number | no | Longitude in degrees; east is positive. |
| timezone | no | IANA timezone name (e.g. Asia/Kolkata) or a fixed UTC offset in hours (e.g. 5.5). | |
| location_name | string | no | Display name for the location. |
| as_of | no | Date in YYYY-MM-DD to evaluate the running dasha; defaults to today. |
Return the day's auspicious and inauspicious time windows. Includes Abhijit and Brahma muhurta, Rahu kaalam, Yamagandam, Gulika and Durmuhurtam. Windows are in the requested location's local time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Local date in YYYY-MM-DD format. |
| latitude | number | no | Latitude in degrees; north is positive. |
| longitude | number | no | Longitude in degrees; east is positive. |
| timezone | no | IANA timezone name (e.g. Asia/Kolkata) or a fixed UTC offset in hours (e.g. 5.5). | |
| location_name | string | no | Display name for the location. |
- The full Personal plan for 7 days
- 50,000 calls a month, included
- Nothing is charged inside the trial
- A card goes on file, and is only charged when it ends
- Becomes Personal on day 8 unless cancelled
- 50,000 calls a month, included
- 60 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against the 50,000 calls a month on Personal
| Tool | Unit | Calls used | Out of the monthly allowance |
|---|---|---|---|
| get_panchang | call | 1 | 0.0020% |
| get_kundli | call | 1 | 0.0020% |
| get_dashas | call | 1 | 0.0020% |
| get_muhurta | call | 1 | 0.0020% |
Failed calls, timeouts and anything the gateway rejects never count. When the allowance runs out the gateway returns an error naming the plan limit — nothing is billed beyond the subscription, ever.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (4 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_panchang | no tags | |
| get_kundli | no tags | |
| get_dashas | no tags | |
| get_muhurta | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 0.1.0.
- The version this listing went live with, after review.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish astro-mcp can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.