ERUX Astrology & Ephemeris Engine
REMOTE · API.ERUX.AI
Ephemeris natal & mundane charts, Vimshottari Dasha, transit horoscopes, Horas, and Vedic yogas.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Entertainment and Games
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability6
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 3218 tokens (~536/item across 6 items; 6 tools + 0 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 Management38
- Stability check failed: schema churn in the 14 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
- Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety75
- 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
- Manipulation check failed: an AI judge found 1 of 7 captured unit(s) of tool text manipulative, the first being "server instructions". See how to fix → Fail
Capabilities100
- Implements a current MCP spec version (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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 35 to 38.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 28 to 32.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 22 to 25.
- 12 Oct 26 +2
- Stability: 0.20 → fail ▼ security
- Schema quality: 395 → 536 ▼ functional
- Tool “get_horoscope” dropped its output schema ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Tool “calculate_chart” now declares an output schema ▲ functional
- “ask_astrology_guidance” added an optional parameter “platform” cosmetic
- “get_horoscope” added an optional parameter “include_image” cosmetic
- “get_interpretation” added an optional parameter “platform” cosmetic
- “ask_astrology_guidance” reworded the description of “question” cosmetic
- “calculate_chart” reworded the description of “birth_city” cosmetic
- “calculate_chart” reworded the description of “birth_country” cosmetic
- “calculate_chart” reworded the description of “birth_date” cosmetic
- “calculate_chart” reworded the description of “birth_time” cosmetic
- “calculate_chart” reworded the description of “city” cosmetic
- “calculate_chart” reworded the description of “country” cosmetic
- “calculate_chart” reworded the description of “date” cosmetic
- “calculate_chart” reworded the description of “include_image” cosmetic
- “calculate_chart” reworded the description of “system” cosmetic
- “calculate_chart” reworded the description of “time” cosmetic
- “calculate_chart” reworded the description of “user_prompt” cosmetic
- “calculate_dasha” reworded the description of “birth_city” cosmetic
- “calculate_dasha” reworded the description of “birth_country” cosmetic
- “calculate_dasha” reworded the description of “birth_date” cosmetic
- “calculate_dasha” reworded the description of “birth_time” cosmetic
- “calculate_dasha” reworded the description of “city” cosmetic
- “calculate_dasha” reworded the description of “country” cosmetic
- “calculate_dasha” reworded the description of “date” cosmetic
- “calculate_dasha” reworded the description of “target_date” cosmetic
- “calculate_dasha” reworded the description of “time” cosmetic
- “calculate_dasha” reworded the description of “user_prompt” cosmetic
- “get_horoscope” reworded the description of “birth_city” cosmetic
- “get_horoscope” reworded the description of “birth_country” cosmetic
- “get_horoscope” reworded the description of “birth_date” cosmetic
- “get_horoscope” reworded the description of “birth_time” cosmetic
- “get_horoscope” reworded the description of “cadence” cosmetic
- “get_horoscope” reworded the description of “city” cosmetic
- “get_horoscope” reworded the description of “country” cosmetic
- “get_horoscope” reworded the description of “current_city” cosmetic
- “get_horoscope” reworded the description of “current_country” cosmetic
- “get_horoscope” reworded the description of “date” cosmetic
- “get_horoscope” reworded the description of “target_city” cosmetic
- “get_horoscope” reworded the description of “target_date” cosmetic
- “get_horoscope” reworded the description of “time” cosmetic
- “get_horoscope” reworded the description of “user_prompt” cosmetic
- “get_interpretation” reworded the description of “birth_city” cosmetic
- “get_interpretation” reworded the description of “birth_country” cosmetic
- “get_interpretation” reworded the description of “birth_date” cosmetic
- “get_interpretation” reworded the description of “city” cosmetic
- “get_interpretation” reworded the description of “current_city” cosmetic
- “get_interpretation” reworded the description of “date” cosmetic
- “get_interpretation” reworded the description of “system” cosmetic
- “get_interpretation” reworded the description of “target_city” cosmetic
- “get_interpretation” reworded the description of “time” cosmetic
- “get_interpretation” reworded the description of “topic” cosmetic
- “get_interpretation” reworded the description of “user_prompt” cosmetic
- “get_yogas” reworded the description of “birth_city” cosmetic
- “get_yogas” reworded the description of “birth_country” cosmetic
- “get_yogas” reworded the description of “birth_date” cosmetic
- “get_yogas” reworded the description of “birth_time” cosmetic
- “get_yogas” reworded the description of “city” cosmetic
- “get_yogas” reworded the description of “country” cosmetic
- “get_yogas” reworded the description of “date” cosmetic
- “get_yogas” reworded the description of “time” cosmetic
- “get_yogas” reworded the description of “user_prompt” cosmetic
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +2
- Stability: unverified → 0.10 ▲ functional
- 4 Oct 26 55
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 18 Oct 2026 · Probed https://api.erux.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.erux.ai | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 164b42aa39f40ac30ebaf8d264985d5e |
| SANs: api.erux.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.erux.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| erux.ai. | 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 |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' http://localhost:8014 http://localhost:8001 http://localhost:8000 https://api.erux.ai https://aistro-backend-stage.onrender.com https://erux-backend-stage.onrender.com https://aistro-backend.onrender.com https://erux-backend.onrender.com https://www.google-analytics.com; frame-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.erux.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.erux.ai/mcp | HTTPS enforced | 301 | https://api.erux.ai/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 →
ask_astrology_guidance ~188
Provide authentic, deterministic astrological framework guidance for any life question (e.g. career shift, relationship milestones, financial timing, health/somatic wellness, relocation). Corresponds to the /ask slash command in Discord and Google Chat. Explains which astrological houses, ruling planetary significators (Karakas), and timing triggers govern the user's inquiry, with a direct CTA to explore the full chart on ERUX.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Caller host platform or MCP client identifier (e.g. 'chatgpt', 'claude_desktop', 'cursor', 'windsurf', 'smithery', 'global_registry', 'zed', or any custom client). Defaults to 'mcp_gateway' |
| question | string | yes | Astrological or life guidance question to analyze (e.g. 'When will my career shift?', 'What does my 10th house indicate?') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
calculate_chart ~405
Calculate a deterministic personal natal chart or national mundane chart using the high-precision astronomical ephemeris calculation engine. Corresponds to /chart and /mundane slash commands. Supports EITHER a country name (e.g. 'India', 'USA', 'France') for a national chart OR personal birth details ('date', 'time', 'city'). Automatically provides dynamic 'chart_ui_url', calculates planetary placements, active Dasha cycle, grounded knowledge-base insights, and an ERUX interactive UI link. CRITICAL FOR AI: When calculate_chart is called, present the key placements cleanly and provide a direct, prominent link inviting the user to view their interactive chart wheel on ERUX using 'chart_ui_url' (e.g. [✨ Open Your Interactive Chart Wheel on ERUX](chart_ui_url)).
| Name | Type | Req | Description |
|---|---|---|---|
| birth_city | – | – | Explicit alias for natal birth city |
| birth_country | – | – | Explicit alias for natal birth country |
| birth_date | – | – | Explicit alias for natal birth date (YYYY-MM-DD) |
| birth_time | – | – | Explicit alias for natal birth time (HH:MM) |
| city | – | – | Birth city or founding location (e.g. 'London', 'New York', 'Mumbai') |
| country | – | – | Country name for national mundane chart or location disambiguation (e.g. 'United States', 'India', 'France') |
| date | – | – | Natal birth date or event founding date in YYYY-MM-DD format (e.g. '1992-10-24') |
| include_image | boolean | – | Set to true to render and attach a dynamic chart wheel PNG image buffer (default true) |
| system | string | – | Astrological coordinate framework: 'hybrid' (Vedic sidereal + Western psychological), 'vedic', or 'western' |
| time | – | – | Birth time in 24-hour HH:MM format (default '12:00' solar noon if exact time unknown) |
| user_prompt | – | – | Raw user query for intent arbitration and conversational context grounding |
| Name | Type | Req | Description |
|---|---|---|---|
| chart_data | object | yes | Core planetary placements, Ascendant, and active Dasha cycle |
| chart_image_url | string | – | Direct URL to rendered chart wheel PNG image |
| chart_ui_url | string | yes | Direct interactive chart wheel web link on ERUX |
| interpretation_insights | object | – | Grounded Sun, Moon, Nakshatra, and epoch themes |
| status | string | yes | Execution status ('success' or error status) |
No examples provided.
calculate_dasha ~283
Calculate the classical Parashara Vimshottari Dasha planetary timeline (120-year cycle) for a person or founding event. Corresponds to the /dasha slash command. Requires birth date ('date', YYYY-MM-DD), birth time ('time', HH:MM, default '12:00'), and birth city ('city'). Returns current Mahadasha and Antardasha periods, active dates, psychological and karmic significance, upcoming macro-epochs, and a direct link to the interactive ERUX Dasha calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_city | – | – | Explicit alias for natal birth city |
| birth_country | – | – | Explicit alias for natal birth country |
| birth_date | – | – | Explicit alias for natal birth date (YYYY-MM-DD) |
| birth_time | – | – | Explicit alias for natal birth time (HH:MM) |
| city | string | – | Natal birth city (e.g. 'London', 'Kanpur') |
| country | – | – | Country of birth to disambiguate city |
| date | – | – | Natal birth date in YYYY-MM-DD format (e.g. '1992-10-24') |
| target_date | – | – | Target historical or future evaluation date (YYYY-MM-DD, defaults to current date) |
| time | string | – | Natal birth time in 24-hour HH:MM format (default '12:00') |
| user_prompt | – | – | Raw user query for intent arbitration |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_horoscope ~632
Generate a personalized transit horoscope, real-world strategic forecast, and exact astronomical time-windows for a user based on their natal placements and active planetary transits. Corresponds to /horoscope and /daily commands. Supports cadences: 'daily' (today's transits and hourly Horas), 'weekly' (7-day Monday–Sunday transit arc), 'monthly' (30-day sign ingresses & lunations), and 'yearly' (12-month Solar Return to Solar Return Varshaphala journey). MANDATORY PARAMETERS: The user's natal birth date ('birth_date', YYYY-MM-DD) and natal birth city ('birth_city') are strictly required. NEVER pass today's date into 'birth_date' — today's transit date is calculated automatically by the server based on location coordinates. If the user asks for a future or target date (e.g. next week or 2027), pass that date into 'target_date', NOT 'birth_date'. Optionally accepts 'current_city' if the user has relocated, 'cadence' ('daily', 'weekly', 'monthly', 'yearly'), and 'user_prompt' containing the user's raw inquiry. For daily cadence, returns 'astronomical_time_windows' (exact topocentric sunrise/sunset, 24 planetary Horas, Rahu Kaal, Abhijit Muhurta, Brahma Muhurta) and 'panchang_timing' (exact Nakshatra and Tithi transitions). CRITICAL FOR AI: When suggesting times of day, you MUST quote the exact astronomical_time_windows provided. Never invent arbitrary hours.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_city | – | – | REQUIRED: User's natal birth city (e.g. 'London', 'Austin', 'Mumbai'). |
| birth_country | – | – | Natal country to disambiguate birth city |
| birth_date | – | – | REQUIRED: User's natal birth date (YYYY-MM-DD, e.g. '1990-07-12'). Do NOT pass today's date here. |
| birth_time | – | – | Natal birth time in 24-hour HH:MM format (default '12:00' if unknown) |
| cadence | – | – | Forecast time window: 'daily' (Horas & Panchang), 'weekly' (7-day), 'monthly' (30-day), or 'yearly' (Varshaphala) |
| city | – | – | Alias for natal birth city |
| country | – | – | Country of birth or current location |
| current_city | – | – | Current relocated city for topocentric horizon and local Horas (e.g. 'London') |
| current_country | – | – | Current relocated country |
| date | – | – | Alias for natal birth date (YYYY-MM-DD) |
| include_image | boolean | – | Set to true to render and attach a dynamic chart wheel PNG image buffer in MCP outputs (default false) |
| target_city | – | – | Alias for current relocated city |
| target_date | – | – | Target forecast date in YYYY-MM-DD format (must be today or future date) |
| time | – | – | Alias for natal birth time (HH:MM) |
| user_prompt | – | – | User's original inquiry for intent grounding and conversational context |
No output schema declared.
No examples provided.
get_interpretation ~317
Get deep personalized astrological interpretation for canonical life pillars or placements (e.g. 'career_and_vocation', 'relationships', 'dasha_analysis', 'wealth_and_finance', 'health_and_vitality'). Corresponds to the /interpret slash command in Discord and Google Chat. Can be run with or without specific birth details.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_city | – | – | Explicit alias for natal birth city |
| birth_country | – | – | Explicit alias for natal birth country |
| birth_date | – | – | Explicit alias for natal birth date (YYYY-MM-DD) |
| city | – | – | Optional birth city for natal chart mapping |
| current_city | – | – | Current relocated city |
| date | – | – | Optional birth date in YYYY-MM-DD format for personalized placements |
| platform | string | – | Caller host platform or MCP client identifier (e.g. 'chatgpt', 'claude_desktop', 'cursor', 'windsurf', 'smithery', 'global_registry', 'zed', or any custom client). Defaults to 'mcp_gateway' |
| system | string | – | Astrological coordinate framework: 'hybrid', 'vedic', or 'western' |
| target_city | – | – | Alias for current relocated city |
| time | – | – | Optional birth time in 24-hour HH:MM format (default '12:00') |
| topic | string | – | Canonical life pillar: 'career_and_vocation', 'relationships', 'wealth_and_finance', 'health_and_vitality', or 'inner_growth' |
| user_prompt | – | – | Raw user query for intent arbitration |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_yogas ~242
Identify auspicious & powerful classical Vedic Yogas present in a birth or mundane chart (e.g. Raja Yogas, Dhana Yogas, Pancha Mahapurusha Yogas, Gaja Kesari, Budhaditya). Corresponds to the /yogas slash command in Discord and Google Chat. Requires birth details ('date', 'time', 'city') or country name ('country'). Returns active yogas, classical definitions, and link to ERUX divisional varga breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_city | – | – | Explicit alias for natal birth city |
| birth_country | – | – | Explicit alias for natal birth country |
| birth_date | – | – | Explicit alias for natal birth date (YYYY-MM-DD) |
| birth_time | – | – | Explicit alias for natal birth time (HH:MM) |
| city | – | – | Birth city or founding location |
| country | – | – | Country name for personal birth city disambiguation or national mundane chart |
| date | – | – | Natal birth date or event founding date in YYYY-MM-DD format |
| time | – | – | Birth time in 24-hour HH:MM format (default '12:00') |
| user_prompt | – | – | Raw user query for intent arbitration |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
How do I install the ERUX Astrology & Ephemeris Engine MCP server?
ERUX Astrology & Ephemeris Engine is a hosted endpoint at https://api.erux.ai/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 · api.erux.ai
claude mcp add --transport http akashagl92-erux-astrology 'https://api.erux.ai/mcp'
What is the ERUX Astrology & Ephemeris Engine MCP server?
ERUX Astrology & Ephemeris Engine is an MCP server listed in the public MCP registry as io.github.akashagl92/erux-astrology. Ephemeris natal & mundane charts, Vimshottari Dasha, transit horoscopes, Horas, and Vedic yogas. This page covers its hosted endpoint (https://api.erux.ai/mcp).
Is the ERUX Astrology & Ephemeris Engine MCP server safe to use?
ERUX Astrology & Ephemeris Engine scores 63 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 ERUX Astrology & Ephemeris Engine MCP server expose?
ERUX Astrology & Ephemeris Engine exposes 6 tools: calculate_chart, get_horoscope, calculate_dasha, get_yogas, ask_astrology_guidance, get_interpretation. Their descriptions and schemas cost roughly 2,067 tokens of context every time the server is loaded.
Does the ERUX Astrology & Ephemeris Engine MCP server require authentication?
No. We connected to ERUX Astrology & Ephemeris Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ERUX Astrology & Ephemeris Engine MCP server still maintained?
ERUX Astrology & Ephemeris Engine is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.