# AstroWay Relationships (remote · mcp.astroway.info) Synastry, composite, compatibility scores, family dynamics and pet charts. - Trust score: 76/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-10 ## Components - remote · `mcp.astroway.info`: 76/100 (this document), [markdown](https://verifymcp.io/servers/info-astroway-relationships/mcp-relationships.md), [page](https://verifymcp.io/servers/info-astroway-relationships/mcp-relationships) ## Channel facts - Endpoint: `https://mcp.astroway.info/mcp/relationships` - 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-10. - **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 17894 tokens (~303/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**: 10/100 - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 86/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 52% 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 Relationships MCP server? AstroWay Relationships is a hosted endpoint at https://mcp.astroway.info/mcp/relationships, 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-relationships 'https://mcp.astroway.info/mcp/relationships' ``` ### Cursor ```json { "mcpServers": { "info-astroway-relationships": { "url": "https://mcp.astroway.info/mcp/relationships" } } } ``` ### VS Code ```json { "servers": { "info-astroway-relationships": { "type": "http", "url": "https://mcp.astroway.info/mcp/relationships" } } } ``` ### Codex ```toml [mcp_servers.info-astroway-relationships] url = "https://mcp.astroway.info/mcp/relationships" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "info-astroway-relationships": { "type": "remote", "url": "https://mcp.astroway.info/mcp/relationships", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add info-astroway-relationships --url 'https://mcp.astroway.info/mcp/relationships' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: info-astroway-relationships: url: "https://mcp.astroway.info/mcp/relationships" ``` ### Netclaw ```json { "McpServers": { "info-astroway-relationships": { "Transport": "http", "Url": "https://mcp.astroway.info/mcp/relationships" } } } ``` ### Vellum ```bash assistant mcp add info-astroway-relationships -t streamable-http -u 'https://mcp.astroway.info/mcp/relationships' ``` ### Other ```json { "mcpServers": { "info-astroway-relationships": { "type": "http", "url": "https://mcp.astroway.info/mcp/relationships" } } } ``` 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 76, +1) - [security] Tool “astroway_agent_tools” rewrote its description, which is the text the model reads - [security] Tool “astroway_family_genogram” rewrote its description, which is the text the model reads - [security] Tool “astroway_family_parent_child_deep” rewrote its description, which is the text the model reads - [security] Tool “astroway_family_saturn_return_cycles” rewrote its description, which is the text the model reads - [security] Tool “astroway_family_sibling_dynamics” rewrote its description, which is the text the model reads - [security] Tool “astroway_family_system_pattern” 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_pet_best_names” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_birth_chart” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_communication_style” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_diet_by_sign” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_exercise_needs” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_grooming_by_element” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_health_tips” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_lucky_day” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_owner_pet_compatibility” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_personality” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_play_style” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_sun_sign_meaning” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_temperament” rewrote its description, which is the text the model reads - [security] Tool “astroway_pet_training_style” rewrote its description, which is the text the model reads - [security] Tool “astroway_rel_synastry_attraction_score” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_coalescent” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_composite” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_davison” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_group_synastry” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_match_score” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_synastry” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_synastry_aspect_grid” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_synastry_attraction_score” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_synastry_element_balance” rewrote its description, which is the text the model reads - [security] Tool “astroway_relational_synastry_house_overlay” rewrote its description, which is the text the model reads - [functional improvement] Stability: unverified → 0.10 ### 2026-10-07 (score 75, +50) - [security regression] Authorization: unverified → fail - [security improvement] Transport: unverified → pass - [security improvement] Injection markers: unverified → pass - [security] First check of Judged manipulation: pass - [functional improvement] MCP protocol: unverified → pass - [functional improvement] Schema quality: unverified → 100 - [functional improvement] Tool coverage: unverified → 100 - [functional] First check of Schema quality: fail - [functional] First check of Destructive annotations: pass - [functional] First check of Schema quality: fail - [functional] First check of Tool coverage: 52 - [functional] First check of Tool coverage: 91 - [functional] First check of Schema quality: good ### 2026-10-06 (score 25) 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_relational_coalescent` (~486 tokens) Coalescent Chart Calculate a coalescent chart: the harmonic chart that resonates most strongly between two charts. [Group: Comparisons] [Endpoint: POST /v1/coalescent] [Required: input1, input2] [Cost: 50 credits (Tier 3)] 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. - `input1` (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;… - `input2` (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;… - `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` - `chartSect` - `houseAspects` - `houses` - `input` - `julianDay` - `meta` - `parallelAspects` - `planets` - `siderealTime` ### `astroway_relational_composite` (~485 tokens) Composite Chart Calculate a midpoint composite chart by averaging the planetary positions and house cusps of two natal charts. [Group: Comparisons] [Endpoint: POST /v1/composite] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] 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. - `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_relational_davison` (~486 tokens) Davison Chart Calculate a Davison relationship chart using the midpoint in time and space between two birth moments. [Group: Comparisons] [Endpoint: POST /v1/davison] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] 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. - `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` - `chartSect` - `houseAspects` - `houses` - `input` - `julianDay` - `meta` - `midpoint` - `parallelAspects` - `planets` - `siderealTime` ### `astroway_family_genogram` (~642 tokens) Genogram Multi-generational family pattern map. [Group: Family Astrology] [Endpoint: POST /v1/family/genogram] [Required: grandparent, parent, child] [Cost: 10 credits (Tier 1)] Input parameters: - `child` (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. - `grandparent` (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;… - `parent` (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;… - `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` - `generations` - `karmicLine` - `moonInheritance` - `outerPlanetEcho` - `source` ### `astroway_family_parent_child_deep` (~476 tokens) Parent-Child Deep Deep parent-child synastry analysis. [Group: Family Astrology] [Endpoint: POST /v1/family/parent-child-deep] [Required: parent, child] [Cost: 10 credits (Tier 1)] Input parameters: - `child` (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. - `parent` (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;… - `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` - `inheritanceScore` - `interpretation` - `luminaryAspects` - `mcContact` - `parentalAxisOverlay` - `saturnCrossCount` - `source` ### `astroway_family_saturn_return_cycles` (~146 tokens) Saturn Return Cycles Saturn return timing across a family cohort. [Group: Family Astrology] [Endpoint: POST /v1/family/saturn-return-cycles] [Required: members] [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. - `members` (array, 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: - `concurrentTransits` - `disclaimer` - `familyPhaseSummary` - `members` - `source` ### `astroway_family_sibling_dynamics` (~648 tokens) Sibling Dynamics Inter-sibling synastry and dynamics. [Group: Family Astrology] [Endpoint: POST /v1/family/sibling-dynamics] [Required: sibling1, sibling2] [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. - `parent` (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;… - `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. - `sibling1` (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;… - `sibling2` (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;… Output parameters: - `disclaimer` - `interpretation` - `mercuryAspect` - `moonAspect` - `sharedParentImprint` - `siblingHouseOverlay` - `siblingScore` - `source` ### `astroway_family_system_pattern` (~139 tokens) Family System Pattern System-level family astrological signatures. [Group: Family Astrology] [Endpoint: POST /v1/family/system-pattern] [Required: members] [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. - `members` (array, 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: - `disclaimer` - `excludedThemes` - `generationalShadow` - `luminaryGhostContacts` - `members` - `source` - `systemSummary` ### `astroway_relational_group_synastry` (~158 tokens) Group Synastry Calculate synastry aspects among 2–8 charts simultaneously, returning all pairwise cross-chart aspect matrices. [Group: Comparisons] [Endpoint: POST /v1/group-synastry] [Required: inputs] [Cost: 100 credits (Tier 4)] 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. - `inputs` (array, 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: - `averageScore` - `charts` - `matrix` - `pairs` ### `astroway_relational_match_score` (~562 tokens) Match Score (dating compatibility) One-call dating-compatibility aggregate over the synastry engine: overall score (0-100) + label + harmony/tension, the attraction score (Venus-Mars / Moon-Venus / 5th-house), the most influential cross-aspects, and green/red flags surfaced from those aspects. Built for dating apps that want a single call instead of synastry + attraction + their own flag logic. Same TwoChart input as /synastry. [Group: Comparisons] [Endpoint: POST /v1/match/score] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] 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. - `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: - `attraction` - `greenFlags` - `harmony` - `label` - `redFlags` - `score` - `tension` - `topAspects` ### `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_pet_best_names` (~298 tokens) Best Names by Sign Sign-aligned name suggestions; optional gender filter. [Group: Pet Astrology] [Endpoint: POST /v1/pet/best-names] [Cost: 10 credits (Tier 1)] 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: - `disclaimer` - `element` - `names` - `sunSign` ### `astroway_pet_birth_chart` (~431 tokens) Pet Birth Chart Full natal chart for the pet (sun, moon, ASC + planets) plus disclaimer. [Group: Pet Astrology] [Endpoint: POST /v1/pet/birth-chart] [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: - `ascendant` - `disclaimer` - `moonSign` - `planets` - `sunSign` ### `astroway_pet_communication_style` (~422 tokens) Communication Style How best to communicate with this pet. [Group: Pet Astrology] [Endpoint: POST /v1/pet/communication-style] [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: - `communication` ### `astroway_pet_diet_by_sign` (~421 tokens) Diet by Sign Element-based dietary focus. [Group: Pet Astrology] [Endpoint: POST /v1/pet/diet-by-sign] [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: - `diet` - `disclaimer` - `element` - `sunSign` ### `astroway_pet_exercise_needs` (~425 tokens) Exercise Needs Element-based daily exercise minutes + recommended activities. [Group: Pet Astrology] [Endpoint: POST /v1/pet/exercise-needs] [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` - `element` - `exercise` - `sunSign` ### `astroway_pet_grooming_by_element` (~426 tokens) Grooming by Element Grooming focus + frequency by element. [Group: Pet Astrology] [Endpoint: POST /v1/pet/grooming-by-element] [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: - `grooming` ### `astroway_pet_health_tips` (~424 tokens) Health Watch-Outs Sign-specific health vulnerabilities. NOT veterinary advice. [Group: Pet Astrology] [Endpoint: POST /v1/pet/health-tips] [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` - `element` - `healthTips` - `sunSign` ### `astroway_pet_lucky_day` (~423 tokens) Lucky Days Days of week traditionally aligned with the sign. [Group: Pet Astrology] [Endpoint: POST /v1/pet/lucky-day] [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: - `luckyDays` ### `astroway_pet_owner_pet_compatibility` (~485 tokens) Owner-Pet Compatibility Compatibility score (0-100) based on element + sign distance. [Group: Pet Astrology] [Endpoint: POST /v1/pet/owner-pet-compatibility] [Required: owner, pet] [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. - `owner` (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;… - `pet` (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;… - `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: - `compatibility` ### `astroway_pet_personality` (~416 tokens) Pet Personality Profile Full personality breakdown. [Group: Pet Astrology] [Endpoint: POST /v1/pet/personality] [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: - `bestSuited` - `disclaimer` - `element` - `quirks` - `sunSign` - `temperament` ### `astroway_pet_play_style` (~418 tokens) Play Style + Toys Preferred play and toy types. [Group: Pet Astrology] [Endpoint: POST /v1/pet/play-style] [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` - `play` - `sunSign` ### `astroway_pet_sun_sign_meaning` (~427 tokens) Pet Sun-Sign Meaning Personality + temperament + best-suited household. [Group: Pet Astrology] [Endpoint: POST /v1/pet/sun-sign-meaning] [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` - `element` - `personality` - `sunSign` ### `astroway_pet_temperament` (~419 tokens) Pet Temperament Short temperament-only summary. [Group: Pet Astrology] [Endpoint: POST /v1/pet/temperament] [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` - `element` - `quirks` - `sunSign` - `temperament` ### `astroway_pet_training_style` (~421 tokens) Training Style Preferred training style + 3 tips. [Group: Pet Astrology] [Endpoint: POST /v1/pet/training-style] [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` - `sunSign` - `training` ### `astroway_relational_synastry` (~278 tokens) Synastry Calculate cross-chart aspects between two natal charts for relationship analysis. Either partner may set timeUnknown: true: cross-aspects are still returned, while that partner's houses, angles and sect come back null. [Group: Comparisons] [Endpoint: POST /v1/synastry] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] Input parameters: - `chart1` (object, required): Birth data where the clock time may be unknown. Either pass time (HH:mm:ss), or set timeUnknown: true and omit it. In the second case the response carries planets and aspects but no houses, angles or… - `chart2` (object, required): Birth data where the clock time may be unknown. Either pass time (HH:mm:ss), or set timeUnknown: true and omit it. In the second case the response carries planets and aspects but no houses, angles or… - `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: - `chart1` - `chart2` - `compatibility` - `crossAspects` ### `astroway_relational_synastry_aspect_grid` (~512 tokens) Synastry Aspect Grid NxM matrix of cross-chart aspects between the two charts (default 13×13: Sun..Pluto + nodes + Lilith + Chiron). Cells contain aspect or null. [Group: Comparisons] [Endpoint: POST /v1/synastry/aspect-grid] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] 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. - `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: - `bodies1` - `bodies2` - `grid` - `totals` ### `astroway_relational_synastry_attraction_score` (~516 tokens) Synastry Attraction Score Weighted 0–100 attraction score from Sun-Moon, Mars-Venus, ASC/DSC, Mars-Mars, Sun-Mars, Moon-Venus contacts and 5th-house overlay. [Group: Comparisons] [Endpoint: POST /v1/synastry/attraction-score] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] 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. - `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: - `components` - `notes` - `score` ### `astroway_rel_synastry_attraction_score` (~533 tokens) Synastry Attraction Score Weighted 0–100 attraction score from Sun-Moon, Mars-Venus, ASC/DSC, Mars-Mars, Sun-Mars, Moon-Venus contacts and 5th-house overlay. [Group: Comparisons] [Endpoint: POST /v1/synastry/attraction-score] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] (Cursor-friendly alias for `astroway_relational_synastry_attraction_score`.) 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. - `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: - `components` - `notes` - `score` ### `astroway_relational_synastry_element_balance` (~511 tokens) Synastry Element Balance Element (fire/earth/air/water) and modality (cardinal/fixed/mutable) tallies for each chart and the combined pair, with dominant and missing elements. [Group: Comparisons] [Endpoint: POST /v1/synastry/element-balance] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] 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. - `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: - `balance` - `chart1` - `chart2` - `combined` ### `astroway_relational_synastry_house_overlay` (~496 tokens) Synastry House Overlay Locate each chart’s personal planets in the partner’s houses; reports top-3 emphasized houses on either side. [Group: Comparisons] [Endpoint: POST /v1/synastry/house-overlay] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)] 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. - `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: - `chart1InChart2` - `chart2InChart1` - `emphasizedHouses` ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/info-astroway-relationships/mcp-relationships#diagnostics ## Score history - 2026-10-10: 76 - 2026-10-07: 75 - 2026-10-06: 25 ## Common questions ### What is the AstroWay Relationships MCP server? AstroWay Relationships is an MCP server listed in the public MCP registry as info.astroway/relationships. Synastry, composite, compatibility scores, family dynamics and pet charts. This page covers its hosted endpoint (https://mcp.astroway.info/mcp/relationships). ### Is the AstroWay Relationships MCP server safe to use? AstroWay Relationships scores 76 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 Relationships MCP server expose? AstroWay Relationships 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 16,999 tokens of context every time the server is loaded. ### Does the AstroWay Relationships MCP server require authentication? Yes. AstroWay Relationships 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 Relationships MCP server still maintained? AstroWay Relationships is still listed as active in the MCP registry. We last reached this channel on 10 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/relationships - Authorisation metadata: https://mcp.astroway.info/.well-known/oauth-protected-resource/mcp/relationships - Website: https://api.astroway.info/en/examples/mcp/ - Changelog RSS feed: https://verifymcp.io/servers/info-astroway-relationships/mcp-relationships.xml - Changelog JSON feed: https://verifymcp.io/servers/info-astroway-relationships/mcp-relationships.json - HTML version of this page: https://verifymcp.io/servers/info-astroway-relationships/mcp-relationships