AstroWay Relationships
REMOTE · MCP.ASTROWAY.INFO · SCANNED OCT 10
Synastry, composite, compatibility scores, family dynamics and pet charts.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
- Structured output schemas are declared (91% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 45 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.astroway.info
claude mcp add --transport http info-astroway-relationships 'https://mcp.astroway.info/mcp/relationships'
{
"mcpServers": {
"info-astroway-relationships": {
"url": "https://mcp.astroway.info/mcp/relationships"
}
}
} {
"servers": {
"info-astroway-relationships": {
"type": "http",
"url": "https://mcp.astroway.info/mcp/relationships"
}
}
} [mcp_servers.info-astroway-relationships] url = "https://mcp.astroway.info/mcp/relationships"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"info-astroway-relationships": {
"type": "remote",
"url": "https://mcp.astroway.info/mcp/relationships",
"enabled": true
}
}
} openclaw mcp add info-astroway-relationships --url 'https://mcp.astroway.info/mcp/relationships' --transport streamable-http
mcp_servers:
info-astroway-relationships:
url: "https://mcp.astroway.info/mcp/relationships" {
"McpServers": {
"info-astroway-relationships": {
"Transport": "http",
"Url": "https://mcp.astroway.info/mcp/relationships"
}
}
} assistant mcp add info-astroway-relationships -t streamable-http -u 'https://mcp.astroway.info/mcp/relationships'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 +1
- 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 security
- Stability: unverified → 0.10 ▲ functional
- 7 Oct 26 +50
- Authorization: unverified → fail ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 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 functional
- 6 Oct 26 25
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 10 Oct 2026 · Probed https://mcp.astroway.info/mcp/relationships
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=astroway.info | CN=YE1,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 676709b5e42e439072e19c38481bf59d5a7 |
| SANs: *.astroway.info, astroway.info | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.astroway.info. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| info. | present | 5104, 9986 | 8, 8 | Verified |
| astroway.info. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.astroway.info/mcp/relationships | Verified | 200 | |
| http (plaintext) | http://mcp.astroway.info/mcp/relationships | HTTPS enforced | 301 | https://mcp.astroway.info/mcp/relationships |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
astroway_account_status Account Status ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
astroway_agent_tools Agent tool definitions ~405
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]
| Name | Type | Req | Description |
|---|---|---|---|
| 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:<tag>` such as `group:Vedic`, or `paths:/chart,/synastry` for an explicit list. An unknown path is named in `notes` rather t… |
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | – | – |
| executors | – | – | – |
| format | – | – | – |
| notes | – | – | – |
| select | – | – | – |
| tools | – | – | – |
| totalAvailable | – | – | – |
| totalMatched | – | – | – |
| truncated | – | – | – |
No examples provided.
astroway_cost_estimate Cost Estimate ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | Endpoint paths to estimate, e.g. ["/chart", "/synastry", "/reports/natal"]. Leading slash optional. |
No output schema declared.
No examples provided.
astroway_family_genogram Genogram ~642
Multi-generational family pattern map. [Group: Family Astrology] [Endpoint: POST /v1/family/genogram] [Required: grandparent, parent, child] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| child | object | yes | 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 | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| generations | – | – | – |
| karmicLine | – | – | – |
| moonInheritance | – | – | – |
| outerPlanetEcho | – | – | – |
| source | – | – | – |
No examples provided.
astroway_family_parent_child_deep Parent-Child Deep ~476
Deep parent-child synastry analysis. [Group: Family Astrology] [Endpoint: POST /v1/family/parent-child-deep] [Required: parent, child] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| child | object | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| inheritanceScore | – | – | – |
| interpretation | – | – | – |
| luminaryAspects | – | – | – |
| mcContact | – | – | – |
| parentalAxisOverlay | – | – | – |
| saturnCrossCount | – | – | – |
| source | – | – | – |
No examples provided.
astroway_family_saturn_return_cycles Saturn Return Cycles ~146
Saturn return timing across a family cohort. [Group: Family Astrology] [Endpoint: POST /v1/family/saturn-return-cycles] [Required: members] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| precision | integer | – | Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. |
| Name | Type | Req | Description |
|---|---|---|---|
| concurrentTransits | – | – | – |
| disclaimer | – | – | – |
| familyPhaseSummary | – | – | – |
| members | – | – | – |
| source | – | – | – |
No examples provided.
astroway_family_sibling_dynamics Sibling Dynamics ~648
Inter-sibling synastry and dynamics. [Group: Family Astrology] [Endpoint: POST /v1/family/sibling-dynamics] [Required: sibling1, sibling2] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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;… |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| interpretation | – | – | – |
| mercuryAspect | – | – | – |
| moonAspect | – | – | – |
| sharedParentImprint | – | – | – |
| siblingHouseOverlay | – | – | – |
| siblingScore | – | – | – |
| source | – | – | – |
No examples provided.
astroway_family_system_pattern Family System Pattern ~139
System-level family astrological signatures. [Group: Family Astrology] [Endpoint: POST /v1/family/system-pattern] [Required: members] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| precision | integer | – | Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| excludedThemes | – | – | – |
| generationalShadow | – | – | – |
| luminaryGhostContacts | – | – | – |
| members | – | – | – |
| source | – | – | – |
| systemSummary | – | – | – |
No examples provided.
astroway_mcp_agent_debate MCP Agent Debate ~351
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| agentA | string | yes | – |
| agentB | string | yes | – |
| 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 | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| transcript | – | – | – |
No examples provided.
astroway_mcp_agent_pool_status MCP Agent Pool Status ~131
8 personas with specialties. [Group: MCP Advanced] [Endpoint: GET /v1/mcp/agent-pool-status] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | – | – |
| note | – | – | – |
| personas | – | – | – |
No examples provided.
astroway_mcp_ai_chat Chart-grounded AI chat ~387
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| duration_ms | – | – | – |
| language | – | – | – |
| model | – | – | – |
| persona | – | – | – |
| reply | – | – | – |
| tokens | – | – | – |
No examples provided.
astroway_mcp_ai_comparison_coach Comparison Coach ~497
Coach two charts on relationship dynamics. [Group: AI & MCP] [Endpoint: POST /v1/ai/comparison-coach] [Required: chart1, chart2, question] [Cost: 100 credits (Tier 4)]
| Name | Type | Req | Description |
|---|---|---|---|
| chart1 | object | yes | 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 | yes | 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 | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coaching | – | – | – |
No examples provided.
astroway_mcp_ai_explain_aspect Explain Aspect ~347
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| aspectType | string | yes | – |
| 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 | yes | – |
| planet2 | string | yes | – |
| precision | integer | – | Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. |
| Name | Type | Req | Description |
|---|---|---|---|
| explanation | – | – | – |
No examples provided.
astroway_mcp_ai_explain_transit Explain Transit ~360
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| aspectType | string | yes | – |
| chart | object | yes | 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 | yes | – |
| 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 | yes | – |
| transitPlanet | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| explanation | – | – | – |
No examples provided.
astroway_mcp_multi_agent_coordinate MCP Multi-Agent Coordinate ~330
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | – |
| 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 | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| individual | – | – | – |
| synthesis | – | – | – |
No examples provided.
astroway_mcp_multi_chart_context MCP Multi-Chart Context ~154
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| charts | array | yes | – |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| chartCount | – | – | – |
| contextHash | – | – | – |
| intent | – | – | – |
| notes | – | – | – |
| summaries | – | – | – |
| summaryString | – | – | – |
No examples provided.
astroway_mcp_rag_search MCP RAG Search ~320
Keyword-tag scoring over chart chunks. [Group: MCP Advanced] [Endpoint: POST /v1/mcp/rag-search] [Required: query, chart] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| chart | object | yes | 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 | yes | – |
| topK | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | – | – | – |
| query | – | – | – |
| results | – | – | – |
| tokens | – | – | – |
| total | – | – | – |
No examples provided.
astroway_mcp_streaming MCP Streaming Chat ~322
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| precision | integer | – | Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. |
No output schema declared.
No examples provided.
astroway_mcp_tool_call_stream MCP Tool-Call Stream ~157
SSE-stream of a tool call envelope. [Group: MCP Advanced] [Endpoint: POST /v1/mcp/tool-call-stream] [Required: tool] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
astroway_mcp_tools_list MCP Tools List ~144
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]
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | – | – | – |
| server | – | – | – |
| spec | – | – | – |
| toolCount | – | – | – |
| tools | – | – | – |
No examples provided.
astroway_pet_best_names Best Names by Sign ~298
Sign-aligned name suggestions; optional gender filter. [Group: Pet Astrology] [Endpoint: POST /v1/pet/best-names] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| element | – | – | – |
| names | – | – | – |
| sunSign | – | – | – |
No examples provided.
astroway_pet_birth_chart Pet Birth Chart ~431
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ascendant | – | – | – |
| disclaimer | – | – | – |
| moonSign | – | – | – |
| planets | – | – | – |
| sunSign | – | – | – |
No examples provided.
astroway_pet_communication_style Communication Style ~422
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| communication | – | – | – |
No examples provided.
astroway_pet_diet_by_sign Diet by Sign ~421
Element-based dietary focus. [Group: Pet Astrology] [Endpoint: POST /v1/pet/diet-by-sign] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| diet | – | – | – |
| disclaimer | – | – | – |
| element | – | – | – |
| sunSign | – | – | – |
No examples provided.
astroway_pet_exercise_needs Exercise Needs ~425
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| element | – | – | – |
| exercise | – | – | – |
| sunSign | – | – | – |
No examples provided.
astroway_pet_grooming_by_element Grooming by Element ~426
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| grooming | – | – | – |
No examples provided.
astroway_pet_health_tips Health Watch-Outs ~424
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| element | – | – | – |
| healthTips | – | – | – |
| sunSign | – | – | – |
No examples provided.
astroway_pet_lucky_day Lucky Days ~423
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| luckyDays | – | – | – |
No examples provided.
astroway_pet_owner_pet_compatibility Owner-Pet Compatibility ~485
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| compatibility | – | – | – |
No examples provided.
astroway_pet_personality Pet Personality Profile ~416
Full personality breakdown. [Group: Pet Astrology] [Endpoint: POST /v1/pet/personality] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bestSuited | – | – | – |
| disclaimer | – | – | – |
| element | – | – | – |
| quirks | – | – | – |
| sunSign | – | – | – |
| temperament | – | – | – |
No examples provided.
astroway_pet_play_style Play Style + Toys ~418
Preferred play and toy types. [Group: Pet Astrology] [Endpoint: POST /v1/pet/play-style] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| play | – | – | – |
| sunSign | – | – | – |
No examples provided.
astroway_pet_sun_sign_meaning Pet Sun-Sign Meaning ~427
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| element | – | – | – |
| personality | – | – | – |
| sunSign | – | – | – |
No examples provided.
astroway_pet_temperament Pet Temperament ~419
Short temperament-only summary. [Group: Pet Astrology] [Endpoint: POST /v1/pet/temperament] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| element | – | – | – |
| quirks | – | – | – |
| sunSign | – | – | – |
| temperament | – | – | – |
No examples provided.
astroway_pet_training_style Training Style ~421
Preferred training style + 3 tips. [Group: Pet Astrology] [Endpoint: POST /v1/pet/training-style] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | – | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |
| ayanamsaId | – | – | – |
| city | string | – | – |
| cosmogram | boolean | – | – |
| date | string | yes | – |
| 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 | yes | – |
| longitude | number | yes | – |
| 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 | yes | – |
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | – | – | – |
| sunSign | – | – | – |
| training | – | – | – |
No examples provided.
astroway_rel_synastry_attraction_score Synastry Attraction Score ~533
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`.)
| Name | Type | Req | Description |
|---|---|---|---|
| chart1 | object | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| components | – | – | – |
| notes | – | – | – |
| score | – | – | – |
No examples provided.
astroway_relational_coalescent Coalescent Chart ~486
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| antiscia | – | – | – |
| antisciaAspects | – | – | – |
| aspects | – | – | – |
| chartSect | – | – | – |
| houseAspects | – | – | – |
| houses | – | – | – |
| input | – | – | – |
| julianDay | – | – | – |
| meta | – | – | – |
| parallelAspects | – | – | – |
| planets | – | – | – |
| siderealTime | – | – | – |
No examples provided.
astroway_relational_composite Composite Chart ~485
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| chart1 | object | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| antiscia | – | – | – |
| antisciaAspects | – | – | – |
| aspects | – | – | – |
| houses | – | – | – |
| input | – | – | – |
| julianDay | – | – | – |
| parallelAspects | – | – | – |
| planets | – | – | – |
| siderealTime | – | – | – |
No examples provided.
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.