mcp-registry/io.astrotune/jyotish-vedic-astrology · v1.21.7a593463
As of 2026-10-27 00:08 UTC, the Astrotune Jyotish Vedic Astrology MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 7 minutes.
Jyotish charts, vargas, dashas, panchang, transits, matching. Place by name, no API key.
Point your MCP client at this streamable-http endpoint: https://astrotune.io/mcp
125 parameter(s) across 21 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
21 of 21 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
In the last 30 days: 0 tool(s) removed and 14 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. 21 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.astrotune%2Fjyotish-vedic-astrology/fixes
{
"name": "compare_methods",
"description": "Одна карта в 2–5 аянамшах (ayanamsas, напр. [\"Lahiri\", \"Raman\", \"KP\"]): меняется ли знак лагны, Луны или накшатра. Для «почему на другом сайте другая лагна», когда чужих чисел нет; есть их числа — verify_external_chart.",
"inputSchema": {
"type": "object",
"required": [
"ayanamsas"
],
"properties": {
"date": {
"type": [
"string",
"null"
]
},
"lang": {
"enum": [
"ru",
"en"
],
"type": "string",
"default": "ru"
},
"time": {
"type": [
"string",
"null"
]
},
"place": {
"type": [
"string",
"null"
]
},
"chart_id": {
"type": [
"string",
"null"
]
},
"ayanamsas": {
"type": "array",
"items": {
"enum": [
"Aryabhata",
"Deluce",
"FaganBradley",
"GalacticMula",
"Hipparchos",
"KP",
"Lahiri",
"Raman",
"Revati",
"SS_Citra",
"SS_Revati",
"SuryaSiddhanta",
"TrueChitra",
"TruePushya",
"ValensMoon",
"Yukteshwar"
],
"type": "string"
},
"maxItems": 5,
"minItems": 2,
"uniqueItems": true
},
"geonameid": {
"type": [
"integer",
"null"
]
},
"utc_offset": {
"type": [
"string",
"null"
],
"description": "После отказа time_ambiguous: utc_offset из error.choices."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "corpus_search",
"description": "Какие известные люди (корпус 76 тыс.) родились с этой грахой в этом знаке и сколько их. znak 0…11, 0 — Овен. В ответе два числа — подходящие и неопределимые; называйте оба. Сравнить группу со всеми — research_query.",
"inputSchema": {
"type": "object",
"required": [
"graha",
"znak"
],
"properties": {
"lang": {
"enum": [
"ru",
"en"
],
"type": "string",
"default": "ru"
},
"znak": {
"type": "integer",
"maximum": 11,
"minimum": 0
},
"graha": {
"enum": [
"surya",
"chandra",
"budha",
"shukra",
"mangala",
"guru",
"shani",
"rahu",
"ketu",
"sun",
"moon",
"mercury",
"venus",
"mars",
"jupiter",
"saturn"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "explain_chart_section",
"description": "Что значит в карте человека его лагна, Луна или текущая даша (section) — объяснение словами с источником; у каждого утверждения уровень calculated или tradition. Без предсказаний и советов. Нужно время рождения.",
"inputSchema": {
"type": "object",
"required": [
"section"
],
"properties": {
"date": {
"type": [
"string",
"null"
]
},
"lang": {
"enum": [
"ru",
"en"
],
"type": "string",
"default": "ru"
},
"time": {
"type": [
"string",
"null"
]
},
"place": {
"type": [
"string",
"null"
]
},
"section": {
"enum": [
"lagna",
"luna",
"dasha"
],
"type": "string"
},
"ayanamsa": {
"enum": [
"Aryabhata",
"Deluce",
"FaganBradley",
"GalacticMula",
"Hipparchos",
"KP",
"Lahiri",
"Raman",
"Revati",
"SS_Citra",
"SS_Revati",
"SuryaSiddhanta",
"TrueChitra",
"TruePushya",
"ValensMoon",
"Yukteshwar"
],
"type": "string",
"default": "Lahiri"
},
"chart_id": {
"type": [
"string",
"null"
]
},
"geonameid": {
"type": [
"integer",
"null"
]
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/io.astrotune/jyotish-vedic-astrology"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.astrotune/jyotish-vedic-astrology"}) over MCP.
life_events ~364 tokensnatal_chart ~356 tokenscompatibility ~296 tokenschart_transits ~291 tokensastro_context ~284 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%2Fio.astrotune%2Fjyotish-vedic-astrology?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.astrotune%2Fjyotish-vedic-astrology?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.astrotune%2Fjyotish-vedic-astrology.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.astrotune%2Fjyotish-vedic-astrology.svg :target: https://glimind.com/server/mcp-registry%2Fio.astrotune%2Fjyotish-vedic-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:5fb1ad263c812772…, first seen 2026-10-17, included at leaf 10280 of 76,250. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable communication servers · most reliable search 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-27 00:08 UTC, the Astrotune Jyotish Vedic Astrology MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 7 minutes.
Astrotune Jyotish Vedic Astrology MCP server advertises 21 tools, including ashtakavarga, astro_context, birth_time_window, chart_transits, compare_methods.
Point your MCP client at this streamable-http endpoint: https://astrotune.io/mcp
Glimind scanned all 21 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.