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_relational_davison Davison Chart ~486
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)]
| 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 | – | – | – |
| chartSect | – | – | – |
| houseAspects | – | – | – |
| houses | – | – | – |
| input | – | – | – |
| julianDay | – | – | – |
| meta | – | – | – |
| midpoint | – | – | – |
| parallelAspects | – | – | – |
| planets | – | – | – |
| siderealTime | – | – | – |
No examples provided.
astroway_relational_group_synastry Group Synastry ~158
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)]
| 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. |
| inputs | 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 |
|---|---|---|---|
| averageScore | – | – | – |
| charts | – | – | – |
| matrix | – | – | – |
| pairs | – | – | – |
No examples provided.
astroway_relational_match_score Match Score (dating compatibility) ~562
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)]
| 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 |
|---|---|---|---|
| attraction | – | – | – |
| greenFlags | – | – | – |
| harmony | – | – | – |
| label | – | – | – |
| redFlags | – | – | – |
| score | – | – | – |
| tension | – | – | – |
| topAspects | – | – | – |
No examples provided.
astroway_relational_synastry Synastry ~278
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)]
| Name | Type | Req | Description |
|---|---|---|---|
| chart1 | object | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| chart1 | – | – | – |
| chart2 | – | – | – |
| compatibility | – | – | – |
| crossAspects | – | – | – |
No examples provided.
astroway_relational_synastry_aspect_grid Synastry Aspect Grid ~512
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)]
| 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 |
|---|---|---|---|
| bodies1 | – | – | – |
| bodies2 | – | – | – |
| grid | – | – | – |
| totals | – | – | – |
No examples provided.
astroway_relational_synastry_attraction_score Synastry Attraction Score ~516
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)]
| 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_synastry_element_balance Synastry Element Balance ~511
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)]
| 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 |
|---|---|---|---|
| balance | – | – | – |
| chart1 | – | – | – |
| chart2 | – | – | – |
| combined | – | – | – |
No examples provided.
astroway_relational_synastry_house_overlay Synastry House Overlay ~496
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)]
| 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 |
|---|---|---|---|
| chart1InChart2 | – | – | – |
| chart2InChart1 | – | – | – |
| emphasizedHouses | – | – | – |
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.