Astrodai Vedic Astrology & Ephemeris Engine
REMOTE · ASTRODAI.COM
Vedic astrology and ephemeris engine calibrated to Swiss Ephemeris and Jagannatha Hora.
Available components
Last scanned (22 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 Nov 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1326 tokens (~165/item across 8 items; 6 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://astrodai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=astrodai.com | CN=YR1,O=Let's Encrypt,C=US | 30 Oct 2026 | 28 Jan 2027 | RSA 2048 | SHA256-RSA | 665d5e52fd6e418b3ff7d951bca2699be88 |
| SANs: astrodai.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of astrodai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| astrodai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://astrodai.com/mcp | Verified | 200 | |
| http (plaintext) | http://astrodai.com/mcp | HTTPS enforced | 308 | https://astrodai.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
birth_time_check Birth time sensitivity ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | yes | Birth date, YYYY-MM-DD (1900 to 2099). |
| birth_time | string | yes | Local birth time as recorded, 24-hour HH:MM or HH:MM:SS. |
| place_token | string | yes | place_token from find_birthplace (valid 24 hours). |
No output schema declared.
No examples provided.
chart_overview Birth chart overview ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | yes | Birth date, YYYY-MM-DD (1900 to 2099). |
| birth_time | string | yes | Local birth time as recorded, 24-hour HH:MM or HH:MM:SS. |
| place_token | string | yes | place_token from find_birthplace (valid 24 hours). |
No output schema declared.
No examples provided.
current_chapter Current life chapter ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | yes | Birth date, YYYY-MM-DD (1900 to 2099). |
| birth_time | string | yes | Local birth time as recorded, 24-hour HH:MM or HH:MM:SS. |
| place_token | string | yes | place_token from find_birthplace (valid 24 hours). |
No output schema declared.
No examples provided.
find_birthplace Find birthplace ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| place | string | yes | Town name, optionally followed by a comma and the region or country. |
No output schema declared.
No examples provided.
life_area Life area evidence ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | One of: career, relationships, wealth, home_property, children, education, foreign_settlement, spiritual_growth. |
| birth_date | string | yes | Birth date, YYYY-MM-DD (1900 to 2099). |
| birth_time | string | yes | Local birth time as recorded, 24-hour HH:MM or HH:MM:SS. |
| place_token | string | yes | place_token from find_birthplace (valid 24 hours). |
No output schema declared.
No examples provided.
panchang Panchang for a day ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date, YYYY-MM-DD (1900 to 2099). |
| place_token | string | yes | place_token from find_birthplace (valid 24 hours). |
| time | string | – | Local time, 24-hour HH:MM; default 12:00. |
No output schema declared.
No examples provided.
How do I install the Astrodai Vedic Astrology & Ephemeris Engine MCP server?
Astrodai Vedic Astrology & Ephemeris Engine is a hosted endpoint at https://astrodai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · astrodai.com
claude mcp add --transport http tanudai-astrodai 'https://astrodai.com/mcp'
What is the Astrodai Vedic Astrology & Ephemeris Engine MCP server?
Astrodai Vedic Astrology & Ephemeris Engine is an MCP server listed in the public MCP registry as io.github.tanudai/astrodai. Vedic astrology and ephemeris engine calibrated to Swiss Ephemeris and Jagannatha Hora. This page covers its hosted endpoint (https://astrodai.com/mcp).
Is the Astrodai Vedic Astrology & Ephemeris Engine MCP server safe to use?
Astrodai Vedic Astrology & Ephemeris Engine scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Astrodai Vedic Astrology & Ephemeris Engine MCP server expose?
Astrodai Vedic Astrology & Ephemeris Engine exposes 6 tools: find_birthplace, chart_overview, life_area, current_chapter, birth_time_check, panchang. Their descriptions and schemas cost roughly 1,010 tokens of context every time the server is loaded.
Does the Astrodai Vedic Astrology & Ephemeris Engine MCP server require authentication?
No. We connected to Astrodai Vedic Astrology & Ephemeris Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Astrodai Vedic Astrology & Ephemeris Engine MCP server still maintained?
Astrodai Vedic Astrology & Ephemeris Engine is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.