mcp-registry/com.roxyapi/vedic-astrology · v2.0.0
As of 2026-10-22 12:09 UTC, the Roxyapi Vedic Astrology MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 2 minutes.
Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.
Claude Code
claude mcp add --transport http roxyapi-vedic-astrology-mcp-server https://roxyapi.com/mcp/vedic-astrology
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"roxyapi-vedic-astrology-mcp-server": {
"type": "http",
"url": "https://roxyapi.com/mcp/vedic-astrology"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Loading this server's tool list costs an agent ~60,644 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
20 tool definition(s) exceed ~1,200 tokens each (largest: post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma, ~1,944).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~19,159 tokens every session. How to fix →
58 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
2 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
In the last 30 days: 0 tool(s) removed and 54 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.roxyapi%2Fvedic-astrology/fixes
{
"name": "post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantarda",
"description": "Sookshma dasha API. Returns the 9 Sookshma periods inside a chosen Pratyantardasha, the fourth and finest level of the Vimshottari dasha hierarchy. Completes a full vimshottari drill down from the 120-year cycle to day level timing, typically 3 to 30 days per period. Built for dasha drill down tables, current DBA readouts, and precise event timing in Vedic astrology software.",
"inputSchema": {
"type": "object",
"examples": [
{
"date": "1990-07-04",
"time": "10:12:00",
"latitude": 28.6139,
"longitude": 77.209,
"mahadasha": "Saturn",
"antardasha": "Venus",
"pratyantardasha": "Rahu"
}
],
"required": [
"mahadasha",
"antardasha",
"pratyantardasha",
"date",
"time",
"latitude",
"longitude"
],
"properties": {
"date": {
"type": "string",
"format": "date",
"example": "1990-07-04",
"description": "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 divisional charts (vargas)."
},
"lang": {
"enum": [
"en",
"tr",
"de",
"es",
"hi",
"pt",
"fr",
"ru",
"zh-Hans",
"zh-Hant"
],
"type": "string",
"default": "en",
"example": "en",
"description": "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 English."
},
"time": {
"type": "string",
"format": "time",
"example": "10:12:00",
"description": "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 divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect."
},
"focus": {
"enum": [
"general",
"finance"
],
"type": "string",
"default": "general",
"example": "general",
"description": "Which 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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\"."
},
"compact": {
"type": "boolean",
"default": false,
"description": "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."
},
"ayanamsa": {
"enum": [
"kp-newcomb",
"kp-old",
"lahiri",
"raman",
"custom"
],
"type": "string",
"default": "lahiri",
"example": "lahiri",
"description": "Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses."
},
"latitude": {
"type": "number",
"example": 28.6139,
"maximum": 90,
"minimum": -90,
"description": "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."
},
"nodeType": {
"enum": [
"mean",
"true"
],
"type": "string",
"default": "mean",
"example": "mean",
"description": "Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\"."
},
"timezone": {
"anyOf": [
{
"type": "number",
"maximum": 14,
"minimum": -14
},
{
"type": "string"
}
],
"default": 5.5,
"example": 5.5,
"description": "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 the offset in force at the given date and time. Defaults to 5.5."
},
"longitude": {
"type": "number",
"example": 77.209,
"maximum": 180,
"minimum": -180,
"description": "Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240."
},
"mahadasha": {
"enum": [
"Ketu",
"Venus",
"Sun",
"Moon",
"Mars",
"Rahu",
"Jupiter",
"Saturn",
"Mercury"
],
"type": "string",
"example": "Saturn",
"description": "Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury."
},
"antardasha": {
"enum": [
"Ketu",
"Venus",
"Sun",
"Moon",
"Mars",
"Rahu",
"Jupiter",
"Saturn",
"Mercury"
],
"type": "string",
"example": "Venus",
"description": "Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive."
},
"ayanamsaValue": {
"type": "number",
"example": 24,
"description": "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."
},
"significators": {
"type": "boolean",
"default": false,
"example": false,
"description": "Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above."
},
"pratyantardasha": {
"enum": [
"Ketu",
"Venus",
"Sun",
"Moon",
"Mars",
"Rahu",
"Jupiter",
"Saturn",
"Mercury"
],
"type": "string",
"example": "Rahu",
"description": "Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive."
}
}
},
"annotations": {
"readOnlyHint": true,
"destructiveHint": false
},
"title": "Get all Sookshma dashas for a Mahadasha, Antardasha and Pratyantardasha"
}{
"name": "post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantar_2",
"description": "Prana dasha API for Vedic astrology. Returns the 9 Prana periods inside a chosen Sookshma dasha, the fifth and finest level of the Vimshottari dasha hierarchy. Completes the full vimshottari drill down from the 120-year cycle to hour level timing, typically 20 minutes to 4 days per period depending on the parent Mahadasha. Built for five column dasha drill down tables, muhurta selection, and pinpointing the trigger moment inside an event window already found at the Sookshma level.",
"inputSchema": {
"type": "object",
"examples": [
{
"date": "1990-07-04",
"time": "10:12:00",
"latitude": 28.6139,
"sookshma": "Jupiter",
"longitude": 77.209,
"mahadasha": "Saturn",
"antardasha": "Venus",
"pratyantardasha": "Rahu"
}
],
"required": [
"mahadasha",
"antardasha",
"pratyantardasha",
"sookshma",
"date",
"time",
"latitude",
"longitude"
],
"properties": {
"date": {
"type": "string",
"format": "date",
"example": "1990-07-04",
"description": "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 divisional charts (vargas)."
},
"lang": {
"enum": [
"en",
"tr",
"de",
"es",
"hi",
"pt",
"fr",
"ru",
"zh-Hans",
"zh-Hant"
],
"type": "string",
"default": "en",
"example": "en",
"description": "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 English."
},
"time": {
"type": "string",
"format": "time",
"example": "10:12:00",
"description": "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 divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect."
},
"focus": {
"enum": [
"general",
"finance"
],
"type": "string",
"default": "general",
"example": "general",
"description": "Which 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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\"."
},
"compact": {
"type": "boolean",
"default": false,
"description": "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."
},
"ayanamsa": {
"enum": [
"kp-newcomb",
"kp-old",
"lahiri",
"raman",
"custom"
],
"type": "string",
"default": "lahiri",
"example": "lahiri",
"description": "Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses."
},
"latitude": {
"type": "number",
"example": 28.6139,
"maximum": 90,
"minimum": -90,
"description": "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."
},
"nodeType": {
"enum": [
"mean",
"true"
],
"type": "string",
"default": "mean",
"example": "mean",
"description": "Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\"."
},
"sookshma": {
"enum": [
"Ketu",
"Venus",
"Sun",
"Moon",
"Mars",
"Rahu",
"Jupiter",
"Saturn",
"Mercury"
],
"type": "string",
"example": "Jupiter",
"description": "Sookshma dasha planet name inside that Pratyantardasha, case-insensitive. Every full period contains all 9 lords, so a repeat such as saturn/saturn/saturn/saturn is valid."
},
"timezone": {
"anyOf": [
{
"type": "number",
"maximum": 14,
"minimum": -14
},
{
"type": "string"
}
],
"default": 5.5,
"example": 5.5,
"description": "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 the offset in force at the given date and time. Defaults to 5.5."
},
"longitude": {
"type": "number",
"example": 77.209,
"maximum": 180,
"minimum": -180,
"description": "Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240."
},
"mahadasha": {
"enum": [
"Ketu",
"Venus",
"Sun",
"Moon",
"Mars",
"Rahu",
"Jupiter",
"Saturn",
"Mercury"
],
"type": "string",
"example": "Saturn",
"description": "Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury."
},
"antardasha": {
"enum": [
"Ketu",
"Venus",
"Sun",
"Moon",
"Mars",
"Rahu",
"Jupiter",
"Saturn",
"Mercury"
],
"type": "string",
"example": "Venus",
"description": "Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive."
},
"ayanamsaValue": {
"type": "number",
"example": 24,
"description": "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."
},
"significators": {
"type": "boolean",
"default": false,
"example": false,
"description": "Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above."
},
"pratyantardasha": {
"enum": [
"Ketu",
"Venus",
"Sun",
"Moon",
"Mars",
"Rahu",
"Jupiter",
"Saturn",
"Mercury"
],
"type": "string",
"example": "Rahu",
"description": "Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive."
}
}
},
"annotations": {
"readOnlyHint": true,
"destructiveHint": false
},
"title": "Get all Prana dashas for a Mahadasha, Antardasha, Pratyantardasha and Sookshma"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.roxyapi/vedic-astrology"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.roxyapi/vedic-astrology"}) over MCP.
post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma ~1,944 tokenspost_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha ~1,815 tokenspost_vedic_astrology_compatibility_dashakoot ~1,793 tokenspost_vedic_astrology_compatibility_papasamyam ~1,772 tokenspost_vedic_astrology_dasha_sub_mahadasha_antardasha ~1,766 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.roxyapi%2Fvedic-astrology?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.roxyapi%2Fvedic-astrology?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.roxyapi%2Fvedic-astrology.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.roxyapi%2Fvedic-astrology.svg :target: https://glimind.com/server/mcp-registry%2Fcom.roxyapi%2Fvedic-astrology?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:11a8e5dd1940baa8…, first seen 2026-10-17, included at leaf 14554 of 45,844. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 12:09 UTC, the Roxyapi Vedic Astrology MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 2 minutes.
Roxyapi Vedic Astrology MCP server advertises 58 tools, including get_vedic_astrology_avasthas, get_vedic_astrology_avasthas_id, get_vedic_astrology_kp_ayanamsa, get_vedic_astrology_nakshatras, get_vedic_astrology_nakshatras_id.
Point your MCP client at this streamable-http endpoint: https://roxyapi.com/mcp/vedic-astrology
Glimind scanned all 58 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.