Advanced techniques

Cuspal Interlink Event Score (Khullar)

get_cuspal_interlink_score

[KP extended, S.P. Khullar's Cuspal Interlink theory] For one event, the interlinks between its own cusps: where one required cusp's sub lord is another's sub lord (CSL_to_CSL) or star lord (CSL_to_StarLord), with a density score. Reading links ACROSS cusps is Khullar's method; KSK judges a matter by the cuspal sub lord's own significations (KP Reader 5 canon p.195), so this is a successor's reading beside the KSK verdict, not part of it. Returns '{ school, author, system, divergencePoint, event, requiredHouses, relevantInterlinks: [{ houseA, houseB, linkType, sharedPlanet, score }], totalScore, maxPossibleScore, scoreRatio, verdict, summary, scoreProvenance }'. The 2/1 weights, the maximum and the 40%/20% bands are Lumin's ('scoreProvenance'); read 'relevantInterlinks', which carry the method. For every cusp against every other, get_interlink_strength_matrix.

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.
event	event name	No	Event whose cusps to link (default: Marriage).

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