# Human Design MCP Server by RoxyAPI (remote · roxyapi.com) Human Design bodygraph, type, authority, profile, gates and channels for AI agents. - Trust score: 65/100 (medium) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `roxyapi.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-roxyapi-human-design/mcp-human-design.md), [page](https://verifymcp.io/servers/com-roxyapi-human-design/mcp-human-design) ## Channel facts - Endpoint: `https://roxyapi.com/mcp/human-design` - Transports: `streamable-http` - Auth: `required` - Version: `1.0.0` ## 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-08-03. - **Endpoint Security**: 63/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - 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**: 58/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 6272 tokens (~522/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 21/100 - Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http com-roxyapi-human-design https://roxyapi.com/mcp/human-design ``` ### Codex ```toml [mcp_servers.com-roxyapi-human-design] url = "https://roxyapi.com/mcp/human-design" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-roxyapi-human-design": { "type": "remote", "url": "https://roxyapi.com/mcp/human-design", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-roxyapi-human-design --url https://roxyapi.com/mcp/human-design --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-roxyapi-human-design: url: "https://roxyapi.com/mcp/human-design" ``` ### Other ```json { "mcpServers": { "com-roxyapi-human-design": { "type": "http", "url": "https://roxyapi.com/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-08-03 (score 65, 0) - [security regression] Stability: 0.23 → fail - [security regression] A breaking change shipped without a version bump: still 2.0.0 - [functional regression] “get_human_design_gates_number” changed the type of “number”: integer → integer|null ### 2026-08-01 (score 65, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 64, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 63, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-28 (score 62, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 61, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 60) First indexed and scored. ## MCP tools (12) ### `post_human_design_bodygraph` (~689 tokens) Generate full Human Design bodygraph - Type, authority, profile, centers, channels, gates Generate a complete Human Design bodygraph from a birth date, time, and timezone. Returns the energy type, strategy, inner authority, signature, not-self theme, profile, definition, incarnation cross, all nine centers with defined state and active gates, the defined channels, and all 26 planetary activations across the Personality and Design sides. The single endpoint for a full chart in one call, built for Human Design apps, readings, and coaching tools. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string, required): Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `latitude` (number): Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. - `longitude` (number): Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. - `nodeType` (string): Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (… - `time` (string, required): Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the D… ### `post_human_design_connection` (~291 tokens) Calculate Human Design connection chart - Two-person composite bodygraph compatibility Calculate a Human Design connection chart by overlaying two bodygraphs. For each of the 36 channels the dynamic between the two people is classified as electromagnetic, dominance, compromise, or companionship, the four mechanics of how two designs meet. Also returns the nine centers as defined or open in the combined bodygraph with which person defines each, the combined definition, and a count of each dynamic. Built for relationship, dating, and coaching tools. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `personA` (object, required): Birth moment of the first person in the connection. - `personB` (object, required): Birth moment of the second person in the connection. ### `post_human_design_penta` (~354 tokens) Calculate Human Design Penta - Small-group BG5 operating system for three to five people Calculate the Human Design Penta (BG5, Base Group 5) for a small group of three to five people. The Penta is a trans-auric form built from a fixed set of six channels running only between the Sacral, the G Center, and the Throat. It reports which of the twelve Penta gates are filled and by whom, which of the six channels are defined Strengths, the upper leadership channels versus the lower generative channels, the 2/14 material core, and the functional gaps where no member supplies a role. Built for team, family, and group analysis tools. Below three people no Penta forms and above five a second Penta emerges, so the group size must be three to five. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `members` (array, required): Birth moments of the three to five people in the group. Below three no Penta forms; above five a second Penta emerges. ### `post_human_design_transit` (~393 tokens) Generate Human Design transit overlay - Current planetary activations on a natal bodygraph Overlay the current or any given planetary positions on a natal Human Design bodygraph to see which channels the transit temporarily completes. Returns the 13 transiting body activations with gate and line, the channels the transit completes beyond the natal definition split into personal channels where the transit supplies the partner gate of a natal gate and educational channels where the transit supplies both gates, the natally open centers those channels temporarily define, and a short factual summary. A transit is a single moment, so there is no Design side. When date and time are omitted the overlay is computed for now in UTC. Built for daily Human Design apps, transit widgets, and notification tools. Input parameters: - `birthData` (object, required): Birth moment whose natal bodygraph the transit is overlaid on. - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string): Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `time` (string): Transit time in HH:MM:SS UTC. Optional. Defaults to the current UTC time when omitted. Precision matters: the Moon moves through a gate in roughly half a day. ### `post_human_design_type` (~655 tokens) Calculate Human Design type, authority and profile Calculate the core Human Design identity from a birth moment: the energy type, the aura strategy, the inner authority, the signature and not-self themes, and the profile. The fast lookup for type-and-authority features without the full bodygraph payload. Verified against NASA JPL Horizons positions. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string, required): Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `latitude` (number): Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. - `longitude` (number): Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. - `nodeType` (string): Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (… - `time` (string, required): Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the D… ### `post_human_design_gates` (~668 tokens) Calculate the 26 Human Design gate activations Calculate the 26 gate activations for a birth moment, split into the 13 conscious Personality activations at birth and the 13 unconscious Design activations 88 degrees of solar arc earlier. Each activation reports the planet, gate, line, gate keynote, and the matching I-Ching hexagram. Built for activation columns and detailed chart views. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string, required): Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `latitude` (number): Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. - `longitude` (number): Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. - `nodeType` (string): Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (… - `time` (string, required): Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the D… ### `get_human_design_gates_number` (~247 tokens) Look up a Human Design gate by number Look up the static reference data for a Human Design gate by its number from 1 to 64: the gate keynote name, the center it sits in, the matching I-Ching hexagram, and the gates that form a channel with it. A pure reference endpoint with no birth data required. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `number` (integer|null, required): Gate number from 1 to 64. ### `post_human_design_channels` (~664 tokens) Calculate the defined Human Design channels Calculate the defined channels for a birth moment. A channel is defined when both of its gates are activated, and it wires together the two centers it connects. Returns each defined channel with its gates, name, circuit family, and connected centers, plus the full set of centers those channels define. Built for bodygraph rendering and definition analysis. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string, required): Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `latitude` (number): Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. - `longitude` (number): Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. - `nodeType` (string): Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (… - `time` (string, required): Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the D… ### `post_human_design_centers` (~658 tokens) Calculate the nine Human Design centers Calculate the state of all nine Human Design centers for a birth moment: whether each is defined or open, whether it is a motor or an awareness center, its theme, and the active gates it holds. The data layer behind a rendered bodygraph where defined centers are colored and open centers are white. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string, required): Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `latitude` (number): Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. - `longitude` (number): Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. - `nodeType` (string): Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (… - `time` (string, required): Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the D… ### `get_human_design_centers_id` (~256 tokens) Look up a Human Design center by id Look up the static reference data for one of the nine Human Design centers by its id: the display name, whether it is a motor or awareness center, and what it means both defined and undefined. A pure reference endpoint with no birth data required. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `id` (string, required): Center id. One of head, ajna, throat, g, heart, sacral, solar-plexus, spleen, root. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. ### `post_human_design_profile` (~654 tokens) Calculate the Human Design profile and line keynotes Calculate the Human Design profile for a birth moment: the conscious Personality Sun line over the unconscious Design Sun line, with the keynote for each. The profile is the geometry of the life role, for example 5/1 the Heretic Investigator. Verified against NASA JPL Horizons positions. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string, required): Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `latitude` (number): Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. - `longitude` (number): Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. - `nodeType` (string): Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (… - `time` (string, required): Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the D… ### `post_human_design_variables` (~743 tokens) Calculate Human Design Variables - The four arrows and Color, Tone, Base substructure Calculate the four Human Design Variable arrows for a birth moment: Determination and Environment on the design side, Perspective and Motivation on the personality side. Each arrow returns its Color, Tone, and Base numbers from the hexagram-line substructure, the left or right direction set by the Tone, and the sourced Color and direction labels. This is the advanced Rave Variables and Primary Health System layer beneath Type, Strategy, Authority, and Profile. Color, Tone, and Base shift with tiny differences in birth time, so each arrow carries a confidence flag that turns false near a Color or Tone boundary, and a precise birth time is essential. Built for Human Design apps offering PHS, diet, environment, and Rave Psychology readings. Input parameters: - `compact` (boolean): Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… - `date` (string, required): Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier. - `lang` (string): Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. - `latitude` (number): Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. - `longitude` (number): Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. - `nodeType` (string): Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (… - `time` (string, required): Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the D… ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-roxyapi-human-design/mcp-human-design#diagnostics ## Score history - 2026-08-03: 65 - 2026-08-02: 65 - 2026-08-01: 65 - 2026-07-31: 64 - 2026-07-30: 63 - 2026-07-29: 62 - 2026-07-28: 62 - 2026-07-27: 61 - 2026-07-26: 60 ## Links - Remote endpoint: https://roxyapi.com/mcp/human-design - Authorisation metadata: https://roxyapi.com/.well-known/oauth-protected-resource/mcp/human-design - Website: https://roxyapi.com/products/human-design-api - Changelog RSS feed: https://verifymcp.io/servers/com-roxyapi-human-design/mcp-human-design/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/com-roxyapi-human-design/mcp-human-design/changelog.json - HTML version of this page: https://verifymcp.io/servers/com-roxyapi-human-design/mcp-human-design