# AstroWay Human Design (remote · mcp.astroway.info)

Bodygraph, centres, channels, incarnation cross, penta and group overlay.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-10

## Components

- remote · `mcp.astroway.info`: 77/100 (this document), [markdown](https://verifymcp.io/servers/info-astroway-human-design/mcp-human-design.md), [page](https://verifymcp.io/servers/info-astroway-human-design/mcp-human-design)

## Channel facts

- Endpoint: `https://mcp.astroway.info/mcp/human-design`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.4.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-10.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 9331 tokens (~227/item across 41 items; 27 tools + 14 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
  - Structured output schemas are declared (85% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AstroWay 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.

### Claude

```bash
claude mcp add --transport http info-astroway-human-design 'https://mcp.astroway.info/mcp/human-design'
```

### Cursor

```json
{
  "mcpServers": {
    "info-astroway-human-design": {
      "url": "https://mcp.astroway.info/mcp/human-design"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "info-astroway-human-design": {
      "type": "http",
      "url": "https://mcp.astroway.info/mcp/human-design"
    }
  }
}
```

### Codex

```toml
[mcp_servers.info-astroway-human-design]
url = "https://mcp.astroway.info/mcp/human-design"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "info-astroway-human-design": {
      "type": "remote",
      "url": "https://mcp.astroway.info/mcp/human-design",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add info-astroway-human-design --url 'https://mcp.astroway.info/mcp/human-design' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  info-astroway-human-design:
    url: "https://mcp.astroway.info/mcp/human-design"
```

### Netclaw

```json
{
  "McpServers": {
    "info-astroway-human-design": {
      "Transport": "http",
      "Url": "https://mcp.astroway.info/mcp/human-design"
    }
  }
}
```

### Vellum

```bash
assistant mcp add info-astroway-human-design -t streamable-http -u 'https://mcp.astroway.info/mcp/human-design'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-10 (score 77, 0)

- [security] 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

### 2026-10-09 (score 77, +2)

- [security] Tool “astroway_hd_incarnation_cross” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.10

### 2026-10-06 (score 75)

First indexed and scored.

## MCP tools (27)

### `astroway_account_status` (~73 tokens)

Account Status

Check current API key status: tier, credit balance, rate limits, monthly cycle reset. Run this BEFORE invoking expensive endpoints (Tier 4+ at 100+ credits, Tier 6/7 at 500-5000 credits) to confirm the user has budget. Returns plain-text human-readable summary.

### `astroway_cost_estimate` (~91 tokens)

Cost Estimate

Estimate the credit cost of one or more endpoints WITHOUT invoking them. Returns total + per-endpoint breakdown with tier annotations. Useful when planning multi-step workflows: estimate first, ask user confirmation, then invoke. Cache TTL 5 min.

Input parameters:

- `endpoints` (array, required): Endpoint paths to estimate, e.g. ["/chart", "/synastry", "/reports/natal"]. Leading slash optional.

### `astroway_agent_tools` (~405 tokens)

Agent tool definitions

Tool definitions for an agent framework, generated from the live OpenAPI document, so the schema a model fills is the schema the endpoint validates. `format=openai` (default) returns `{ type, function }` objects you can spread straight into a chat completion; `format=anthropic` returns `{ name, description, input_schema }`. The objects carry nothing of ours: how to call each tool lives in a separate `executors` map keyed by tool name, because an unexpected key inside a vendor tool object is a 400 at their end.

[Group: Agent Platform]
[Endpoint: GET /v1/agent/tools]
[Cost: see your plan — endpoint not in the public credit manifest]

Input parameters:

- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `format` (string): Which vendor contract the tool objects follow. `openai` returns `{ type, function }`, `anthropic` returns `{ name, description, input_schema }`.
- `limit` (integer): How many tools to return. The ceiling is the OpenAI limit of 128 functions per request; models degrade well before it. Anything left out is counted in `totalMatched`.
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `q` (string): Free-text filter applied within the selection, matched against path, summary, description and group.
- `select` (string): What to hand over: `starter` (the curated set, the default), `all`, `group:<tag>` such as `group:Vedic`, or `paths:/chart,/synastry` for an explicit list. An unknown path is named in `notes` rather t…

Output parameters:

- `count`
- `executors`
- `format`
- `notes`
- `select`
- `tools`
- `totalAvailable`
- `totalMatched`
- `truncated`

### `astroway_mcp_ai_chat` (~387 tokens)

Chart-grounded AI chat

Chat answered from the positions we computed for this birth moment, not from the model's memory of a sun sign. Carries up to 10 turns of history, replies in 21 languages, and takes four voices through `persona`. Send your own provider key and the turn costs 5 credits instead of the endpoint price.

[Group: AI & MCP]
[Endpoint: POST /v1/ai/chat]
[Required: message]
[Cost: 100 credits (Tier 4)]

Input parameters:

- `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `history` (array)
- `language` (string)
- `message` (string, required)
- `persona` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `disclaimer`
- `duration_ms`
- `language`
- `model`
- `persona`
- `reply`
- `tokens`

### `astroway_mcp_ai_comparison_coach` (~497 tokens)

Comparison Coach

Coach two charts on relationship dynamics.

[Group: AI & MCP]
[Endpoint: POST /v1/ai/comparison-coach]
[Required: chart1, chart2, question]
[Cost: 100 credits (Tier 4)]

Input parameters:

- `chart1` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `chart2` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `language` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `question` (string, required)

Output parameters:

- `coaching`

### `astroway_mcp_ai_explain_aspect` (~347 tokens)

Explain Aspect

Detailed explanation of an aspect between two planets.

[Group: AI & MCP]
[Endpoint: POST /v1/ai/explain-aspect]
[Required: planet1, planet2, aspectType]
[Cost: 100 credits (Tier 4)]

Input parameters:

- `aspectType` (string, required)
- `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `language` (string)
- `planet1` (string, required)
- `planet2` (string, required)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `explanation`

### `astroway_mcp_ai_explain_transit` (~360 tokens)

Explain Transit

Explain a current transit hitting your natal chart.

[Group: AI & MCP]
[Endpoint: POST /v1/ai/explain-transit]
[Required: chart, transitDate, transitPlanet, natalPlanet, aspectType]
[Cost: 100 credits (Tier 4)]

Input parameters:

- `aspectType` (string, required)
- `chart` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `language` (string)
- `natalPlanet` (string, required)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `transitDate` (string, required)
- `transitPlanet` (string, required)

Output parameters:

- `explanation`

### `astroway_hd_circuitry` (~449 tokens)

HD Circuitry Analysis

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)]

Input parameters:

- `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
- `ayanamsaId`
- `city` (string)
- `cosmogram` (boolean)
- `date` (string, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `houseSystem` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `name` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `time` (string, required)
- `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it…
- `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
- `zodiacType` (string)

Output parameters:

- `circuits`
- `totalActive`

### `astroway_hd_design_date` (~440 tokens)

HD Design Date

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)]

Input parameters:

- `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
- `ayanamsaId`
- `city` (string)
- `cosmogram` (boolean)
- `date` (string, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `houseSystem` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `name` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `time` (string, required)
- `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it…
- `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
- `zodiacType` (string)

Output parameters:

- `birthJd`
- `designDate`
- `designJd`

### `astroway_hd_dream_rave` (~445 tokens)

Dream Rave

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)]

Input parameters:

- `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
- `ayanamsaId`
- `city` (string)
- `cosmogram` (boolean)
- `date` (string, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `houseSystem` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `name` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `time` (string, required)
- `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it…
- `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
- `zodiacType` (string)

Output parameters:

- `activeGates`
- `activePortals`
- `centers`
- `channels`
- `type`
- `weakPoints`

### `astroway_hd_group_overlay` (~153 tokens)

HD Group Overlay

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)]

Input parameters:

- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `inputs` (array, required)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `count`
- `definedCenters`
- `definedChannels`
- `openCenters`

### `astroway_hd_hologenetic` (~438 tokens)

Hologenetic Profile

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)]

