Home / MCP registry index / io.github.amarpathak/birthstar
Birthstar Vedic Astrology MCP
io.github.amarpathak/birthstar in the official MCP registry.
Endpoint https://mcp.birthstar.ai/mcp.
The registry describes it as: 30 Vedic Jyotish tools: natal charts, dashas, yogas, nakshatras. Swiss Ephemeris.
We read its 30 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
create_chart get_grahas get_houses get_current_dasha get_dasha_periods get_timeline get_lagna_points get_panchanga get_yogas get_varga get_vimsopaka get_strengths get_ashtakavarga get_aspects get_karakas get_transits get_day_periods get_avasthas get_fixed_stars get_longevity get_compatibility get_doshas get_numerology get_prompt_library describe_chart rectify_birth_time get_account_status health_check server_stats calculate_birth_star
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-amarpathak-birthstar)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.