Home / MCP registry index / co.cosmicchemistry/vedic-astrology
Cosmic Chemistry
co.cosmicchemistry/vedic-astrology in the official MCP registry.
Endpoint https://cosmicchemistry.co/mcp.
The registry describes it as: Free Vedic astrology: birth chart, dasha, Sade Sati, Saturn return, panchang, planetary hours.
We read its 21 tools on 2026-10-22. 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
vedic_birth_chart vedic_rising_sign moon_sign_nakshatra sade_sati_check saturn_return_dates current_dasha manglik_check planet_in_house_meaning daily_panchang festival_and_vrat_dates moon_today planetary_hours mercury_retrograde venus_retrograde chara_karakas divisional_chart indu_lagna_money_sign vedic_and_western_signs vehicle_purchase_dates birth_chart_compatibility mahadasha_meaning
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/co-cosmicchemistry-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.