Input parameters:

- `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
- `ayanamsaId`
- `city` (string)
- `cosmogram` (boolean)
- `date` (string, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `houseSystem` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `name` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `time` (string, required)
- `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it…
- `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
- `zodiacType` (string)

Output parameters:

- `activationSequence`
- `pearlSequence`
- `spheres`
- `venusSequence`

### `astroway_hd_incarnation_cross` (~484 tokens)

Incarnation Cross

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)]

Input parameters:

- `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
- `ayanamsaId`
- `city` (string)
- `cosmogram` (boolean)
- `date` (string, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `houseSystem` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `name` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `time` (string, required)
- `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it…
- `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
- `zodiacType` (string)

Output parameters:

- `gates`
- `lines`
- `name`
- `theme`
- `type`

### `astroway_hd_penta` (~157 tokens)

Penta Chart

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)]

Input parameters:

- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `inputs` (array, required)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `channels`
- `definedCenters`
- `pentaAuthority`
- `role`
- `size`

### `astroway_hd_rave_new_years` (~174 tokens)

Rave New Years

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)]

Input parameters:

- `endYear` (required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `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` (required)

Output parameters:

- `count`
- `years`

### `astroway_hd_sensitivity` (~439 tokens)

HD Time Sensitivity

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)]

Input parameters:

