Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vedic Astrology and Kundli MCP Server by RoxyAPI

REMOTE · ROXYAPI.COM · SCANNED SEP 20

Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.

Available components

0 this week 87 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 38327 tokens (~684/item across 56 items; 56 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 56 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 56 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
Install

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

# add to Claude Code
claude mcp add --transport http com-roxyapi-vedic-astrology 'https://roxyapi.com/mcp/vedic-astrology'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-roxyapi-vedic-astrology": {
      "url": "https://roxyapi.com/mcp/vedic-astrology"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-roxyapi-vedic-astrology": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/vedic-astrology"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-roxyapi-vedic-astrology]
url = "https://roxyapi.com/mcp/vedic-astrology"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-roxyapi-vedic-astrology": {
      "type": "remote",
      "url": "https://roxyapi.com/mcp/vedic-astrology",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-roxyapi-vedic-astrology --url 'https://roxyapi.com/mcp/vedic-astrology' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-roxyapi-vedic-astrology:
    url: "https://roxyapi.com/mcp/vedic-astrology"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-roxyapi-vedic-astrology": {
      "Transport": "http",
      "Url": "https://roxyapi.com/mcp/vedic-astrology"
    }
  }
}
# add to Vellum
assistant mcp add com-roxyapi-vedic-astrology -t streamable-http -u 'https://roxyapi.com/mcp/vedic-astrology'
// mcp.json
{
  "mcpServers": {
    "com-roxyapi-vedic-astrology": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/vedic-astrology"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 19 Sept 26 0
    • Tool “post_vedic_astrology_dasha_current” rewrote its description, which is the text the model reads security
  • 17 Sept 26 0
    • “get_vedic_astrology_kp_ayanamsa” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_arudha” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_ashtakavarga” 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_navamsa” 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_upagraha” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_yoga_detect” reworded the description of “timezone” cosmetic
    • Tool “post_vedic_astrology_kp_daily_finance” changed its title: Score the day for money with four sub lord layers - KP Daily Finance API → Daily finance score from four KP sub lord layers - KP Daily Finance API cosmetic

    23 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 15 Sept 26 0
    • New tool “post_vedic_astrology_kp_daily_finance” functional
  • 14 Sept 26 0
    • Tool “post_vedic_astrology_daily” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_dasha_current” rewrote its description, which is the text the model reads security
    • “post_vedic_astrology_dasha_current” added an optional parameter “datetime” cosmetic
  • 8 Sept 26 0
    • Tool “post_vedic_astrology_kp_sublord_changes” rewrote its description, which is the text the model reads security
    • “post_vedic_astrology_kp_rasi_changes” reworded the description of “endDate” cosmetic
    • “post_vedic_astrology_kp_rasi_changes” reworded the description of “startDate” cosmetic
    • “post_vedic_astrology_kp_rasi_changes” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_kp_sublord_changes” reworded the description of “endDate” cosmetic
    • “post_vedic_astrology_kp_sublord_changes” reworded the description of “startDate” cosmetic
    • “post_vedic_astrology_kp_sublord_changes” reworded the description of “timezone” cosmetic
  • 4 Sept 26 0
    • Tool “get_vedic_astrology_avasthas_id” rewrote its description, which is the text the model reads security
    • Tool “get_vedic_astrology_kp_ayanamsa” rewrote its description, which is the text the model reads security
    • Tool “get_vedic_astrology_nakshatras_id” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_dasha_major” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_dasha_sub_mahadasha” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_dasha_sub_mahadasha_antardasha” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma” rewrote its description, which is the text the model reads security
    • 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_planets” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_kp_ruling_planets” rewrote its description, which is the text the model reads security
    • “post_vedic_astrology_aspects” reworded the description of “coordinateSystem” cosmetic
    • “post_vedic_astrology_aspects_lunar” reworded the description of “coordinateSystem” cosmetic
    • “post_vedic_astrology_aspects_monthly” reworded the description of “coordinateSystem” cosmetic
    • “post_vedic_astrology_ecliptic_crossings” reworded the description of “coordinateSystem” cosmetic
    • “post_vedic_astrology_planetary_positions_monthly” reworded the description of “coordinateSystem” cosmetic
    • “post_vedic_astrology_transit” reworded the description of “coordinateSystem” cosmetic
    • “post_vedic_astrology_transit_monthly” reworded the description of “coordinateSystem” cosmetic
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 20 Sept 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 26 Jul 2026 24 Oct 2026 ECDSA 256 ECDSA-SHA256 fb04ac30ca01abb60e3558bdfadfe2f4
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' https://cdn.jsdelivr.net; img-src 'self' data: https:; font-src 'self' https://fonts.scalar.com; connect-src 'self' https://api.scalar.com https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src 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
MCP tools · 56 exposed · ~38,327 tokens

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 →

Tool Tokens
post_vedic_astrology_kp_horary ~1,126

Cast a Krishnamurti Paddhati horary chart, also called Prashna, from a number between 1 and 249 given by the querent plus the moment and place the question is judged. NO BIRTH DETAILS ARE NEEDED, which is what makes horary the KP answer when birth time is unknown or unreliable. The number maps to one of the 249 KP sub divisions and sets the Ascendant; the twelve Placidus cusps follow from that Ascendant at the given latitude, and every planetary position comes from the real sky at the moment of the question. Returns the Ascendant with its sub lord, all twelve cusps with star lord and sub lord, the nine grahas placed against those cusps, the five ruling planets for validating the chart, and four-level significators for judging which houses each graha supports. KP horary API, Prashna kundali calculator, 249 horary number chart, Krishnamurti Paddhati horary, cusp sub lord question answering.

NameTypeReqDescription
ayanamsastringAyanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanam…
ayanamsaValuenumberCustom 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.
compactbooleanSet 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.
datestringyesDate the question was taken up for judgment, YYYY-MM-DD. Not a birth date: a horary chart needs no birth details at all, which is the point of the method.
focusstringWhich signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same…
horaryNumberintegeryesHorary number from 1 to 249, given by the querent while focused on their question. It maps to one of the 249 KP sub divisions of the zodiac, and that division sets the Ascendant of the chart. The que…
langstringResponse 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…
latitudenumberyesLatitude where the question is judged, decimal degrees. The house cusps are Placidus and therefore latitude dependent, so this is the place of judgment, not the querent birthplace.
longitudenumberyesLongitude where the question is judged, decimal degrees.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesTime the question was taken up for judgment, 24-hour HH:MM:SS. In KP practice this is the moment the astrologer receives and understands the question, not the moment the querent first thought of it.…
timezoneTimezone: IANA name (e.g. "Asia/Kolkata") OR decimal hours from UTC. Defaults to 5.5.

No output schema declared.

{"date":"2026-03-08","horaryNumber":108,"latitude":19.076,"longitude":72.8777,"time":"14:30:00"}
post_vedic_astrology_kp_planets ~567

Get planetary positions with detailed KP star-lord and sub-lord calculations for precise event timing and significator analysis. Returns all 9 planets (Sun through Ketu) with nakshatra, star-lord, sub-lord, and KP horary numbers (1-249). Essential for KP astrology software, significator analysis, and event prediction. Use it as a star lord and sub lord calculator wherever Krishnamurti Paddhati planet positions drive the reading.

NameTypeReqDescription
ayanamsastringAyanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanam…
ayanamsaValuenumberCustom 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.
compactbooleanSet 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.
datestringyesBirth date in YYYY-MM-DD format
latitudenumberyesBirth location latitude in decimal degrees
longitudenumberyesBirth location longitude in decimal degrees
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format
timezoneTimezone offset from UTC in hours. Defaults to 5.5 (IST) for Vedic astrology.

No output schema declared.

{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_kp_planets_interval ~714

Calculate positions of all 9 planets (Sun through Saturn, Rahu, Ketu) at regular time intervals with full KP hierarchy: sign lord, star lord, sublord, and sub-sublord. Returns longitude, zodiac sign, nakshatra, sublord, sub-sublord, and KP number (1-249) for each planet at each timestamp. Ideal for tracking planetary motion, finding optimal muhurta windows, analyzing transit patterns, and building KP ephemeris tables. Maximum range of 7 days with 15-minute to 24-hour intervals.

NameTypeReqDescription
ayanamsastringAyanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with…
compactbooleanSet 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.
endDatetimestringyesEnd datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Maximum 7 days from start. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is…
intervalMinutesnumberyesTime between calculations in minutes. Range: 15 (quarter-hourly) to 1440 (daily).
latitudenumberyesObserver latitude in decimal degrees (for future Lagna calculations)
longitudenumberyesObserver longitude in decimal degrees (for future Lagna calculations)
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
startDatetimestringyesStart datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
timezoneIANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local t…

No output schema declared.

{"endDatetime":"2025-01-15T23:59:00Z","intervalMinutes":60,"latitude":28.6139,"longitude":77.209,"startDatetime":"2025-01-15T00:00:00Z"}
post_vedic_astrology_kp_rasi_changes ~643

Track when planets enter new zodiac signs (rasi) with precise ingress timestamps. Essential for Vedic astrology transit analysis, muhurta selection, and predictive horoscope readings. Returns exact times when planets cross sign boundaries (0, 30, 60 degrees etc). Use for tracking Sun sankranti dates, Moon sign changes for panchang, or outer planet transits for yearly predictions.

NameTypeReqDescription
ayanamsastringAyanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with…
compactbooleanSet 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.
endDatestringyesLast day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
planetstringyesPlanet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn
startDatestringyesFirst day of the search (YYYY-MM-DD), a calendar day in `timezone`.
timezoneIANA name (e.g. "America/New_York", "Europe/London"), a fixed offset like "+05:30", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole ra…

No output schema declared.

{"endDate":"2025-12-31","planet":"Sun","startDate":"2025-01-01"}
post_vedic_astrology_kp_ruling_planets ~714

Calculate the 5 ruling planets at any moment using Krishnamurti Paddhati horary astrology. Returns Day Lord, Moon Sign/Star/Sub Lord, Lagna Sign/Star/Sub Lord. Optionally provide birth data (birthDate, birthTime) to include significators showing which houses each ruling planet signifies in the birth chart, which is essential for KP prediction.

NameTypeReqDescription
birthDatestringBirth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.
birthTimestringBirth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.
compactbooleanSet 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.
datetimestringISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timez…
focusstringWhich signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same…
langstringResponse 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…
latitudenumberyesObserver latitude in decimal degrees
longitudenumberyesObserver longitude in decimal degrees
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timezoneTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5.

No output schema declared.

{"latitude":28.6139,"longitude":77.209}
post_vedic_astrology_kp_ruling_planets_interval ~961

Calculate ruling planets and their KP significators at regular time intervals using Krishnamurti Paddhati prashna (horary) astrology. For each interval, a full Placidus house chart is erected and significators are computed using the 4-level KP hierarchy: Level 1 (strongest) planets in star of house occupant, Level 2 occupants, Level 3 planets in star of house owner, Level 4 house owner. Returns Day Lord (sunrise-based Hindu Vara), Moon Sign/Star/Sub/Sub-Sub Lords, Lagna Sign/Star/Sub/Sub-Sub Lords, unique ruling planets set, and per-ruling-planet house significations. No birth data needed, significators come from each moments sky chart. Use for birth time rectification, muhurta selection, and KP horary number analysis.

NameTypeReqDescription
ayanamsastringAyanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with…
compactbooleanSet 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.
endDatetimestringyesEnd of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
focusstringWhich signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same…
intervalMinutesintegeryesInterval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.
langstringResponse 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…
latitudenumberyesObserver latitude in decimal degrees
longitudenumberyesObserver longitude in decimal degrees
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
startDatetimestringyesStart of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
timezoneTimezone offset from UTC in decimal hours. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to…

No output schema declared.

{"endDatetime":"2026-02-03T01:00:00Z","intervalMinutes":5,"latitude":17.385044,"longitude":78.486671,"startDatetime":"2026-02-03T00:00:00Z"}
post_vedic_astrology_kp_sublord_changes ~656

Track when planets cross KP sublord boundaries (1-249 divisions) for precise Krishnamurti Paddhati event timing. Returns exact timestamps when a planet transitions between sublords, essential for prashna kundali analysis and dasha predictions. Use this to find favorable windows when benefic sublords are active. Supports Sun, Moon, Mars, Mercury, Jupiter, Venus, and Saturn tracking over any window up to 365 days.

NameTypeReqDescription
ayanamsastringAyanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with…
compactbooleanSet 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.
endDatestringyesLast day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
planetstringyesPlanet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn
startDatestringyesFirst day of the search (YYYY-MM-DD), a calendar day in `timezone`.
timezoneIANA name (e.g. "America/New_York", "Europe/London"), a fixed offset like "+05:30", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole ra…

No output schema declared.

{"endDate":"2025-01-31","planet":"Moon","startDate":"2025-01-01"}
post_vedic_astrology_navamsa ~754

Calculate Navamsa (D9 divisional chart) for marriage compatibility analysis, spouse prediction, and spiritual life assessment. Navamsa calculator API reveals planetary strength in married life. Each planetary position is divided into 9 parts for accurate marriage astrology. Detects Vargottama planets (exalted status). Essential for matrimonial matching, relationship prediction, and marital harmony analysis in Vedic astrology.

NameTypeReqDescription
ayanamsastringSidereal 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…
ayanamsaValuenumberCustom 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.
compactbooleanSet 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.
datestringyesBirth 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…
langstringResponse 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…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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…
timezoneTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so…

No output schema declared.

{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_panchang_basic ~375

Calculate Panchang elements (Hindu calendar) for any date: Tithi (lunar day), Nakshatra (lunar mansion), Yoga, and Karana. Daily panchang API for determining auspicious timings (muhurta), festival dates, and planetary influences. Tithi calculator with Shukla/Krishna paksha. Accurate nakshatra today with ruling planet. Essential for Hindu calendar integration, muhurta selection, and Vedic timekeeping in astrology apps.

NameTypeReqDescription
compactbooleanSet 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.
datestringyesDate in YYYY-MM-DD format. Panchang elements (Tithi, Nakshatra, Yoga, Karana) are calculated for this date.
langstringResponse 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…
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise/sunset times which define the Vara (weekday) and muhurta boundaries.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise/sunset-dependent panchang elements.
timestringyesTime in HH:MM:SS format (24-hour). Determines the exact Moon and Sun positions for tithi and nakshatra calculation.
timezoneTimezone offset from UTC in decimal hours. Defaults to 5.5 (IST).

No output schema declared.

{"date":"2025-12-17","latitude":28.6139,"longitude":77.209,"time":"12:00:00"}
post_vedic_astrology_panchang_choghadiya ~361

Calculate Choghadiya (Chaughadia) muhurta timings for any date and location. Divides day (sunrise to sunset) and night (sunset to next sunrise) into 8 equal auspicious/inauspicious periods. Each period ruled by a planet: Udveg (Sun, bad), Amrit (Moon, good), Rog (Mars, bad), Labh (Mercury, good), Shubh (Jupiter, good), Char (Venus, good), Kaal (Saturn, bad). Essential for muhurta selection, daily planning, and traditional Hindu timekeeping. Choghadiya calculator API, daily muhurat timings, auspicious time finder.

NameTypeReqDescription
compactbooleanSet 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.
datestringyesDate in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected.
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.
timezoneTimezone offset from UTC in decimal hours. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Choghadiya periods outside IST. Defaults to 5.5 (IST).

No output schema declared.

{"date":"2026-02-03","latitude":17.385044,"longitude":78.486671}
post_vedic_astrology_panchang_detailed ~451

Complete daily panchang with all five limbs (Tithi, Nakshatra, Yoga, Karana, Vara) plus sunrise, sunset, moonrise, moonset times. Includes inauspicious periods (Rahu Kaal, Yamaganda, Gulika Kaal) and auspicious windows (Abhijit Muhurta, Brahma Muhurta). Current planetary hora with start/end times. Essential for muhurta selection, daily horoscope apps, Hindu calendar integration, and electional astrology. Accurate calculations based on observer location.

NameTypeReqDescription
compactbooleanSet 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.
datestringyesDate in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected.
langstringResponse 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…
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.
timezoneTimezone offset from UTC in decimal hours, for example -5 for New York or 9 for Tokyo. Send the offset that matches the coordinates: sunrise, sunset and every muhurta boundary are found by searching…

No output schema declared.

{"date":"2026-02-03","latitude":28.6139,"longitude":77.209}
post_vedic_astrology_panchang_hora ~293

Calculate all 24 Hora (planetary hour) periods for any date and location. Day is divided into 12 equal horas from sunrise to sunset, night into 12 equal horas from sunset to next sunrise. Each hora is ruled by a planet in the Chaldean sequence starting from the day lord. Hora timings API, planetary hours calculator, Vedic hora chart, electional astrology timing.

NameTypeReqDescription
compactbooleanSet 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.
datestringyesDate in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected.
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.
timezoneTimezone offset from UTC in decimal hours. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Hora periods outside IST. Defaults to 5.5 (IST).

No output schema declared.

{"date":"2026-02-03","latitude":17.385044,"longitude":78.486671}
post_vedic_astrology_parallels ~291

Calculate planetary declinations and find parallels (same declination) and contraparallels (opposite declination). Parallels are considered equivalent to conjunctions in strength, contraparallels to oppositions. Returns declination for each planet and all parallel/contraparallel aspects. Declination parallels API, planetary declination calculator, contraparallel aspects.

NameTypeReqDescription
compactbooleanSet 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.
datestringyesDate in YYYY-MM-DD format. Planetary declinations are calculated for this date to find parallel and contraparallel aspects.
latitudenumberyesObserver latitude in decimal degrees. Used for topocentric declination corrections.
longitudenumberyesObserver longitude in decimal degrees. Affects local time context for declination calculations.
orbnumberOrb in degrees for parallel/contraparallel detection. Defaults to 1.5°.
timestringyesTime in HH:MM:SS format (24-hour). Exact time affects declination values, especially for the fast-moving Moon.
timezoneTimezone offset from UTC in hours. Defaults to 5.5 (IST).

No output schema declared.

{"date":"2026-02-03","latitude":17.385044,"longitude":78.486671,"time":"12:00:00"}
post_vedic_astrology_parallels_monthly ~324

Find all declination parallel and contraparallel events between the 7 visible planets for a given month. Parallels occur when two planets share the same celestial declination (equivalent to conjunction in strength). Contraparallels occur at opposite declinations (equivalent to opposition). Scanned daily at noon UTC. Omit year and month to get the month in progress, so a published parallel calendar stays current without a redeploy. Essential for advanced transit analysis and hidden aspect discovery. Monthly declination parallels API, planetary parallel ephemeris, contraparallel event calendar.

NameTypeReqDescription
compactbooleanSet 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.
langstringResponse 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…
monthintegerMonth number (1-12) for parallel analysis. Defaults to the current month (UTC).
timezoneTimezone offset from UTC in hours. Output times are converted to this timezone. Defaults to 0 (UTC).
yearintegerYear for monthly parallel analysis (1900-2100). Defaults to the current year (UTC).

No output schema declared.

{}
post_vedic_astrology_planetary_positions ~768

Get simplified planetary positions (graha positions) for all 9 planets (Sun through Ketu) plus Ascendant (Lagna). Real-time planet transit calculator for Vedic astrology. Navagraha positions API with nakshatra, pada, and rashi details. Includes house number placement using Whole Sign house system from Lagna. Faster response for basic planetary data without full chart structure. Perfect for planetary alignment tracking, daily transit updates, and astrology widgets.

NameTypeReqDescription
ayanamsastringSidereal 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…
ayanamsaValuenumberCustom 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.
compactbooleanSet 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.
datestringyesBirth 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…
langstringResponse 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…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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…
timezoneTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so…

No output schema declared.

{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_planetary_positions_monthly ~364

Get daily sidereal ecliptic positions for all 9 Vedic planets (Navagraha) for an entire month. Returns longitude, zodiac sign, degree within sign, and retrograde status for each planet on each day. Calculated at noon UTC. Omit year and month to get the month in progress, so a published ephemeris page stays current without a redeploy. Essential for ephemeris generation, transit tracking, and planetary movement visualization. Monthly planetary ephemeris API, sidereal position table, daily graha gochara positions, ecliptic longitude calculator.

NameTypeReqDescription
compactbooleanSet 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.
coordinateSystemstringCoordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defau…
langstringResponse 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…
monthintegerMonth number (1-12) for ephemeris. Defaults to the current month (UTC).
yearintegerYear for monthly ephemeris (1900-2100). Defaults to the current year (UTC).

No output schema declared.

{}
post_vedic_astrology_shadbala ~811

Calculate complete Shadbala (six-fold planetary strength) per Brihat Parashara Hora Shastra (BPHS) and BV Raman Graha and Bhava Balas. Returns all 6 strength components (Sthana Bala, Dig Bala, Kala Bala, Chesta Bala, Naisargika Bala, Drik Bala) plus Ishta Phala, Kashta Phala, strength ratio, and relative ranking for all 7 classical planets. Essential for evaluating planetary strength in Vedic birth chart analysis, dasha prediction, transit interpretation, and yoga assessment. Shadbala calculator API, planetary strength Vedic astrology, graha bala, Ishta Kashta Phala.

NameTypeReqDescription
ayanamsastringSidereal 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…
ayanamsaValuenumberCustom 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.
compactbooleanSet 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.
datestringyesBirth 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…
langstringResponse 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…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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…
timezoneTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so…

No output schema declared.

{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_transit ~525

Analyze planetary transits (Gochar) over natal chart positions. Each transiting graha comes back with TWO whole-sign house numbers, because the two readings answer different questions: houseFromMoon is counted from the natal Moon sign (Janma Rashi), which is the reference classical Gochara uses, and natalHouse is counted from the Lagna. Also returns graha drishti onto the natal grahas (7th for every graha, plus Mars 4th and 8th, Jupiter 5th and 9th, Saturn 3rd and 10th), degree-based angular aspects with orbs, the Gochara Kaksha verdict, and highlighted transits from the slow-moving grahas (Jupiter, Saturn, Rahu, Ketu). Essential for timing predictions, event forecasting, and understanding current planetary influences. Transit analysis API, gochar calculator, vedic transit predictions, Chandra Lagna gochara, graha drishti.

NameTypeReqDescription
birthDatestringyesBirth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.
birthTimestringyesBirth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.
compactbooleanSet 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.
coordinateSystemstringCoordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defau…
latitudenumberyesObserver latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.
longitudenumberyesObserver longitude in decimal degrees. Affects local sidereal time for Lagna and house calculations.
timezoneTimezone offset from UTC in hours. Defaults to 5.5 (IST).
transitDatestringyesTransit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.
transitTimestringTransit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.

No output schema declared.

{"birthDate":"1990-07-04","birthTime":"10:12:00","latitude":17.385044,"longitude":78.486671,"transitDate":"2026-02-03"}
post_vedic_astrology_transit_monthly ~388

Get all planetary sign (rashi) changes for a given month. Shows when each planet transitions from one zodiac sign to another. Covers all 9 Vedic planets: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. Includes starting positions at the beginning of the month. Omit year and month to get the month in progress, so a published gochar calendar stays current without a redeploy. Essential for transit prediction, monthly horoscope generation, and muhurta planning. Monthly planetary transit API, gochar calendar, rashi parivartan dates.

NameTypeReqDescription
compactbooleanSet 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.
coordinateSystemstringCoordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defau…
langstringResponse 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…
monthintegerMonth number (1-12) for transit analysis. Defaults to the current month (UTC).
timezoneTimezone offset from UTC in hours. Output times are converted to this timezone. Defaults to 0 (UTC).
yearintegerYear for monthly transit analysis (1900-2100). Defaults to the current year (UTC).

No output schema declared.

{}
post_vedic_astrology_upagraha ~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.

NameTypeReqDescription
ayanamsastringSidereal 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…
ayanamsaValuenumberCustom 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.
compactbooleanSet 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.
datestringyesBirth 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…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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…
timezoneTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so…

No output schema declared.

{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_yoga_detect ~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…

NameTypeReqDescription
ayanamsastringSidereal 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…
ayanamsaValuenumberCustom 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.
compactbooleanSet 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.
datestringyesBirth 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…
langstringResponse 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…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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…
timezoneTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so…

No output schema declared.

{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
Common questions

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 56 tools: post_vedic_astrology_birth_chart, post_vedic_astrology_navamsa, post_vedic_astrology_divisional_chart, post_vedic_astrology_compatibility, post_vedic_astrology_planetary_positions, and 51 more. Their descriptions and schemas cost roughly 38,327 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.