AstroWay Human Design
REMOTE · MCP.ASTROWAY.INFO · SCANNED OCT 10
Bodygraph, centres, channels, incarnation cross, penta and group overlay.
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 Usability70
- 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 9331 tokens (~227/item across 41 items; 27 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
- Structured output schemas are declared (85% 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 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 29 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 Human Design MCP server?
AstroWay Human Design is a hosted endpoint at https://mcp.astroway.info/mcp/human-design, 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-human-design 'https://mcp.astroway.info/mcp/human-design'
{
"mcpServers": {
"info-astroway-human-design": {
"url": "https://mcp.astroway.info/mcp/human-design"
}
}
} {
"servers": {
"info-astroway-human-design": {
"type": "http",
"url": "https://mcp.astroway.info/mcp/human-design"
}
}
} [mcp_servers.info-astroway-human-design] url = "https://mcp.astroway.info/mcp/human-design"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"info-astroway-human-design": {
"type": "remote",
"url": "https://mcp.astroway.info/mcp/human-design",
"enabled": true
}
}
} openclaw mcp add info-astroway-human-design --url 'https://mcp.astroway.info/mcp/human-design' --transport streamable-http
mcp_servers:
info-astroway-human-design:
url: "https://mcp.astroway.info/mcp/human-design" {
"McpServers": {
"info-astroway-human-design": {
"Transport": "http",
"Url": "https://mcp.astroway.info/mcp/human-design"
}
}
} assistant mcp add info-astroway-human-design -t streamable-http -u 'https://mcp.astroway.info/mcp/human-design'
{
"mcpServers": {
"info-astroway-human-design": {
"type": "http",
"url": "https://mcp.astroway.info/mcp/human-design"
}
}
} 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 0
- Tool “astroway_agent_tools” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_circuitry” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_design_date” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_dream_rave” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_group_overlay” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_hologenetic” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_human_design” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_human_design_compatibility” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_human_design_transits” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_incarnation_cross” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_penta” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_rave_new_years” rewrote its description, which is the text the model reads security
- Tool “astroway_hd_sensitivity” 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
- 9 Oct 26 +2
- Tool “astroway_hd_incarnation_cross” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.10 ▲ functional
- 6 Oct 26 75
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/human-design
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/human-design | Verified | 200 | |
| http (plaintext) | http://mcp.astroway.info/mcp/human-design | HTTPS enforced | 301 | https://mcp.astroway.info/mcp/human-design |
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_hd_circuitry HD Circuitry Analysis ~449
Analyze which of the 3 Circuits (Tribal, Individual, Collective) and 6 Sub-circuits are activated in a Human Design chart based on defined channels. [Group: Human Design] [Endpoint: POST /v1/hd/circuitry] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]
| 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 |
|---|---|---|---|
| circuits | – | – | – |
| totalActive | – | – | – |
No examples provided.
astroway_hd_design_date HD Design Date ~440
Find the Design date (the moment 88° of solar arc before birth) for a given birth moment, the unconscious imprinting point. [Group: Human Design] [Endpoint: POST /v1/hd/design-date] [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 |
|---|---|---|---|
| birthJd | – | – | – |
| designDate | – | – | – |
| designJd | – | – | – |
No examples provided.
astroway_hd_dream_rave Dream Rave ~445
Calculate the Dream Rave chart: sleep type, active gates in lower centers (Sacral, Solar Plexus, Root), and dream themes. [Group: Human Design] [Endpoint: POST /v1/hd/dream-rave] [Required: date, time, latitude, longitude] [Cost: 50 credits (Tier 3)]
| 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 |
|---|---|---|---|
| activeGates | – | – | – |
| activePortals | – | – | – |
| centers | – | – | – |
| channels | – | – | – |
| type | – | – | – |
| weakPoints | – | – | – |
No examples provided.
astroway_hd_group_overlay HD Group Overlay ~153
Calculate a combined HD group overlay chart for 2 or more people, showing collectively defined centers and channels. [Group: Human Design] [Endpoint: POST /v1/hd/group-overlay] [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 |
|---|---|---|---|
| count | – | – | – |
| definedCenters | – | – | – |
| definedChannels | – | – | – |
| openCenters | – | – | – |
No examples provided.
astroway_hd_hologenetic Hologenetic Profile ~438
Calculate the Gene Keys hologenetic profile (Activation Sequence, Venus Sequence, Pearl Sequence) from HD gate activations. [Group: Human Design] [Endpoint: POST /v1/hd/hologenetic] [Required: date, time, latitude, longitude] [Cost: 50 credits (Tier 3)]
| 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 |
|---|---|---|---|
| activationSequence | – | – | – |
| pearlSequence | – | – | – |
| spheres | – | – | – |
| venusSequence | – | – | – |
No examples provided.
astroway_hd_human_design Human Design Chart ~522
Calculate a full Human Design BodyGraph chart: type, strategy, authority, profile, definition, incarnation cross, centers, channels, and gate activations. Centre identifiers are PascalCase with no separator and are stable: Head, Ajna, Throat, G, Heart, SolarPlexus, Spleen, Sacral, Root. `channels[].centerA` and `centerB` use the same nine. These identifiers are English and have no localised twin yet, unlike the sign and planet names on /public/moon-phase. [Group: Human Design] [Endpoint: POST /v1/human-design] [Required: date, time, latitude, longitude] [Cost: 50 credits (Tier 3)]
| 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 |
|---|---|---|---|
| activations | – | – | – |
| authority | – | – | – |
| centers | – | – | – |
| channels | – | – | – |
| cross | – | – | – |
| definition | – | – | – |
| designActivations | – | – | – |
| designJd | – | – | – |
| input | – | – | – |
| notSelfTheme | – | – | – |
| personalityActivations | – | – | – |
| personalityJd | – | – | – |
| profile | – | – | – |
| strategy | – | – | – |
| type | – | – | – |
No examples provided.
astroway_hd_human_design_compatibility HD Compatibility ~497
Calculate Human Design connection chart (compatibility) between two people: electromagnetic connections, compromise, dominance, and companionship channels. [Group: Human Design] [Endpoint: POST /v1/human-design/compatibility] [Required: chart1, chart2] [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. |
| 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 |
|---|---|---|---|
| attractionScore | – | – | – |
| chart1 | – | – | – |
| chart2 | – | – | – |
| combinedDefinedCenters | – | – | – |
| combinedDefinition | – | – | – |
| companionship | – | – | – |
| compromise | – | – | – |
| connections | – | – | – |
| dominance | – | – | – |
| electromagnetic | – | – | – |
No examples provided.
astroway_hd_human_design_transits HD Transits ~168
Calculate current Human Design transit activations. Optionally overlay on natal chart to show combined defined centers and channels. [Group: Human Design] [Endpoint: POST /v1/human-design/transits] [Cost: 50 credits (Tier 3)]
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | yes | Transit moment plus an optional natal date, time and offset to overlay the activations on. |
| 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 |
|---|---|---|---|
| combinedCenters | – | – | – |
| combinedChannels | – | – | – |
| transitActivations | – | – | – |
No examples provided.
astroway_hd_incarnation_cross Incarnation Cross ~484
Return the Incarnation Cross from birth data (or directly from gate numbers). Includes cross name, type, and theme description. With gate numbers, personalitySunLine and designSunLine decide the angle: lines 1-3 and profile 4/6 are right angle, 4/1 juxtaposition, 5 and 6 left angle. [Group: Human Design] [Endpoint: POST /v1/hd/incarnation-cross] [Required: date, time, latitude, longitude] [Cost: 50 credits (Tier 3)]
| 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 |
|---|---|---|---|
| gates | – | – | – |
| lines | – | – | – |
| name | – | – | – |
| theme | – | – | – |
| type | – | – | – |
No examples provided.
astroway_hd_penta Penta Chart ~157
Calculate the Penta (group) chart for 3–5 people: combined BodyGraph showing group dynamics and collective conditioning. [Group: Human Design] [Endpoint: POST /v1/hd/penta] [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 |
|---|---|---|---|
| channels | – | – | – |
| definedCenters | – | – | – |
| pentaAuthority | – | – | – |
| role | – | – | – |
| size | – | – | – |
No examples provided.
astroway_hd_rave_new_years Rave New Years ~174
Calculate Rave New Year dates (exact moment Sun enters Gate 41) for a range of years. Max range: 50 years. [Group: Human Design] [Endpoint: POST /v1/hd/rave-new-years] [Required: startYear, endYear] [Cost: 10 credits (Tier 1)]
| Name | Type | Req | Description |
|---|---|---|---|
| endYear | – | 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. |
| precision | integer | – | Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. |
| startYear | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | – | – |
| years | – | – | – |
No examples provided.
astroway_hd_sensitivity HD Time Sensitivity ~439
Analyze how sensitive the HD chart type/authority is to birth time changes. Returns windows where the chart is stable vs. in transition. [Group: Human Design] [Endpoint: POST /v1/hd/sensitivity] [Required: date, time, latitude, longitude] [Cost: 50 credits (Tier 3)]
| 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 |
|---|---|---|---|
| confidence | – | – | – |
| stableWindow | – | – | – |
| transitions | – | – | – |
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.
What is the AstroWay Human Design MCP server?
AstroWay Human Design is an MCP server listed in the public MCP registry as info.astroway/human-design. Bodygraph, centres, channels, incarnation cross, penta and group overlay. This page covers its hosted endpoint (https://mcp.astroway.info/mcp/human-design).
Is the AstroWay Human Design MCP server safe to use?
AstroWay Human Design scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AstroWay Human Design MCP server expose?
AstroWay Human Design exposes 27 tools: astroway_account_status, astroway_cost_estimate, astroway_agent_tools, astroway_mcp_ai_chat, astroway_mcp_ai_comparison_coach, and 22 more. Their descriptions and schemas cost roughly 8,435 tokens of context every time the server is loaded.
Does the AstroWay Human Design MCP server require authentication?
Yes. AstroWay Human Design 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 Human Design MCP server still maintained?
AstroWay Human Design 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.