Advanced techniques

Vedha Transit Check (Saturn / Jupiter Obstruction)

get_vedha_transit

Traditional Hindu Gochara obstruction check, NOT a KP verdict. Saturn favourable in 3/6/11 from natal Moon with Vedha at 12/9/5; Jupiter favourable in 2/5/7/9/11 with Vedha at 12/4/3/10/8. Returns each slow planet's house from natal Moon, whether the favourable rule applies, whether the Vedha house is occupied (by which planets), the no-Vedha exceptions (Sun-Saturn, Moon-Mercury), and a final verdict (FAVOURABLE_CLEAR / FAVOURABLE_BUT_VEDHA / NEUTRAL / UNFAVOURABLE_HOUSE). Provenance: the rules are transcribed from KP Reader 5 pp.26-28, where they are presented as the Hindu system, and the SAME BOOK rejects them at p.361 as "useless, meaningless and not universally applicable", warning that reproducing them without saying they fail for most people does harm. Report it as the traditional view and say the source disputes it; never let it decide a KP verdict on its own, and prefer get_transit_analysis and get_transit_timing_hierarchy for that. Books: KP Reader 5 pp.26-28 for the rules, p.361 for the rejection.

Parameters

Name	Type	Required	Description
birth_datetime	string	Yes	Birth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitude	number	Yes	Birth location latitude. Range: -90 to 90.
longitude	number	Yes	Birth location longitude. Range: -180 to 180.
utc_offset_minutes	number	Yes	UTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsa	enum: kp \| kp_new \| lahiri \| raman \| true_chitra \| khullar	No	Ayanamsa system. Defaults to kp.
query_date	string	No	ISO date to evaluate against (default: now).

Example call

Send the request as a standard MCP tools/call:

http

POST https://mcp.lumin.guru/mcp
Authorization: Bearer mcp_yourkey...
Accept: application/json, text/event-stream
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_vedha_transit",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp"
    }
  }
}

Birth data

This tool requires birth data on every call. The MCP server is stateless, so calling set_birth_profile first validates the data and returns the reading plan, but it does not store anything. Repeat the same five fields here.