- `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
- `ayanamsaId`
- `city` (string)
- `cosmogram` (boolean)
- `date` (string, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `houseSystem` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `name` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `time` (string, required)
- `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it…
- `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
- `zodiacType` (string)

Output parameters:

- `confidence`
- `stableWindow`
- `transitions`

### `astroway_hd_human_design` (~522 tokens)

Human Design Chart

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)]

Input parameters:

- `ayanamsa` (string): Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
- `ayanamsaId`
- `city` (string)
- `cosmogram` (boolean)
- `date` (string, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `houseSystem` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `name` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `time` (string, required)
- `timezone` (string): IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it…
- `timezoneOffset`: Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
- `zodiacType` (string)

Output parameters:

- `activations`
- `authority`
- `centers`
- `channels`
- `cross`
- `definition`
- `designActivations`
- `designJd`
- `input`
- `notSelfTheme`
- `personalityActivations`
- `personalityJd`
- `profile`
- `strategy`
- `type`

### `astroway_hd_human_design_compatibility` (~497 tokens)

HD Compatibility

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)]

Input parameters:

- `chart1` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `chart2` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `attractionScore`
- `chart1`
- `chart2`
- `combinedDefinedCenters`
- `combinedDefinition`
- `companionship`
- `compromise`
- `connections`
- `dominance`
- `electromagnetic`

### `astroway_hd_human_design_transits` (~168 tokens)

HD Transits

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)]

Input parameters:

- `body` (required): 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.

Output parameters:

- `combinedCenters`
- `combinedChannels`
- `transitActivations`

### `astroway_mcp_agent_debate` (~351 tokens)

MCP Agent Debate

2 personas debate a topic, multi-round transcript.

[Group: MCP Advanced]
[Endpoint: POST /v1/mcp/agent-debate]
[Required: topic, agentA, agentB]
[Cost: 100 credits (Tier 4)]

Input parameters:

- `agentA` (string, required)
- `agentB` (string, required)
- `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `language` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `rounds` (integer)
- `topic` (string, required)

Output parameters:

- `transcript`

### `astroway_mcp_agent_pool_status` (~131 tokens)

MCP Agent Pool Status

8 personas with specialties.

[Group: MCP Advanced]
[Endpoint: GET /v1/mcp/agent-pool-status]
[Cost: 10 credits (Tier 1)]

Input parameters:

- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `count`
- `note`
- `personas`

### `astroway_mcp_multi_agent_coordinate` (~330 tokens)

MCP Multi-Agent Coordinate

Run N personas in parallel + LLM synthesis.

[Group: MCP Advanced]
[Endpoint: POST /v1/mcp/multi-agent-coordinate]
[Required: question, agents]
[Cost: 100 credits (Tier 4)]

Input parameters:

- `agents` (array, required)
- `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `language` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `question` (string, required)

Output parameters:

- `individual`
- `synthesis`

### `astroway_mcp_multi_chart_context` (~154 tokens)

MCP Multi-Chart Context

Compact context for MCP agents working across multiple charts.

[Group: AI & MCP]
[Endpoint: POST /v1/mcp/multi-chart-context]
[Required: charts]
[Cost: 10 credits (Tier 1)]

Input parameters:

- `charts` (array, required)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `intent` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `chartCount`
- `contextHash`
- `intent`
- `notes`
- `summaries`
- `summaryString`

### `astroway_mcp_rag_search` (~320 tokens)

MCP RAG Search

Keyword-tag scoring over chart chunks.

[Group: MCP Advanced]
[Endpoint: POST /v1/mcp/rag-search]
[Required: query, chart]
[Cost: 10 credits (Tier 1)]

Input parameters:

- `chart` (object, required): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `query` (string, required)
- `topK` (integer)

Output parameters:

- `matches`
- `query`
- `results`
- `tokens`
- `total`

### `astroway_mcp_streaming` (~322 tokens)

MCP Streaming Chat

Server-Sent Events streaming chat completion with optional chart context.

[Group: AI & MCP]
[Endpoint: POST /v1/mcp/streaming]
[Required: message]
[Cost: 100 credits (Tier 4)]

Input parameters:

- `chart` (object): Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD;…
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `language` (string)
- `message` (string, required)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

### `astroway_mcp_tool_call_stream` (~157 tokens)

MCP Tool-Call Stream

SSE-stream of a tool call envelope.

[Group: MCP Advanced]
[Endpoint: POST /v1/mcp/tool-call-stream]
[Required: tool]
[Cost: 10 credits (Tier 1)]

Input parameters:

- `args` (object)
- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `language` (string)
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
- `tool` (string, required)

### `astroway_mcp_tools_list` (~144 tokens)

MCP Tools List

Auto-generated tool manifest for MCP clients (modelcontextprotocol/2025-03 spec).

[Group: AI & MCP]
[Endpoint: GET /v1/mcp/tools-list]
[Cost: see your plan — endpoint not in the public credit manifest]

Input parameters:

- `fields` (string): Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
- `precision` (integer): Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output parameters:

- `notes`
- `server`
- `spec`
- `toolCount`
- `tools`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/info-astroway-human-design/mcp-human-design#diagnostics

## Score history

- 2026-10-10: 77
- 2026-10-09: 77
- 2026-10-06: 75

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.astroway.info/mcp/human-design
- Authorisation metadata: https://mcp.astroway.info/.well-known/oauth-protected-resource/mcp/human-design
- Website: https://api.astroway.info/en/examples/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/info-astroway-human-design/mcp-human-design.xml
- Changelog JSON feed: https://verifymcp.io/servers/info-astroway-human-design/mcp-human-design.json
- HTML version of this page: https://verifymcp.io/servers/info-astroway-human-design/mcp-human-design