Vedic Astrology and Kundli MCP Server by RoxyAPI
REMOTE · ROXYAPI.COM
Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.
Available components
Last scanned (12 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 42024 tokens (~724/item across 58 items; 58 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (95% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 58 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
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.
- 29 Oct 26 0
- Tool “post_vedic_astrology_kp_chart” rewrote its description, which is the text the model reads security
- Tool “post_vedic_astrology_kp_cusps” rewrote its description, which is the text the model reads security
- Tool “post_vedic_astrology_kp_daily_finance” rewrote its description, which is the text the model reads security
- Tool “post_vedic_astrology_kp_horary” rewrote its description, which is the text the model reads security
- Tool “post_vedic_astrology_kp_ruling_planets_interval” rewrote its description, which is the text the model reads security
- “post_vedic_astrology_daily” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dasha_current” reworded the description of “datetime” cosmetic
- “post_vedic_astrology_dasha_current” reworded the description of “significators” cosmetic
- “post_vedic_astrology_dasha_major” reworded the description of “significators” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha” reworded the description of “significators” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha” reworded the description of “significators” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha” reworded the description of “significators” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma” reworded the description of “significators” cosmetic
- “post_vedic_astrology_kp_chart” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_kp_cusps” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_kp_daily_finance” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_kp_daily_finance” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_kp_horary” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_kp_planets” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_kp_ruling_planets” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_kp_ruling_planets” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_kp_ruling_planets_interval” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_transit” reworded the description of “timezone” cosmetic
- 10 Oct 26 0
- Tool “post_vedic_astrology_birth_chart” rewrote its description, which is the text the model reads security
- Tool “post_vedic_astrology_planetary_positions” rewrote its description, which is the text the model reads security
- Tool “post_vedic_astrology_planetary_positions_monthly” rewrote its description, which is the text the model reads security
- 3 Oct 26 87
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 1 Oct 26 0
- “post_vedic_astrology_aspects_lunar” reworded the description of “year” cosmetic
- “post_vedic_astrology_aspects_monthly” reworded the description of “year” cosmetic
- “post_vedic_astrology_ecliptic_crossings” reworded the description of “year” cosmetic
- “post_vedic_astrology_panchang_choghadiya” reworded the description of “date” cosmetic
- “post_vedic_astrology_panchang_detailed” reworded the description of “date” cosmetic
- “post_vedic_astrology_panchang_hora” reworded the description of “date” cosmetic
- “post_vedic_astrology_parallels_monthly” reworded the description of “year” cosmetic
- “post_vedic_astrology_planetary_positions_monthly” reworded the description of “year” cosmetic
- “post_vedic_astrology_transit_monthly” reworded the description of “year” cosmetic
9 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 30 Sept 26 0
- “post_vedic_astrology_panchang_choghadiya” reworded the description of “date” cosmetic
- “post_vedic_astrology_panchang_detailed” reworded the description of “date” cosmetic
- “post_vedic_astrology_panchang_hora” reworded the description of “date” cosmetic
- “post_vedic_astrology_parallels” reworded the description of “latitude” cosmetic
- “post_vedic_astrology_parallels” reworded the description of “longitude” cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- “post_vedic_astrology_ecliptic_crossings” added an optional parameter “lang” cosmetic
- “post_vedic_astrology_arudha” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_ashtakavarga” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_aspects” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_aspects_lunar” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_aspects_monthly” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_bhav_chalit” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_bhava_bala” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_birth_chart” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_chara_karakas” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dasha_current” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dasha_major” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_divisional_chart” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dosha_kalsarpa” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dosha_manglik” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_dosha_sadhesati” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_ecliptic_crossings” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_kp_chart” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_kp_cusps” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_kp_planets” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_kp_ruling_planets_interval” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_navamsa” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_panchang_basic” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_panchang_choghadiya” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_panchang_detailed” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_panchang_hora” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_parallels” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_parallels_monthly” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_planetary_positions” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_shadbala” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_transit” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_transit_monthly” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_upagraha” reworded the description of “timezone” cosmetic
- “post_vedic_astrology_yoga_detect” reworded the description of “timezone” cosmetic
38 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
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 5 Nov 2026 · Probed https://roxyapi.com/mcp/vedic-astrology
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roxyapi.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b253589252f3f4620e758a7554771c71 |
| SANs: roxyapi.com, *.roxyapi.com | ||||||
| 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 roxyapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roxyapi.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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' 'unsafe-eval' https://challenges.cloudflare.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src 'self' https://challenges.cloudflare.com https://roxyapi.github.io; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), accelerometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roxyapi.com/mcp/vedic-astrology | Verified | 200 | |
| http (plaintext) | http://roxyapi.com/mcp/vedic-astrology | HTTPS enforced | 301 | https://roxyapi.com/mcp/vedic-astrology |
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 →
post_vedic_astrology_upagraha Get upagraha (sub-planet) positions - Upagraha Calculator API ~750
Calculate all 11 Vedic upagraha (sub-planet) positions per Brihat Parashara Hora Shastra (BPHS). Returns 6 time-based upagrahas (Gulika, Mandi, Kala, Mrityu, Ardhaprahara, Yamaghantaka) derived from the 8-part day/night division, plus 5 Sun-longitude-based upagrahas (Dhuma, Vyatipata, Parivesha, Indra Chapa, Upaketu). Essential for complete kundli analysis, dosha assessment, and advanced chart interpretation. Upagraha calculator API, Gulika Mandi position, sub-planet Vedic astrology.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hind… |
| ayanamsaValue | number | – | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| date | string | yes | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and div… |
| latitude | number | yes | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude | number | yes | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| time | string | yes | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and… |
| timezone | – | – | Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to… |
| Name | Type | Req | Description |
|---|---|---|---|
| frame | object | yes | – |
| sunBased | array | yes | – |
| timeBased | array | yes | – |
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}post_vedic_astrology_yoga_detect Detect classical Vedic yogas in a birth chart ~1,278
Chart-driven detection of 48 classical Vedic yogas. Twelve conjunction and dignity yogas: Gajakesari (parashara three-rule definition), Sunapha, Anapha, Dhurdhura, Kemadruma, Chandra Mangala, Budha-Aditya, and the five Pancha Mahapurusha yogas (Ruchaka, Bhadra, Hamsa, Malavya, Sasa). Plus all 32 Nabhasa distribution yogas, which describe how the seven visible grahas are spread across the whole chart rather than any single conjunction, across four families: Asraya (Rajju, Musala, Nala), Dala (Mala, Sarpa), Akriti (Gada, Shakata, Vihaga, Shringataka, Hala, Vajra, Yava, Kamala, Vapi, Yupa, Shara, Shakti, Danda, Nauka, Kuta, Chhatra, Dhanusha, Ardhachandra, Chakra, Samudra) and Sankhya (Gola, Yuga, Shoola, Kedara, Pasa, Damini, Veena). Plus four wealth and poverty verdicts, each ONE answer over a whole family of classical rules: Dhana Yoga over the eleven catalogued wealth combinations of BPHS ch. 41, Daridra Yoga over the poverty combinations of BPHS ch. 42 and Phaladeepika ch. 6, Lakshmi Yoga (BPHS ch. 36), and Dhana Malika (Jataka Parijata ch. 7). Their evidence names every rule that matched and the exact condition it matched on, so a wealth reading cites the combination rather than a label, and a rule resting on a single authority is excluded from the verdict and says so rather than quietly counting. Each yoga is returned with an `id`, `name`, a `present` boolean, a `quality` (Positive, Negative, or Both, i.e. auspicious, inauspicious, or context-dependent), and a classical-text `evidence` string naming the rule that triggered or failed (kendra position, dignity, malefic drishti, lordship, retrograde state, sign modality, bhava distribution). Nabhasa results also apply the four classical precedence norms, so a yoga that matched its own rule but was outranked by a stronger family is returned as absent with evidence naming the norm that silenced it, letting you explain a verdict rather than only report it. There is no separate major/minor flag; `quality` is the auspi…
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hind… |
| ayanamsaValue | number | – | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| date | string | yes | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and div… |
| lang | string | – | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E… |
| latitude | number | yes | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude | number | yes | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| time | string | yes | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and… |
| timezone | – | – | Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to… |
| Name | Type | Req | Description |
|---|---|---|---|
| birthDetails | object | yes | – |
| frame | object | yes | – |
| total | number | yes | – |
| yogas | array | yes | – |
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}How do I install the Vedic Astrology and Kundli MCP Server by RoxyAPI server?
Vedic Astrology and Kundli MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/vedic-astrology, 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 · roxyapi.com
claude mcp add --transport http com-roxyapi-vedic-astrology 'https://roxyapi.com/mcp/vedic-astrology'
What is the Vedic Astrology and Kundli MCP Server by RoxyAPI server?
Vedic Astrology and Kundli MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/vedic-astrology. Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key. This page covers its hosted endpoint (https://roxyapi.com/mcp/vedic-astrology).
Is the Vedic Astrology and Kundli MCP Server by RoxyAPI server safe to use?
Vedic Astrology and Kundli MCP Server by RoxyAPI scores 87 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 Vedic Astrology and Kundli MCP Server by RoxyAPI server expose?
Vedic Astrology and Kundli MCP Server by RoxyAPI exposes 58 tools: post_vedic_astrology_birth_chart, post_vedic_astrology_navamsa, post_vedic_astrology_divisional_chart, post_vedic_astrology_compatibility, post_vedic_astrology_compatibility_dashakoot, and 53 more. Their descriptions and schemas cost roughly 42,024 tokens of context every time the server is loaded.
Does the Vedic Astrology and Kundli MCP Server by RoxyAPI server require authentication?
No. We connected to Vedic Astrology and Kundli MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vedic Astrology and Kundli MCP Server by RoxyAPI server still maintained?
Vedic Astrology and Kundli MCP Server by RoxyAPI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.