Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
AstroCalc: Vedic astrology is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Vedic astrology: free kundli, kundli milan (guna matching), dasha, yoga rarity, guides. EN/Hindi.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http astrocalc-vedic-astrology-mcp https://astrocalc.in/mcp
# 2 — ask your agent for something these tools do
# free_kundli, kundli_milan, explain_dasha and 12 more
AstroCalc: Vedic astrology costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ASAll 1 server
astrocalc1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http astrocalc-vedic-astrology-mcp https://astrocalc.in/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 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.
Reads a person's birth chart from their date, time and place of birth: their core nature, the life phase they are in now and when it changes, the standout strengths in the chart, and which life areas look strong or need care, with what helps. Useful when the user talks about themselves, a family member or someone they know and wants to understand them better: personality, a life change, career or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date of birth, YYYY-MM-DD (Gregorian calendar). |
| time | string | no | Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate. |
| place | string | no | Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given. |
| lat | number | no | Birth latitude in decimal degrees (north positive). Give together with lon. |
| lon | number | no | Birth longitude in decimal degrees (east positive). Give together with lat. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Checks how well two people match for marriage in the Indian (Vedic) tradition, from both people's birth details: a score out of 36 with what each of its eight parts means, and whether either person has the Mars placement (Manglik) that families often ask about. Useful when the user is thinking about marriage or a relationship, weighing a proposal, or their family has asked for a kundli match ("kun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| person_a | object | yes | Birth details of the first person. |
| person_b | object | yes | Birth details of the second person. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Explains the life phase a person is in right now, what it tends to bring, when it ends and what comes next, from their birth details; or, without birth details, what a given phase means in general and how long it lasts. Useful when the user wonders why life feels a certain way at the moment, when things will change, or about timing for career, marriage, a move or a fresh start, for themselves or s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Date of birth, YYYY-MM-DD (Gregorian calendar). |
| time | string | no | Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate. |
| place | string | no | Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given. |
| lat | number | no | Birth latitude in decimal degrees (north positive). Give together with lon. |
| lon | number | no | Birth longitude in decimal degrees (east positive). Give together with lat. |
| lord | string | no | Mahadasha planet for a general explanation: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu or Ketu (Hindi/Sanskrit names like Shani or Guru also work). Ignored when date is given. |
| antardasha | string | no | Optional antardasha (sub-period) planet inside lord, e.g. "Venus". |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Says how common or rare a particular combination in a birth chart (a yoga) really is, e.g. Gaja Kesari, Raja yoga, Hamsa, Malavya, Budhaditya, Kemadruma, Kaal Sarp, Neecha Bhanga Raja yoga. Useful when someone has been told their chart has a special, lucky or worrying yoga and wants perspective. Accepts English or Hindi names; no birth data needed. Returns "found in about 1 in N charts", the perce
| Parameter | Type | Required | Notes |
|---|---|---|---|
| yoga | string | no | One yoga name, e.g. "Gaja Kesari". |
| yogas | array | no | Several yoga names at once (max 10). |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Finds AstroCalc's plain-language guide chapters that answer a general question about Indian (Vedic) astrology, e.g. "what is Manglik dosha", "is 24 gunas enough", "what is Nadi dosha", "Saturn in the 7th house", "how do dashas work", "what is Sade Sati". Useful for general questions that need no birth data, when a source page the user can read is helpful. Returns up to 3 chapters with title, a sho
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question or topic, in English, Hindi or Hinglish. |
| lang | string | no | Language of titles, summaries and URLs. Defaults to 'hi' for a question written in Devanagari, else 'en'. |
Finds a city or town and its coordinates, Indian places ranked first, from the same city list AstroCalc's kundli form uses. Useful before the birth-chart, matching or life-phase tools when a place name is ambiguous or misspelled (e.g. "Bombay", "Prayagraj", several towns with one name); pass the chosen label as place, or its lat and lon. Returns up to 5 matches with label, state, country, latitude
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Place name, optionally with state or country, e.g. 'Varanasi' or 'Aurangabad, Bihar'. |
| lang | string | no | Language of the summary text: 'en' (default) or 'hi'. |
List the people whose kundlis the user has saved on AstroCalc (themselves, parents, partner, children, friends): name, gender, birth place, Moon sign, when it was saved, and an id. Use when the user talks about themselves or a family member by name or relation ('my mother', 'my son') and a saved kundli may exist, or asks who is saved. Read-only. (needs a free AstroCalc sign-in)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Summary of one saved person's birth chart: their nature (Lagna, Moon sign, nakshatra), the life chapter and phase they are in now with dates (Mahadasha / Antardasha), their most notable yoga and how rare it is, and which life areas are strong or need care, with what helps. Use when the user asks about themselves or a saved family member: personality, a child's nature, strengths, what to work on, w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | yes | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
For one saved person or everyone saved on the account: the life chapter they are in now (Vimshottari Mahadasha) and the current phase within it (Antardasha), with dates, plus what comes next and when, sorted by whose phase changes soonest. Use when the user asks why life feels stuck or is shifting, when things will change, what is changing for someone this year, or about timing for family members.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | no | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. Omit for all saved kundlis. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Marriage compatibility between two saved people: the traditional 36-point Guna Milan (Ashtakoota) with all 8 parts and their cancellations, and the Manglik check for both, from their saved kundlis (bride/groom order follows the saved genders). Use when the user asks whether two saved people are compatible, about a match for a son or daughter, or about Manglik dosha between them. Read-only. (needs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile_a | string | yes | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. |
| profile_b | string | yes | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Side-by-side view of up to 6 saved people: for each of the 12 life areas (career, money, marriage, health, children ...) whether it is strong, mixed or needs care for each person (Sarvashtakavarga points), and the life chapter and phase each is in now. Use when the user asks how family members differ, who is better placed for something, or wants an overview of the family. Omit profiles to compare
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profiles | array | no | Names or ids of 2 to 6 saved kundlis. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Today's planetary weather for one saved person, counted from their Moon sign: where the Moon is (and whether it is a Chandrashtama day to go slow), which houses Saturn, Jupiter, Rahu and Ketu occupy for them, and whether Sade Sati is running. Use when the user asks how today looks for them or someone saved, or whether today suits a plan. Read-only. (needs a free AstroCalc sign-in)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | yes | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
The complete birth chart for a detailed reading: Lagna degree; for each planet its sign, degree, nakshatra and pada, nakshatra lord, house, dignity, retrograde status, aspected houses and conjunctions; the 12 houses with lords and occupants; and divisional charts (D9 Navamsa and D10 Dasamsa by default, or any of D2, D3, D4, D7, D9, D10, D12, D16, D20, D24, D27, D30, D40, D45, D60) with vargottama
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | no | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. |
| date | string | no | Date of birth, YYYY-MM-DD (Gregorian calendar). |
| time | string | no | Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate. |
| place | string | no | Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given. |
| lat | number | no | Birth latitude in decimal degrees (north positive). Give together with lon. |
| lon | number | no | Birth longitude in decimal degrees (east positive). Give together with lat. |
| vargas | array | no | Divisional charts to include. Default ["D9", "D10"]. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Timeline of life chapters (Vimshottari Mahadashas) and phases (Antardashas, or the finer Pratyantardashas for spans up to 3 years) with start and end dates over a chosen span, marking the one running today. For a saved person (profile) or from birth details. Use for timing questions: when a hard period ends, which coming years suit marriage or a career move, what the next decade looks like. Read-o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | no | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. |
| date | string | no | Date of birth, YYYY-MM-DD (Gregorian calendar). |
| time | string | no | Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate. |
| place | string | no | Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given. |
| lat | number | no | Birth latitude in decimal degrees (north positive). Give together with lon. |
| lon | number | no | Birth longitude in decimal degrees (east positive). Give together with lat. |
| from | string | no | Start of the span, YYYY-MM-DD. Defaults to today. |
| years | integer | no | Length of the span in years (default 10). |
| level | string | no | Depth: 'mahadasha', 'antardasha' (default) or 'pratyantardasha'. |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Planet positions on any date from 1900 to 2100 read against a person's chart: each planet's sign, nakshatra and retrograde status, its house from their Lagna and from their Moon, whether Sade Sati is running, and short notes for Saturn, Jupiter, Rahu and Ketu (positions at 12:00 IST). For a saved person (profile) or from birth details. Use when the user asks what is changing for them this year or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | no | A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. |
| date | string | no | Date of birth, YYYY-MM-DD (Gregorian calendar). |
| time | string | no | Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate. |
| place | string | no | Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given. |
| lat | number | no | Birth latitude in decimal degrees (north positive). Give together with lon. |
| lon | number | no | Birth longitude in decimal degrees (east positive). Give together with lat. |
| on | string | no | Date, YYYY-MM-DD. Defaults to today (IST). |
| lang | string | no | Language of the text fields: 'en' (English, default) or 'hi' (Hindi). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AstroCalc: Vedic astrology or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.1 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest1e432ab16eca39cd1be92ed12bf2cf176f50a6334f1175d489d83bdb87d62abe
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| free_kundli | no tags | |
| kundli_milan | no tags | |
| explain_dasha | no tags | |
| yoga_rarity | no tags | |
| learn_answer | no tags | |
| search_place | no tags | |
| my_profiles | no tags | |
| my_kundli | no tags | |
| my_family_phases | no tags | |
| match_my_profiles | no tags | |
| compare_family | no tags | |
| today_for | no tags | |
| full_chart | no tags | |
| life_timeline | no tags | |
| sky_on_date | 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
Integrityfirst-seen
Surface digest1e432ab16eca39cd
Scanned2026-11-07
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can 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.
Sign in to write one
Any signed-in account that does not publish AstroCalc: Vedic astrology can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.