Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Bhrigu Bindu (Destiny Point)

get_bhrigu_bindu

Bhrigu Bindu = midpoint of natal Moon and Rahu, a karmic destiny point that activates strongly when transited by slow planets (Saturn, Jupiter, Rahu, Ketu). Returns BB's longitude, sign, house, star/sub lord, and a chronological list of upcoming slow-planet crossings over BB across the next N years (default 10). Modern KP / cross-system; framed as karmic windows, not deterministic events.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa system. Defaults to kp.
query_datestringNoISO date to begin scan from (default: now).
scan_yearsnumberNoYears forward to scan (default: 10).

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_bhrigu_bindu",
    "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.