@openephemeris/mcp-server 4.14.2 → 4.15.0

package/CHANGELOG.md

@@ -7,6 +7,37 @@ Version numbering follows [Semantic Versioning](https://semver.org/).
 
 ---
 
+## [4.15.0] — 2026-09-03
+
+### Added
+- **`electional_angle_crossings` gains `natal_datetime`.** Pass a zoned natal instant and the search
+  finds when the **secondary-progressed** positions of Sun, Moon, Mercury, Venus, Mars and the lunar
+  nodes reach an angle at the place — the same body set and day-for-a-year formula the hybrid CCG
+  transit map draws with — while slower bodies stay transits. Progressed crossings carry
+  `progressed: true` and `search_summary.progression` names the mode, the natal instant and the
+  bodies progressed. Omit the parameter for the plain transit search, which is unchanged.
+
+## [4.14.3] — 2026-09-02
+
+### Fixed
+- **`ephemeris_transits` silently dropped requested `asc`/`mc`/`dsc`/`ic` natal points.** The tool
+  matched `natal_points` against `/ephemeris/natal-chart`'s angle field names
+  (`ascendant`/`midheaven`/`descendant`/`imum_coeli`), which never matched the short forms the
+  tool itself documents — so a search for transits to the Ascendant silently returned zero hits,
+  with `success: true` and no indication anything was dropped. Added alias resolution both ways,
+  plus an `unresolved_points` field so a genuine mismatch surfaces instead of hiding.
+- **`ephemeris_progressed_chart` hardcoded `subject.name` to `"Progressed Subject"`** on both the
+  natal and progressed blocks of the response, so no consumer could tell them apart by name. Now
+  an optional `name` argument, defaulting to a neutral label.
+
+### Added
+- `/ephemeris/progressed` responses now include `metadata.angle_method`
+  (`chart_for_progressed_moment` or `solar_arc_directed`), naming which algorithm produced the
+  progressed angles — previously undeclared and silently implied by
+  `progression_options.method`, which only ever described planetary progression.
+
+---
+
 ## [4.14.2] — 2026-09-01
 
 ### Fixed

package/dist/tools/specialized/electional.js

@@ -1,7 +1,7 @@
 import { registerTool, validateRequired } from "../index.js";
 import { getActiveClient } from "../../backend/client.js";
 import { OUTPUT_SCHEMA_JSON } from "../output-schemas.js";
-import { WINDOW_DATE_DESC } from "../datetime.js";
+import { DATETIME_DESC, WINDOW_DATE_DESC, localToUtcIso, timezoneProperty } from "../datetime.js";
 // All electional endpoints are GET endpoints with query params.
 // GET /electional/find-window — already existed, keeping it
 registerTool({
@@ -279,6 +279,10 @@ registerTool({
         "Crossing times use the same in-mundo geometry as the astrocartography line engine, so casting a " +
         "map at a returned moment puts that line through the query point. Circumpolar cases (a body that " +
         "never rises or never sets at that latitude) simply return no event.\n\n" +
+        "PROGRESSED (hybrid) lines: pass natal_datetime to search the SECONDARY-PROGRESSED positions of " +
+        "Sun, Moon, Mercury, Venus, Mars and the lunar nodes — the same body set and formula the CCG hybrid " +
+        "transit map (/acg/ccg mode=ccg_hybrid) draws with; every other body stays a transit. Progressed " +
+        "crossings carry progressed: true and search_summary.progression names what was progressed.\n\n" +
         "CREDIT COST: 5 credits per call.\n\n" +
         "EXAMPLE: When does Mercury cross the Descendant over Warsaw on 2026-07-30?\n" +
         "  latitude=52.2297, longitude=21.0122, bodies='Mercury', angles='DC',\n" +
@@ -320,6 +324,14 @@ registerTool({
                 type: "number",
                 description: "Maximum number of crossing events to return (default 5000).",
             },
+            natal_datetime: {
+                type: "string",
+                description: "Optional natal (birth) instant. When given, Sun, Moon, Mercury, Venus, Mars and the lunar " +
+                    "nodes are secondary-progressed from it (day-for-a-year) and the search finds when their " +
+                    "PROGRESSED position reaches the angle — the line a hybrid CCG map paints. Slow bodies " +
+                    "(Jupiter outward) are unaffected. Omit for the plain transit search. " + DATETIME_DESC,
+            },
+            natal_timezone: timezoneProperty("the natal birth location", "Europe/London"),
             format: {
                 type: "string",
                 enum: ["json", "llm"],
@@ -349,6 +361,11 @@ registerTool({
             query.refraction_correction = args.refraction_correction;
         if (args.max_results !== undefined)
             query.max_results = args.max_results;
+        // A naive birth time plus its zone is a legitimate call (the datetime
+        // contract); the API's GET takes one zoned instant, so resolve here.
+        if (args.natal_datetime) {
+            query.natal_datetime = localToUtcIso("natal_datetime", args.natal_datetime, args.natal_timezone, "natal_timezone");
+        }
         if (args.format)
             query.format = args.format;
         return await getActiveClient().request("GET", "/electional/angle-crossings", {

package/dist/tools/specialized/progressed.js

@@ -36,6 +36,10 @@ registerTool({
                 enum: ["secondary", "solar_arc", "tertiary"],
                 description: "Progression method. Defaults to 'secondary' (1 day = 1 year).",
             },
+            name: {
+                type: "string",
+                description: "Optional label for the subject, echoed back in both natal_subject and progressed_subject. Defaults to a generic label if omitted.",
+            },
             include_aspects: {
                 type: "boolean",
                 description: "Whether to include aspect grid in the response. Default false.",
@@ -67,7 +71,10 @@ registerTool({
         assertZonedDatetime("target_datetime", args.target_datetime);
         const body = {
             subject: {
-                name: "Progressed Subject",
+                // Echoed verbatim into both natal_subject.name and progressed_subject.name
+                // by the API (same person, two instants) — never a role-specific label
+                // like "Progressed Subject", which would be wrong on the natal block.
+                name: args.name || "Subject",
                 birth_datetime: { iso: args.birth_datetime },
                 birth_location: {
                     latitude: { decimal: args.birth_latitude },

package/dist/tools/specialized/transits.js

@@ -96,6 +96,7 @@ registerTool({
         const wantedPoints = args.natal_points
             ? new Set(args.natal_points.map((p) => p.toLowerCase()))
             : CORE_BODIES_DEFAULT;
+        const resolvedPoints = new Set();
         for (const planet of planetArray) {
             const name = (planet.name || planet.id || "").toLowerCase();
             const lon = planet.longitude ?? planet.ecliptic_longitude ?? planet.lon;
@@ -105,26 +106,54 @@ registerTool({
                 continue;
             targetDegrees.push(Math.round(lon * 100) / 100);
             natalPositionMap[name] = lon;
+            resolvedPoints.add(name);
         }
-        // Extract angles (ASC, MC) only when explicitly requested
+        // Extract angles (ASC, MC, DSC, IC) only when explicitly requested.
+        // /ephemeris/natal-chart names these "ascendant", "midheaven", "descendant",
+        // "imum_coeli" — but the short forms below are what this tool documents and
+        // what natal_points is usually given as, so map both directions or a caller
+        // asking for "asc" silently gets nothing back (no error, no natal_positions
+        // entry) even though the point exists in the natal chart.
         if (args.natal_points) {
+            const ANGLE_ALIASES = {
+                ascendant: "asc",
+                asc: "ascendant",
+                midheaven: "mc",
+                mc: "midheaven",
+                descendant: "dsc",
+                dsc: "descendant",
+                desc: "descendant",
+                imum_coeli: "ic",
+                ic: "imum_coeli",
+            };
             const angles = natalResult?.angles || natalResult?.data?.angles;
             if (angles) {
                 const angleEntries = Array.isArray(angles)
                     ? angles
                     : Object.entries(angles).map(([k, v]) => ({ name: k, ...(typeof v === "object" ? v : { longitude: v }) }));
                 for (const angle of angleEntries) {
-                    const name = (angle.name || angle.id || "").toLowerCase();
+                    const apiName = (angle.name || angle.id || "").toLowerCase();
                     const lon = angle.longitude ?? angle.ecliptic_longitude ?? angle.lon;
                     if (typeof lon !== "number" || !isFinite(lon))
                         continue;
-                    if (!wantedPoints.has(name))
+                    const matchedAs = wantedPoints.has(apiName)
+                        ? apiName
+                        : (ANGLE_ALIASES[apiName] && wantedPoints.has(ANGLE_ALIASES[apiName]))
+                            ? ANGLE_ALIASES[apiName]
+                            : null;
+                    if (!matchedAs)
                         continue;
                     targetDegrees.push(Math.round(lon * 100) / 100);
-                    natalPositionMap[name] = lon;
+                    natalPositionMap[matchedAs] = lon;
+                    resolvedPoints.add(matchedAs);
                 }
             }
         }
+        // Any requested point that never turned up in natal-chart planets or angles —
+        // surface it instead of silently returning fewer targets than asked for.
+        const unresolvedPoints = args.natal_points
+            ? args.natal_points.filter((p) => !resolvedPoints.has(p.toLowerCase()))
+            : [];
         // Hard cap: never send more than 12 target degrees
         const MAX_TARGETS = 12;
         if (targetDegrees.length > MAX_TARGETS) {
@@ -162,6 +191,7 @@ registerTool({
         // Return combined context so the LLM knows what natal positions were targeted
         return {
             natal_positions: natalPositionMap,
+            ...(unresolvedPoints.length > 0 ? { unresolved_points: unresolvedPoints } : {}),
             target_degrees_used: effectiveTargets,
             aspect_angle: args.aspect_angle ?? 0,
             transit_results: transitResult,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openephemeris/mcp-server",
-  "version": "4.14.2",
+  "version": "4.15.0",
   "description": "Model Context Protocol server for the Open Ephemeris astronomical computation API",
   "type": "module",
   "main": "dist/index.js",