Home / MCP registry index / io.astrotune/jyotish-vedic-astrology
AstroTune — Vedic astrology (Jyotish)
io.astrotune/jyotish-vedic-astrology in the official MCP registry.
Endpoint https://astrotune.io/mcp.
The registry describes it as: Jyotish charts, vargas, dashas, panchang, transits, matching. Place by name, no API key.
We read its 21 tools on 2026-10-25. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
find_place natal_chart varga_chart birth_time_window verify_external_chart compare_methods astro_context panchanga sky_now dasha_timeline ashtakavarga chart_transits compatibility muhurta_search research_query life_events corpus_search explain_chart_section what_we_calculate feedback_add feedback_list
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-astrotune-jyotish-vedic-astrology)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.