Vedic astrology for AI agents: chart facts, panchang windows, and Guna Milan compatibility.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Grounded synthesis answer to a question, computed from the birth chart through the same accuracy-gated path as the retail chat endpoint (chart-anchor check and rewrite retry inside run_reading). The response envelope carries citation_status and accuracy-gate notes. lang: en or hi (default en).
The question to answer from the chart.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Grounded synthesis answer to a question, computed from the birth chart through the same accuracy-gated path as the retail chat endpoint (chart-anchor check and rewrite retry inside run_reading). The response envelope carries citation_status and accuracy-gate notes. lang: en or hi (default en).
| Argument | Type | Description |
|---|---|---|
| lang | string | |
| question* | string | The question to answer from the chart. |
| birth_data* | object |
{
"type": "object",
"required": [
"question",
"birth_data"
],
"properties": {
"lang": {
"enum": [
"en",
"hi"
],
"type": "string"
},
"question": {
"type": "string",
"description": "The question to answer from the chart."
},
"birth_data": {
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
}
}
}
}Deterministic Vedic chart facts for birth data: lagna, Moon sign/nakshatra, current dasha, planets in houses, house lords, dignities, combustions, D9/D10 ascendants, Sade Sati standing, yogas with classical-text citations, dasha timeline. Pure computation, no LLM. Same output as POST /api/b2b/chart-facts.
| Argument | Type | Description |
|---|---|---|
| tz* | number | string | UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata). |
| dob* | string | Birth date, YYYY-MM-DD. |
| lat* | number | Birth latitude, -90 to 90. |
| lng* | number | Birth longitude, -180 to 180. |
| tob* | string | Birth time, HH:MM (24h). |
{
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
}
}Vimshottari dasha standing and full timeline for birth data: current maha / antar / pratyantar dasha plus every maha-dasha period with start and end dates. Deterministic, no LLM. Same compute path as POST /api/b2b/dasha.
| Argument | Type | Description |
|---|---|---|
| birth_data* | object |
{
"type": "object",
"required": [
"birth_data"
],
"properties": {
"birth_data": {
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
}
}
}
}Dosha screen for birth data: Manglik standing under both conventions (Moon and Lagna), Kaal Sarp detection, Sade Sati phase, and extra classical yogas. Deterministic, no LLM. lang: en or hi (default en). Same compute path as POST /api/b2b/doshas.
| Argument | Type | Description |
|---|---|---|
| lang | string | |
| birth_data* | object |
{
"type": "object",
"required": [
"birth_data"
],
"properties": {
"lang": {
"enum": [
"en",
"hi"
],
"type": "string"
},
"birth_data": {
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
}
}
}
}Structured personalized forecast for birth data — per-area tones, day calendar, ingresses, dasha standing. period: daily (optional date), weekly, monthly (optional year+month), or yearly (optional year). Deterministic engine output, no LLM narration. lang: en or hi (default en). Same compute path as POST /api/b2b/forecast.
| Argument | Type | Description |
|---|---|---|
| date | string | YYYY-MM-DD (daily period only). |
| lang | string | |
| year | integer | Target year (monthly/yearly periods). |
| month | integer | Target month 1-12 (monthly period only). |
| period* | string | |
| birth_data* | object |
{
"type": "object",
"required": [
"birth_data",
"period"
],
"properties": {
"date": {
"type": "string",
"description": "YYYY-MM-DD (daily period only)."
},
"lang": {
"enum": [
"en",
"hi"
],
"type": "string"
},
"year": {
"type": "integer",
"description": "Target year (monthly/yearly periods)."
},
"month": {
"type": "integer",
"description": "Target month 1-12 (monthly period only)."
},
"period": {
"enum": [
"daily",
"weekly",
"monthly",
"yearly"
],
"type": "string"
},
"birth_data": {
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
}
}
}
}Use when a user asks about the Hindu calendar day for a location — tithi, paksha, nakshatra, yoga, karana, vara and its lord, sunrise and sunset, plus Rahu Kaal, Yamaganda, Gulika Kaal and the Choghadiya day/night windows. Needs only a place and a date, so it works without anyone's birth details. Deterministic computation, no LLM. Same compute path as GET /api/panchang.
| Argument | Type | Description |
|---|---|---|
| tz* | number | string | UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata). |
| lat* | number | Birth latitude, -90 to 90. |
| lng* | number | Birth longitude, -180 to 180. |
| date | string | YYYY-MM-DD (default: local today at the location). |
{
"type": "object",
"required": [
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"date": {
"type": "string",
"description": "YYYY-MM-DD (default: local today at the location)."
}
}
}Divisional chart (varga) placements for birth data — all sixteen supported divisions d1,d2,d3,d4,d7,d9,d10,d12,d16,d20,d24,d27,d30,d40,d45,d60. Deterministic, no LLM. Same compute path as POST /api/b2b/varga.
| Argument | Type | Description |
|---|---|---|
| varga* | string | |
| birth_data* | object |
{
"type": "object",
"required": [
"birth_data",
"varga"
],
"properties": {
"varga": {
"enum": [
"d1",
"d2",
"d3",
"d4",
"d7",
"d9",
"d10",
"d12",
"d16",
"d20",
"d24",
"d27",
"d30",
"d40",
"d45",
"d60"
],
"type": "string"
},
"birth_data": {
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
}
}
}
}Vedic compatibility (Guna Milan / Ashtakoota) between two people, 36 points across eight kootas: varna, vashya, tara, yoni, graha_maitri, gana, bhakoot, nadi. Moon nakshatra and rashi for each native are computed from their birth data through the same chart engine as get_chart_facts — do not pass nakshatra/rashi yourself. Deterministic, no LLM. Each koota carries its score, its maximum, and a plain-language reason, so the result is auditable rather than a bare number.
| Argument | Type | Description |
|---|---|---|
| person_a* | object | First native's birth data. |
| person_b* | object | Second native's birth data. |
{
"type": "object",
"required": [
"person_a",
"person_b"
],
"properties": {
"person_a": {
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
},
"description": "First native's birth data."
},
"person_b": {
"type": "object",
"required": [
"dob",
"tob",
"lat",
"lng",
"tz"
],
"properties": {
"tz": {
"type": [
"number",
"string"
],
"description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
},
"dob": {
"type": "string",
"description": "Birth date, YYYY-MM-DD."
},
"lat": {
"type": "number",
"description": "Birth latitude, -90 to 90."
},
"lng": {
"type": "number",
"description": "Birth longitude, -180 to 180."
},
"tob": {
"type": "string",
"description": "Birth time, HH:MM (24h)."
}
},
"description": "Second native's birth data."
}
}
}