AstroTune — Vedic astrology (Jyotish)
REMOTE · ASTROTUNE.IO · SCANNED SEP 29
Jyotish charts, vargas, dashas, panchang, transits, matching. Place by name, no API key.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3198 tokens (~145/item across 22 items; 21 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management18
- Stability check failed: schema churn in the 7 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 10% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the AstroTune — Vedic astrology (Jyotish) MCP server?
AstroTune — Vedic astrology (Jyotish) is a hosted endpoint at https://astrotune.io/mcp, 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 · astrotune.io
claude mcp add --transport http io-astrotune-jyotish-vedic-astrology 'https://astrotune.io/mcp'
{
"mcpServers": {
"io-astrotune-jyotish-vedic-astrology": {
"url": "https://astrotune.io/mcp"
}
}
} {
"servers": {
"io-astrotune-jyotish-vedic-astrology": {
"type": "http",
"url": "https://astrotune.io/mcp"
}
}
} [mcp_servers.io-astrotune-jyotish-vedic-astrology] url = "https://astrotune.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-astrotune-jyotish-vedic-astrology": {
"type": "remote",
"url": "https://astrotune.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-astrotune-jyotish-vedic-astrology --url 'https://astrotune.io/mcp' --transport streamable-http
mcp_servers:
io-astrotune-jyotish-vedic-astrology:
url: "https://astrotune.io/mcp" {
"McpServers": {
"io-astrotune-jyotish-vedic-astrology": {
"Transport": "http",
"Url": "https://astrotune.io/mcp"
}
}
} assistant mcp add io-astrotune-jyotish-vedic-astrology -t streamable-http -u 'https://astrotune.io/mcp'
{
"mcpServers": {
"io-astrotune-jyotish-vedic-astrology": {
"type": "http",
"url": "https://astrotune.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 0
- Tool “compatibility” rewrote its description, which is the text the model reads security
- Tool “panchanga” rewrote its description, which is the text the model reads security
- Server version: 1.21.f6f6d6f1 → 1.21.ceec8c18 functional
- 28 Sept 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
- 27 Sept 26 0
- Tool “natal_chart” rewrote its description, which is the text the model reads security
- Server version: 1.21.e16fa74a → 1.21.29e7d0b5 functional
- “ashtakavarga” reworded the description of “chart_id” cosmetic
- “chart_transits” reworded the description of “chart_id” cosmetic
- “dasha_timeline” reworded the description of “chart_id” cosmetic
- 26 Sept 26 0
- Server version: 0.15.1 → 1.21.e16fa74a functional
- New tool “ashtakavarga” functional
- 25 Sept 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.03 → fail ▼ security
- Tool “chart_transits” rewrote its description, which is the text the model reads security
- Tool “compare_methods” rewrote its description, which is the text the model reads security
- Tool “dasha_timeline” rewrote its description, which is the text the model reads security
- Tool “research_query” rewrote its description, which is the text the model reads security
- Tool “sky_now” rewrote its description, which is the text the model reads security
- Tool “what_we_calculate” rewrote its description, which is the text the model reads security
- Schema quality: 4706 → 5283 ▼ functional
- “feedback_add” added a required parameter “title”, so existing callers break ▼ functional
- “compare_methods” made “ayanamsas” required, so existing callers break ▼ functional
- “compare_methods” changed the type of “ayanamsas”: array|null → array ▼ functional
- Server version: 0.12.0 → 0.15.1 functional
- New tool “explain_chart_section” functional
- “what_we_calculate” added an optional parameter “lang” cosmetic
- “chart_transits” reworded the description of “chart_id” cosmetic
- “dasha_timeline” reworded the description of “chart_id” cosmetic
- 23 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Sept 26 64
First indexed and scored.
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 29 Sept 2026 · Probed https://astrotune.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=astrotune.io | CN=WE1,O=Google Trust Services,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 27e26f5dca50372113d24e6f1cd3178d |
| SANs: astrotune.io, *.astrotune.io | ||||||
| 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 astrotune.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| astrotune.io. | 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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://www.google-analytics.com https://www.googletagmanager.com; font-src 'self' data:; connect-src 'self' https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com https://www.googletagmanager.com https://cloudflareinsights.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://astrotune.io/mcp | Verified | 200 | |
| http (plaintext) | http://astrotune.io/mcp | HTTPS enforced | 301 | https://astrotune.io/mcp |
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 →
ashtakavarga ~155
Аштакаварга (Парашари): бинду по 12 знакам для семи грах (BAV) и сводная SAV одним ответом. Нужно время рождения: лагна — один из восьми источников.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | Из natal_chart: date, time, place и аянамша — из карты; без него — поля и Lahiri. Поле против карты — отказ input_conflict. |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
astro_context ~139
Вопрос человека о карьере, браке, деньгах, здоровье или переезде: одним вызовом дома темы со знаком и управителем, грахи в них, варга темы, текущий период. topic выбираете вы по вопросу. Толкования нет — вывод делайте из этих данных.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
birth_time_window ~140
Время рождения известно окном («между 13 и 16», до 6 ч в одних сутках): что одинаково во всём окне, какие лагны возможны и с какого времени, что неопределимо. Не ректификация: одну лагну за человека не выбирать.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time_from | string | yes | – |
| time_to | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
chart_transits ~189
Транзиты по карте человека: где грахи сейчас и когда сменят знак (по умолчанию Сатурн, Юпитер, Раху, Кету; другие — в bodies, для Луны years до 0.15), плюс отрезки ретроградности — «когда Меркурий ретроградный». Время рождения необязательно.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array|null | – | – |
| chart_id | string|null | – | Из natal_chart: date, time, place и аянамша — из карты; без него — поля и Lahiri. Поле против карты — отказ input_conflict. |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
| years | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_methods ~142
Одна карта в 2–5 аянамшах (ayanamsas, напр. ["Lahiri", "Raman", "KP"]): меняется ли знак лагны, Луны или накшатра. Для «почему на другом сайте другая лагна», когда чужих чисел нет; есть их числа — verify_external_chart.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsas | array | yes | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compatibility ~181
Совместимость двух людей по аштакуте (kundli matching, 8 кут): балл и причина по каждой куте и итог. Без времени знак Луны бывает двояким: points — min…max по combinations (у каждого сочетания знаков свой итог и куты), kutas — разбор combinations[0]; при однозначных данных min=max. Процента нет — не вычисляйте его.
| Name | Type | Req | Description |
|---|---|---|---|
| first_date | string | yes | – |
| first_geonameid | integer|null | – | – |
| first_place | string|null | – | – |
| first_time | string|null | – | – |
| lang | string | – | – |
| second_date | string | yes | – |
| second_geonameid | integer|null | – | – |
| second_place | string|null | – | – |
| second_time | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
corpus_search ~96
Какие известные люди (корпус 76 тыс.) родились с этой грахой в этом знаке и сколько их. znak 0…11, 0 — Овен. В ответе два числа — подходящие и неопределимые; называйте оба. Сравнить группу со всеми — research_query.
| Name | Type | Req | Description |
|---|---|---|---|
| graha | string | yes | – |
| lang | string | – | – |
| znak | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
dasha_timeline ~212
Периоды жизни (вимшоттари-даши): какой идёт сейчас и что дальше; depth 1–3 — маха-, антар-, пратьянтардаша. Нужно время рождения. Прошлые годы — отрезком from_date/to_date; full=true — весь круг 120 лет, тяжёлый. Человек назвал даты своих событий — это life_events.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_id | string|null | – | Из natal_chart: date, time, place и аянамша — из карты; без него — поля и Lahiri. Поле против карты — отказ input_conflict. |
| date | string|null | – | – |
| depth | integer | – | – |
| from_date | string|null | – | – |
| full | boolean | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
| to_date | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
explain_chart_section ~126
Что значит в карте человека его лагна, Луна или текущая даша (section) — объяснение словами с источником; у каждого утверждения уровень calculated или tradition. Без предсказаний и советов. Нужно время рождения.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| section | string | yes | – |
| time | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
feedback_add ~160
Сообщить о проблеме САМОГО сервера, не о расчётах: инструмент повёл себя не как описано, не хватило параметра или поля, непонятный отказ или описание. Пишите конкретно: инструмент, аргументы, что ждали и что пришло.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | что звали, с какими аргументами, что ждали, что пришло |
| kind | string | – | – |
| meta | string | – | подробности одной строкой: аргументы вызова, текст отказа |
| title | string | yes | суть одной фразой, от 10 знаков |
| tool | string | – | имя инструмента; пусто — о сервере целиком |
Structured output declared, but exposes no named fields.
No examples provided.
feedback_list ~92
Что уже сообщено об этом сервере и ответы на это. Смотрите перед feedback_add.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | проблема, доработка или вопрос |
| limit | integer | – | – |
| q | string | – | слово в заголовке или тексте |
| show | string | – | – |
| status | string | – | только с этим статусом |
| tool | string | – | только про этот инструмент |
Structured output declared, but exposes no named fields.
No examples provided.
find_place ~74
Место по названию на любом языке («Koln», «Ленинград») → geonameid для расчётов. date — чтобы взять смещение UTC тех лет.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | – |
| lang | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
life_events ~173
ЧЕЛОВЕК НАЗВАЛ ДАТЫ СВОИХ СОБЫТИЙ («переехал в феврале 2018», «женился в 2021»): какие махадаша и антардаша шли на каждую, одним вызовом. День не обязателен: 2018-02 или 2018. Нужно время рождения. Весь ряд периодов — dasha_timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| events | array | yes | события человека: дата и подпись |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
muhurta_search ~121
Хорошие дни и часы на отрезке до 31 суток («хорошие даты с 1 по 20 октября»): по суткам — годен или снят каким правилом, благие чогхадии, абхиджит. Общий отбор, не мухурта под конкретное дело.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string|null | – | – |
| date_from | string|null | – | – |
| date_to | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
natal_chart ~188
Натальная карта (джйотиш): грахи по знакам и домам, лагна, накшатра Луны, текущая даша. Место — place или geonameid. Время необязательно: без него нет лагны, домов и даш. detail: preview (коротко), normal, full. Отдаёт chart_id: его дают дальше вместо даты, времени и места; поле против карты — отказ input_conflict.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| detail | string | – | – |
| geonameid | integer|null | – | – |
| house_system | string | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| podrobno | boolean | – | – |
| time | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
panchanga ~129
Панчанга дня в любом месте (city или geonameid, не оба): титхи, накшатра, йога, карана, вара со временем смены, восход, закат, раху-каал, гулика, ямаганда; detailed — чогхадии. Без date — сегодня.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string|null | – | – |
| date | string|null | – | – |
| detailed | boolean | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| podrobno | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
research_query ~141
«Чаще ли у предпринимателей Юпитер в Стрельце, чем вообще»: доля грахи в знаке (znak 0…11, 0 — Овен) в группе по занятию (occupation словом) против доли во всём корпусе известных людей, с интервалом. Только знаки, домов нет.
| Name | Type | Req | Description |
|---|---|---|---|
| graha | string | yes | – |
| lang | string | – | – |
| occupation | string | – | название занятия: «писатель», «politician» |
| occupation_qid | string | – | идентификатор Wikidata, если он известен точно |
| znak | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sky_now ~45
Небо в эту минуту, без карты человека: грахи по знакам, накшатра Луны с падой, титхи.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
varga_chart ~158
Дробная карта (варга): D9 навамша, D10 дашамша, D2, D3, D7, D12 — один инструмент, нужная задаётся в varga. Лагна варги, грахи по знакам, варготтама. Нужно время рождения. Прочие варги не считаем (not_available в ответе).
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lang | string | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
| varga | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_external_chart ~178
Человек назвал ЧУЖИЕ числа (другой сайт, астролог), и они не сходятся с нашей картой: ищет причину — аянамша или час (декретное, летнее время, пояс). Знаки номером 0 Овен…11 Рыбы, накшатра 1…27. Кто прав, не решает.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | – |
| chart_id | string|null | – | – |
| date | string|null | – | – |
| geonameid | integer|null | – | – |
| lagna_sign | integer|null | – | – |
| lang | string | – | – |
| moon_sign | integer|null | – | – |
| nakshatra | integer|null | – | – |
| place | string|null | – | – |
| time | string|null | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
what_we_calculate ~47
Что этот сервер считает и чего НЕ считает. Спросите, прежде чем обещать человеку метод; недостающее не досчитывайте сами.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the AstroTune — Vedic astrology (Jyotish) MCP server?
AstroTune — Vedic astrology (Jyotish) is an MCP server listed in the public MCP registry as io.astrotune/jyotish-vedic-astrology. Jyotish charts, vargas, dashas, panchang, transits, matching. Place by name, no API key. This page covers its hosted endpoint (https://astrotune.io/mcp).
Is the AstroTune — Vedic astrology (Jyotish) MCP server safe to use?
AstroTune — Vedic astrology (Jyotish) scores 67 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 AstroTune — Vedic astrology (Jyotish) MCP server expose?
AstroTune — Vedic astrology (Jyotish) exposes 21 tools: find_place, natal_chart, varga_chart, birth_time_window, verify_external_chart, and 16 more. Their descriptions and schemas cost roughly 2,886 tokens of context every time the server is loaded.
Does the AstroTune — Vedic astrology (Jyotish) MCP server require authentication?
No. We connected to AstroTune — Vedic astrology (Jyotish) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AstroTune — Vedic astrology (Jyotish) MCP server still maintained?
AstroTune — Vedic astrology (Jyotish) is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.