# AstroWay Forecasting (remote · mcp.astroway.info) Transits, progressions, directions, returns, cosmobiology and evolutionary technique. - Trust score: 77/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-11 ## Components - remote · `mcp.astroway.info`: 77/100 (this document), [markdown](https://verifymcp.io/servers/info-astroway-forecast/mcp-forecast.md), [page](https://verifymcp.io/servers/info-astroway-forecast/mcp-forecast) ## Channel facts - Endpoint: `https://mcp.astroway.info/mcp/forecast` - Transports: `streamable-http` - Auth: `required` - Version: `0.4.3` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-11. - **Endpoint Security**: 89/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 69/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 15243 tokens (~258/item across 59 items; 45 tools + 14 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 17/100 - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 84/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 44% of tool parameters carry a description. - Structured output schemas are declared (91% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 45 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the AstroWay Forecasting MCP server? AstroWay Forecasting is a hosted endpoint at https://mcp.astroway.info/mcp/forecast, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http info-astroway-forecast 'https://mcp.astroway.info/mcp/forecast' ``` ### Cursor ```json { "mcpServers": { "info-astroway-forecast": { "url": "https://mcp.astroway.info/mcp/forecast" } } } ``` ### VS Code ```json { "servers": { "info-astroway-forecast": { "type": "http", "url": "https://mcp.astroway.info/mcp/forecast" } } } ``` ### Codex ```toml [mcp_servers.info-astroway-forecast] url = "https://mcp.astroway.info/mcp/forecast" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "info-astroway-forecast": { "type": "remote", "url": "https://mcp.astroway.info/mcp/forecast", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add info-astroway-forecast --url 'https://mcp.astroway.info/mcp/forecast' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: info-astroway-forecast: url: "https://mcp.astroway.info/mcp/forecast" ``` ### Netclaw ```json { "McpServers": { "info-astroway-forecast": { "Transport": "http", "Url": "https://mcp.astroway.info/mcp/forecast" } } } ``` ### Vellum ```bash assistant mcp add info-astroway-forecast -t streamable-http -u 'https://mcp.astroway.info/mcp/forecast' ``` ### Other ```json { "mcpServers": { "info-astroway-forecast": { "type": "http", "url": "https://mcp.astroway.info/mcp/forecast" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-10 (score 77, +2) - [security improvement] Judged manipulation: unverified → pass - [security] Tool “astroway_agent_tools” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_cosmogram” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_dial_90” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_eight_harmonic_aspects” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_lefeldt_extensions” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_midpoint_pictures” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_personal_point_tree” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_sensitive_points” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_transit_midpoints” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_uranian_tnps” rewrote its description, which is the text the model reads - [security] Tool “astroway_cosmobiology_witte_formulas” rewrote its description, which is the text the model reads - [security] Tool “astroway_evolutionary_nodal_axis_detail” rewrote its description, which is the text the model reads - [security] Tool “astroway_evolutionary_pluto_natal_condition” rewrote its description, which is the text the model reads - [security] Tool “astroway_evolutionary_skipped_steps” rewrote its description, which is the text the model reads - [security] Tool “astroway_evolutionary_soul_types” rewrote its description, which is the text the model reads - [security] Tool “astroway_evolutionary_yesterday_sky” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_agent_debate” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_agent_pool_status” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_ai_chat” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_ai_comparison_coach” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_ai_explain_aspect” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_ai_explain_transit” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_multi_agent_coordinate” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_multi_chart_context” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_rag_search” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_streaming” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_tool_call_stream” rewrote its description, which is the text the model reads - [security] Tool “astroway_mcp_tools_list” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_firdaria” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_forecast_calendar” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_lunar_return” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_minor_progressions” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_planetary_return” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_primary_directions” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_profections” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_progressions” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_rectification” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_rectification_trutine” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_solar_return” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_symbolic_directions” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_tertiary_progressions” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_transit_calendar” rewrote its description, which is the text the model reads - [security] Tool “astroway_prognostics_transits” rewrote its description, which is the text the model reads ### 2026-10-08 (score 75, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-07 (score 74, 0) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-06 (score 74) First indexed and scored. ## MCP tools (45) ### `astroway_account_status` (~73 tokens) Account Status Check current API key status: tier, credit balance, rate limits, monthly cycle reset. Run this BEFORE invoking expensive endpoints (Tier 4+ at 100+ credits, Tier 6/7 at 500-5000 credits) to confirm the user has budget. Returns plain-text human-readable summary. ### `astroway_cost_estimate` (~91 tokens) Cost Estimate Estimate the credit cost of one or more endpoints WITHOUT invoking them. Returns total + per-endpoint breakdown with tier annotations. Useful when planning multi-step workflows: estimate first, ask user confirmation, then invoke. Cache TTL 5 min. Input parameters: - `endpoints` (array, required): Endpoint paths to estimate, e.g. ["/chart", "/synastry", "/reports/natal"]. Leading slash optional. ### `astroway_agent_tools` (~405 tokens) Agent tool definitions Tool definitions for an agent framework, generated from the live OpenAPI document, so the schema a model fills is the schema the endpoint validates. `format=openai` (default) returns `{ type, function }` objects you can spread straight into a chat completion; `format=anthropic` returns `{ name, description, input_schema }`. The objects carry nothing of ours: how to call each tool lives in a separate `executors` map keyed by tool name, because an unexpected key inside a vendor tool object is a 400 at their end. [Group: Agent Platform] [Endpoint: GET /v1/agent/tools] [Cost: see your plan — endpoint not in the public credit manifest] Input parameters: - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `format` (string): Which vendor contract the tool objects follow. `openai` returns `{ type, function }`, `anthropic` returns `{ name, description, input_schema }`. - `limit` (integer): How many tools to return. The ceiling is the OpenAI limit of 128 functions per request; models degrade well before it. Anything left out is counted in `totalMatched`. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `q` (string): Free-text filter applied within the selection, matched against path, summary, description and group. - `select` (string): What to hand over: `starter` (the curated set, the default), `all`, `group:` such as `group:Vedic`, or `paths:/chart,/synastry` for an explicit list. An unknown path is named in `notes` rather t… Output parameters: - `count` - `executors` - `format` - `notes` - `select` - `tools` - `totalAvailable` - `totalMatched` - `truncated` ### `astroway_mcp_ai_chat` (~387 tokens) Chart-grounded AI chat Chat answered from the positions we computed for this birth moment, not from the model's memory of a sun sign. Carries up to 10 turns of history, replies in 21 languages, and takes four voices through `persona`. Send your own provider key and the turn costs 5 credits instead of the endpoint price. [Group: AI & MCP] [Endpoint: POST /v1/ai/chat] [Required: message] [Cost: 100 credits (Tier 4)] Input parameters: - `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `history` (array) - `language` (string) - `message` (string, required) - `persona` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `disclaimer` - `duration_ms` - `language` - `model` - `persona` - `reply` - `tokens` ### `astroway_mcp_ai_comparison_coach` (~497 tokens) Comparison Coach Coach two charts on relationship dynamics. [Group: AI & MCP] [Endpoint: POST /v1/ai/comparison-coach] [Required: chart1, chart2, question] [Cost: 100 credits (Tier 4)] Input parameters: - `chart1` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `chart2` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `language` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `question` (string, required) Output parameters: - `coaching` ### `astroway_mcp_ai_explain_aspect` (~347 tokens) Explain Aspect Detailed explanation of an aspect between two planets. [Group: AI & MCP] [Endpoint: POST /v1/ai/explain-aspect] [Required: planet1, planet2, aspectType] [Cost: 100 credits (Tier 4)] Input parameters: - `aspectType` (string, required) - `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `language` (string) - `planet1` (string, required) - `planet2` (string, required) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `explanation` ### `astroway_mcp_ai_explain_transit` (~360 tokens) Explain Transit Explain a current transit hitting your natal chart. [Group: AI & MCP] [Endpoint: POST /v1/ai/explain-transit] [Required: chart, transitDate, transitPlanet, natalPlanet, aspectType] [Cost: 100 credits (Tier 4)] Input parameters: - `aspectType` (string, required) - `chart` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `language` (string) - `natalPlanet` (string, required) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `transitDate` (string, required) - `transitPlanet` (string, required) Output parameters: - `explanation` ### `astroway_cosmobiology_cosmogram` (~440 tokens) Cosmogram (90° Render Data) Ebertin cosmogram render data. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/cosmogram] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `aspects` - `methodology` - `modulus` - `points` - `ringDegrees` - `source` - `topPictures` ### `astroway_cosmobiology_dial_90` (~444 tokens) 90° Dial All chart points in 90° cardinal modulus. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/dial-90] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `methodology` - `modulus` - `points` - `source` ### `astroway_cosmobiology_eight_harmonic_aspects` (~465 tokens) 8H Aspect Grid 22.5° / 45° / 67.5° / 90° / 135° aspects. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/eight-harmonic-aspects] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `angles` - `aspectNames` - `aspects` - `count` - `methodology` - `orb` - `source` ### `astroway_cosmobiology_lefeldt_extensions` (~448 tokens) Lefeldt Extensions Lefeldt-Brummund 22.5° subdivisions. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/lefeldt-extensions] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `branches` - `methodology` - `octants` - `orb` - `source` ### `astroway_cosmobiology_midpoint_pictures` (~443 tokens) Midpoint Pictures A=B/C structures with sentence form. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/midpoint-pictures] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `count` - `notation` - `orb` - `pictures` - `source` ### `astroway_cosmobiology_personal_point_tree` (~439 tokens) Personal Point Tree Tree per personal point. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/personal-point-tree] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `methodology` - `orb` - `source` - `tree` ### `astroway_cosmobiology_sensitive_points` (~441 tokens) Sensitive Points Ebertin's personal points midpoint hits. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/sensitive-points] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `methodology` - `orb` - `personalPoints` - `pictures` - `source` ### `astroway_cosmobiology_transit_midpoints` (~480 tokens) Transit Midpoints Transits hitting natal midpoints in 90° dial. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/transit-midpoints] [Required: date, time, latitude, longitude, targetDate] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `converse` (boolean) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `targetDate` (string, required) - `targetTime` (string) - `targetTzOffset` - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `count` - `hits` - `methodology` - `orb` - `source` - `targetDate` ### `astroway_cosmobiology_uranian_tnps` (~439 tokens) Uranian TNPs 8 Hamburg trans-Neptunian bodies. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/uranian-tnps] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `zodiacType` (string) Output parameters: - `count` - `methodology` - `source` - `tnps` ### `astroway_cosmobiology_witte_formulas` (~444 tokens) Witte Formulas Witte planetary pictures A+B−C=D. [Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/witte-formulas] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `withTnp` (boolean) - `zodiacType` (string) Output parameters: - `count` - `methodology` - `notation` - `orb` - `pictures` - `source` ### `astroway_evolutionary_nodal_axis_detail` (~430 tokens) Nodal Axis Detail Full NN/SN with rulers + conjuncts. [Group: Evolutionary Astrology] [Endpoint: POST /v1/evolutionary/nodal-axis-detail] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `zodiacType` (string) Output parameters: - `disclaimer` - `doctrine` - `northNode` - `source` - `southNode` ### `astroway_evolutionary_pluto_natal_condition` (~435 tokens) Pluto Natal Condition JWG: Pluto sign+house+ruler+hard aspects. [Group: Evolutionary Astrology] [Endpoint: POST /v1/evolutionary/pluto-natal-condition] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `zodiacType` (string) Output parameters: - `disclaimer` - `doctrine` - `hardAspects` - `pastLifeSignificance` - `pluto` - `ruler` - `source` ### `astroway_evolutionary_skipped_steps` (~430 tokens) Skipped Steps Planets squaring nodal axis = unfinished karma. [Group: Evolutionary Astrology] [Endpoint: POST /v1/evolutionary/skipped-steps] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `zodiacType` (string) Output parameters: - `count` - `disclaimer` - `doctrine` - `nodalAxis` - `skippedSteps` - `source` ### `astroway_evolutionary_soul_types` (~429 tokens) Soul Types JWG's 4-type by Pluto house quadrant. [Group: Evolutionary Astrology] [Endpoint: POST /v1/evolutionary/soul-types] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `zodiacType` (string) Output parameters: - `type` ### `astroway_evolutionary_yesterday_sky` (~428 tokens) Yesterday's Sky Forrest 2008 past-life method. [Group: Evolutionary Astrology] [Endpoint: POST /v1/evolutionary/yesterday-sky] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)] Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `zodiacType` (string) Output parameters: - `disclaimer` - `doctrine` - `luminaryContacts` - `narrative` - `pastLifeImprint` - `source` ### `astroway_prognostics_firdaria` (~162 tokens) Firdaria Calculate Firdaria planetary periods: the traditional Persian time-lord system based on sect and planet order. [Group: Prognostics] [Endpoint: POST /v1/firdaria] [Cost: 20 credits (Tier 2)] Input parameters: - `body` (required): Natal chart plus the number of years of firdaria periods to return. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `periods` ### `astroway_prognostics_forecast_calendar` (~172 tokens) Forecast Calendar Generate a combined forecast calendar including transits, lunar phases, ingresses, and retrograde stations for a given period. [Group: Prognostics] [Endpoint: POST /v1/forecast-calendar] [Cost: 100 credits (Tier 4)] Input parameters: - `body` (required): Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `cells` - `dailySummary` - `maxAbsTotal` - `year` ### `astroway_prognostics_lunar_return` (~307 tokens) Lunar Return Find the next date when the Moon returns to its natal longitude. Returns full lunar return chart. [Group: Prognostics] [Endpoint: POST /v1/lunar-return] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `antiscia` - `antisciaAspects` - `aspects` - `houses` - `input` - `julianDay` - `parallelAspects` - `planets` - `returnMoment` - `siderealTime` ### `astroway_mcp_agent_debate` (~351 tokens) MCP Agent Debate 2 personas debate a topic, multi-round transcript. [Group: MCP Advanced] [Endpoint: POST /v1/mcp/agent-debate] [Required: topic, agentA, agentB] [Cost: 100 credits (Tier 4)] Input parameters: - `agentA` (string, required) - `agentB` (string, required) - `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `language` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `rounds` (integer) - `topic` (string, required) Output parameters: - `transcript` ### `astroway_mcp_agent_pool_status` (~131 tokens) MCP Agent Pool Status 8 personas with specialties. [Group: MCP Advanced] [Endpoint: GET /v1/mcp/agent-pool-status] [Cost: 10 credits (Tier 1)] Input parameters: - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `count` - `note` - `personas` ### `astroway_mcp_multi_agent_coordinate` (~330 tokens) MCP Multi-Agent Coordinate Run N personas in parallel + LLM synthesis. [Group: MCP Advanced] [Endpoint: POST /v1/mcp/multi-agent-coordinate] [Required: question, agents] [Cost: 100 credits (Tier 4)] Input parameters: - `agents` (array, required) - `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `language` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `question` (string, required) Output parameters: - `individual` - `synthesis` ### `astroway_mcp_multi_chart_context` (~154 tokens) MCP Multi-Chart Context Compact context for MCP agents working across multiple charts. [Group: AI & MCP] [Endpoint: POST /v1/mcp/multi-chart-context] [Required: charts] [Cost: 10 credits (Tier 1)] Input parameters: - `charts` (array, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `intent` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `chartCount` - `contextHash` - `intent` - `notes` - `summaries` - `summaryString` ### `astroway_mcp_rag_search` (~320 tokens) MCP RAG Search Keyword-tag scoring over chart chunks. [Group: MCP Advanced] [Endpoint: POST /v1/mcp/rag-search] [Required: query, chart] [Cost: 10 credits (Tier 1)] Input parameters: - `chart` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `query` (string, required) - `topK` (integer) Output parameters: - `matches` - `query` - `results` - `tokens` - `total` ### `astroway_mcp_streaming` (~322 tokens) MCP Streaming Chat Server-Sent Events streaming chat completion with optional chart context. [Group: AI & MCP] [Endpoint: POST /v1/mcp/streaming] [Required: message] [Cost: 100 credits (Tier 4)] Input parameters: - `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `language` (string) - `message` (string, required) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. ### `astroway_mcp_tool_call_stream` (~157 tokens) MCP Tool-Call Stream SSE-stream of a tool call envelope. [Group: MCP Advanced] [Endpoint: POST /v1/mcp/tool-call-stream] [Required: tool] [Cost: 10 credits (Tier 1)] Input parameters: - `args` (object) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `language` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `tool` (string, required) ### `astroway_mcp_tools_list` (~144 tokens) MCP Tools List Auto-generated tool manifest for MCP clients (modelcontextprotocol/2025-03 spec). [Group: AI & MCP] [Endpoint: GET /v1/mcp/tools-list] [Cost: see your plan — endpoint not in the public credit manifest] Input parameters: - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `notes` - `server` - `spec` - `toolCount` - `tools` ### `astroway_prognostics_minor_progressions` (~169 tokens) Minor Progressions Calculate minor progressions (lunar month-for-a-year) to a target date. Supports converse direction. [Group: Prognostics] [Endpoint: POST /v1/minor-progressions] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Natal chart plus a target date for time-based calculations: progressions, directions, profections, returns. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `antiscia` - `antisciaAspects` - `aspects` - `houses` - `input` - `julianDay` - `parallelAspects` - `planets` - `siderealTime` ### `astroway_prognostics_planetary_return` (~312 tokens) Planetary Return Find all returns of any planet to its natal longitude within a given year. Returns full charts for each return. [Group: Prognostics] [Endpoint: POST /v1/planetary-return] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `returns` ### `astroway_prognostics_primary_directions` (~192 tokens) Primary Directions Calculate primary directions (Ptolemaic or Regiomontanus) up to a maximum age. Returns a timeline of directed aspect hits. [Group: Prognostics] [Endpoint: POST /v1/primary-directions] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Natal chart plus the directional rate in degrees per year (Naibod 0.9856353 by default), the age to search to, and the aspect angles to test. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `directions` ### `astroway_prognostics_profections` (~171 tokens) Profections Calculate annual profections: profected Ascendant, lord of the year, activated house, and monthly profection sub-rulers. [Group: Prognostics] [Endpoint: POST /v1/profections] [Cost: 20 credits (Tier 2)] Input parameters: - `body` (required): Natal chart plus a target date for time-based calculations: progressions, directions, profections, returns. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `age` - `ascendant` - `lordOfYear` - `mc` - `moon` - `signIndex` - `sun` ### `astroway_prognostics_progressions` (~172 tokens) Secondary Progressions Calculate secondary progressed chart (day-for-a-year) for a target date. Returns progressed planets, angles, and aspects to natal. [Group: Prognostics] [Endpoint: POST /v1/progressions] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Natal chart plus a target date for time-based calculations: progressions, directions, profections, returns. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `antiscia` - `antisciaAspects` - `aspects` - `houses` - `input` - `julianDay` - `parallelAspects` - `planets` - `siderealTime` ### `astroway_prognostics_rectification` (~371 tokens) Rectification Rectify an approximate birth time using a list of life events and transit/direction hits to narrow the birth time window. [Group: Prognostics] [Endpoint: POST /v1/rectification] [Required: baseInput, events] [Cost: 500 credits (Tier 6)] ⚠️ Heavy — confirm with user before invoking. Input parameters: - `baseInput` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `events` (array, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `methods` (object) - `orb` (number) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `searchRangeMinutes` (number) - `stepMinutes` (number) Output parameters: - `candidates` ### `astroway_prognostics_rectification_trutine` (~457 tokens) Trutine of Hermes Apply the Trutine of Hermes (Animodar) technique to derive the birth time from the Moon's prenatal syzygy position. [Group: Prognostics] [Endpoint: POST /v1/rectification/trutine] [Required: date, time, latitude, longitude] [Cost: 250 credits (Tier 5)] ⚠️ Heavy — confirm with user before invoking. Input parameters: - `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. - `ayanamsaId` - `city` (string) - `cosmogram` (boolean) - `date` (string, required) - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `houseSystem` (string) - `latitude` (number, required) - `longitude` (number, required) - `name` (string) - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `time` (string, required) - `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it… - `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent. - `zodiacType` (string) Output parameters: - `correctedAscendant` - `correctedTime` - `moonAtSyzygy` - `syzygyDate` - `syzygyType` ### `astroway_prognostics_solar_return` (~311 tokens) Solar Return Find the exact moment when the Sun returns to its natal longitude in a given year. Returns full solar return chart. [Group: Prognostics] [Endpoint: POST /v1/solar-return] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `antiscia` - `antisciaAspects` - `aspects` - `houses` - `input` - `julianDay` - `parallelAspects` - `planets` - `returnMoment` - `siderealTime` ### `astroway_prognostics_symbolic_directions` (~198 tokens) Symbolic Directions Calculate symbolic arc directions to natal points for a target date. Key: "one_degree" (default), "naibod", or "solar_arc" (the arc of the progressed Sun). [Group: Prognostics] [Endpoint: POST /v1/symbolic-directions] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Natal chart plus a target date and the directional key: one degree per year, the Naibod rate, or the arc of the progressed Sun. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `arc` - `houses` - `key` - `planets` ### `astroway_prognostics_tertiary_progressions` (~174 tokens) Tertiary Progressions Calculate tertiary progressions (day-for-a-lunar-month) to a target date. Supports converse direction. [Group: Prognostics] [Endpoint: POST /v1/tertiary-progressions] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Natal chart plus a target date for time-based calculations: progressions, directions, profections, returns. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `antiscia` - `antisciaAspects` - `aspects` - `houses` - `input` - `julianDay` - `parallelAspects` - `planets` - `siderealTime` ### `astroway_prognostics_transit_calendar` (~171 tokens) Transit Calendar Build a month-by-month transit calendar for a natal chart showing exact dates of aspect ingresses and partile hits. [Group: Prognostics] [Endpoint: POST /v1/transit-calendar] [Cost: 100 credits (Tier 4)] Input parameters: - `body` (required): Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields. - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `count` - `endDate` - `events` - `maxOrb` - `startDate` ### `astroway_prognostics_transits` (~304 tokens) Transits Calculate transit planet aspects to natal planets for a given date. Returns applying and separating aspects. [Group: Prognostics] [Endpoint: POST /v1/transits] [Cost: 50 credits (Tier 3)] Input parameters: - `body` (required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;… - `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. Output parameters: - `antiscia` - `antisciaAspects` - `aspects` - `houses` - `input` - `julianDay` - `parallelAspects` - `planets` - `siderealTime` ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/info-astroway-forecast/mcp-forecast#diagnostics ## Score history - 2026-10-11: 77 - 2026-10-10: 77 - 2026-10-08: 75 - 2026-10-07: 74 - 2026-10-06: 74 ## Common questions ### What is the AstroWay Forecasting MCP server? AstroWay Forecasting is an MCP server listed in the public MCP registry as info.astroway/forecast. Transits, progressions, directions, returns, cosmobiology and evolutionary technique. This page covers its hosted endpoint (https://mcp.astroway.info/mcp/forecast). ### Is the AstroWay Forecasting MCP server safe to use? AstroWay Forecasting scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the AstroWay Forecasting MCP server expose? AstroWay Forecasting exposes 45 tools: astroway_account_status, astroway_cost_estimate, astroway_agent_tools, astroway_mcp_ai_chat, astroway_mcp_ai_comparison_coach, and 40 more. Their descriptions and schemas cost roughly 14,347 tokens of context every time the server is loaded. ### Does the AstroWay Forecasting MCP server require authentication? Yes. AstroWay Forecasting asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything. ### Is the AstroWay Forecasting MCP server still maintained? AstroWay Forecasting is still listed as active in the MCP registry. We last reached this channel on 11 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://mcp.astroway.info/mcp/forecast - Authorisation metadata: https://mcp.astroway.info/.well-known/oauth-protected-resource/mcp/forecast - Website: https://api.astroway.info/en/examples/mcp/ - Changelog RSS feed: https://verifymcp.io/servers/info-astroway-forecast/mcp-forecast.xml - Changelog JSON feed: https://verifymcp.io/servers/info-astroway-forecast/mcp-forecast.json - HTML version of this page: https://verifymcp.io/servers/info-astroway-forecast/mcp-forecast