Transit and timing
Transit Crossings
get_transit_crossings
All KP sub-lord boundary crossings for the requested planets within a date window (max 366 days). Uses 1-hour coarse scan + binary-search refinement to minute precision. Returns '{ crossings: [{ planet, crossingTimeUTC, fromKP, toKP, fromSubLord, toSubLord, isNakshatraChange, isSignChange }], totalCrossings, planetsSearched }'.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| startDatetime | string | Yes | Start date (ISO 8601) |
| endDatetime | string | Yes | End date (ISO 8601, max 366 days from start) |
| planets | array<planet name> | No | Planets to track (defaults to all 9). |
Example call
Send the request as a standard MCP tools/call:
http
POST https://mcp.lumin.guru/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_transit_crossings",
"arguments": {
"startDatetime": "...",
"endDatetime": "..."
}
}
}Engine endpoint
This tool delegates to the kp-engine endpoint:
http
POST /v1/kp/transit/crossingsThe engine is a private internal service. All public access flows through the MCP server, which handles auth, rate limiting, and response compaction.