Home / MCP registry index / io.github.everyai-com/sahadeva

Sahadeva

io.github.everyai-com/sahadeva in the official MCP registry. Endpoint https://sahadeva.magicteams.ai/mcp. Source: github.com/everyai-com/sahadeva.

The registry describes it as: Vedic astrology MCP: panchanga, kundli matching, muhurta, dashas.

We read its 94 tools on 2026-10-29. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http sahadeva https://sahadeva.magicteams.ai/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "sahadeva": {
      "url": "https://sahadeva.magicteams.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"sahadeva","type":"http","url":"https://sahadeva.magicteams.ai/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

recommend_tools search_locations calculate_chart_from_known_place compare_family_timing calculate_compatibility calculate_relationship_compatibility get_panchanga find_muhurta find_elected_lagna calculate_doshas calculate_kp calculate_jaimini calculate_varshaphal calculate_ayanamsa_chart detect_life_themes consult_jyotishya analyze_chart_topic validate_rule_spec reconstruct_worked_example compare_conventions analyze_house prepare_consultation_intake build_prediction_journal get_planetary_relationship_graph get_natal_panchanga analyze_lal_kitab explore_lal_kitab_sources analyze_lal_kitab_remedies reason_lal_kitab explore_lal_kitab_remedy_catalog get_remedy_catalog suggest_safe_practice calculate_devata_profile analyze_remedies build_remedy_repertoire analyze_transit_activation calculate_strength_profile calculate_ashtakavarga analyze_varga analyze_yogas analyze_special_points analyze_transits calculate_dasha_system analyze_badhaka analyze_arudha_and_upapada audit_reading_evidence explain_chart_sources compare_reading_versions analyze_nakshatra_profile analyze_marriage_structure analyze_career_structure analyze_education_structure analyze_property_and_vehicle analyze_finance_structure analyze_spiritual_path build_claim_evidence_ledger analyze_name find_muhurta_with_natal_fit run_longitudinal_validation generate_full_life_report and 34 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-everyai-com-sahadeva/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-everyai-com-sahadeva)

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.