Home / MCP registry index / com.jagannathahora/vedic-astrology
Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang)
com.jagannathahora/vedic-astrology in the official MCP registry.
Endpoint https://jagannatha-hora-359167915530.europe-west1.run.app/mcp.
The registry describes it as: Vedic astrology (Jyotish): birth charts, divisional charts, dashas, yogas, transits, panchang
We read its 34 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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
generate_horoscope get_amsa_rulers get_arudha_padas get_ashtakavarga get_bhava_bala get_chandra_arudhas get_chara_karakas get_dasha get_divisional_chart get_doshas get_gochara get_gochara_range get_graha_arudhas get_house_varnadas get_longevity get_longevity_reference get_marriage_match get_muhurta get_nakshatra_pada get_other_bala get_planet_ingress get_planetary_states get_sahams get_saturn_transit get_shad_bala get_special_lagnas get_sphutas get_surya_arudhas get_surya_siddhanta_chart get_upagrahas get_vaiseshikamsa_bala get_vimsopaka_bala get_yogas list_divisional_charts
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-jagannathahora-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.