Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Human Design MCP Server by RoxyAPI

REMOTE · ROXYAPI.COM · SCANNED SEP 20

Human Design bodygraph, type, authority, profile, gates and channels for AI agents.

Available components

0 this week 87 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6492 tokens (~541/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management95
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
Install

How do I install the Human Design MCP Server by RoxyAPI server?

Human Design MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/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 · roxyapi.com

# add to Claude Code
claude mcp add --transport http com-roxyapi-human-design 'https://roxyapi.com/mcp/human-design'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-roxyapi-human-design": {
      "url": "https://roxyapi.com/mcp/human-design"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-roxyapi-human-design": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/human-design"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-roxyapi-human-design --url 'https://roxyapi.com/mcp/human-design' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-roxyapi-human-design:
    url: "https://roxyapi.com/mcp/human-design"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-roxyapi-human-design": {
      "Transport": "http",
      "Url": "https://roxyapi.com/mcp/human-design"
    }
  }
}
# add to Vellum
assistant mcp add com-roxyapi-human-design -t streamable-http -u 'https://roxyapi.com/mcp/human-design'
// mcp.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 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.

  • 19 Sept 26 0
    • Stability: pass → fail security
    • A breaking change shipped without a version bump: still 2.0.0 security
    • “get_human_design_gates_number” changed the type of “number”: integer|null → integer functional
  • 17 Sept 26 0
    • “post_human_design_bodygraph” reworded the description of “timezone” cosmetic
    • “post_human_design_centers” reworded the description of “timezone” cosmetic
    • “post_human_design_channels” reworded the description of “timezone” cosmetic
    • “post_human_design_gates” reworded the description of “timezone” cosmetic
    • “post_human_design_profile” reworded the description of “timezone” cosmetic
    • “post_human_design_type” reworded the description of “timezone” cosmetic
    • “post_human_design_variables” reworded the description of “timezone” cosmetic

    7 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 2 Sept 26 0
    • Stability: fail → pass security
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 91 to 95.

  • 23 Aug 26 +1
    • “post_human_design_bodygraph” reworded the description of “nodeType” cosmetic
    • “post_human_design_centers” reworded the description of “nodeType” cosmetic
    • “post_human_design_channels” reworded the description of “nodeType” cosmetic
    • “post_human_design_gates” reworded the description of “nodeType” cosmetic
    • “post_human_design_profile” reworded the description of “nodeType” cosmetic
    • “post_human_design_type” reworded the description of “nodeType” cosmetic
    • “post_human_design_variables” reworded the description of “nodeType” cosmetic

    7 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 15 Aug 26 0
    • Authorization: unverified → partial security
    • Schema quality: 536 → 474 functional
    • Schema quality: fail → pass functional
    • “get_human_design_centers_id” reworded the description of “compact” cosmetic
    • “get_human_design_gates_number” reworded the description of “compact” cosmetic
    • “post_human_design_bodygraph” reworded the description of “compact” cosmetic
    • “post_human_design_centers” reworded the description of “compact” cosmetic
    • “post_human_design_channels” reworded the description of “compact” cosmetic
    • “post_human_design_connection” reworded the description of “compact” cosmetic
    • “post_human_design_gates” reworded the description of “compact” cosmetic
    • “post_human_design_penta” reworded the description of “compact” cosmetic
    • “post_human_design_profile” reworded the description of “compact” cosmetic
    • “post_human_design_transit” reworded the description of “compact” cosmetic
    • “post_human_design_type” reworded the description of “compact” cosmetic
    • “post_human_design_variables” reworded the description of “compact” cosmetic
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 20 Sept 2026 · Probed https://roxyapi.com/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=roxyapi.com CN=WE1,O=Google Trust Services,C=US 26 Jul 2026 24 Oct 2026 ECDSA 256 ECDSA-SHA256 fb04ac30ca01abb60e3558bdfadfe2f4
SANs: roxyapi.com, *.roxyapi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of roxyapi.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
roxyapi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' 'unsafe-eval' https://challenges.cloudflare.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; img-src 'self' data: https:; font-src 'self' https://fonts.scalar.com; connect-src 'self' https://api.scalar.com https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src https://challenges.cloudflare.com https://roxyapi.github.io; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), accelerometer=(), gyroscope=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://roxyapi.com/mcp/human-design Verified 200
http (plaintext) http://roxyapi.com/mcp/human-design HTTPS enforced 301 https://roxyapi.com/mcp/human-design
MCP tools · 12 exposed · ~6,492 tokens

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 →

Tool Tokens
get_human_design_centers_id ~212

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
idstringyesCenter id. One of head, ajna, throat, g, heart, sacral, solar-plexus, spleen, root.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…

No output schema declared.

{"id":"sacral"}
get_human_design_gates_number ~202

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
numberintegeryesGate number from 1 to 64.

No output schema declared.

{"number":34}
post_human_design_bodygraph ~752

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
longitudenumberBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
timezoneyesIANA 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 o…

No output schema declared.

{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}
post_human_design_centers ~721

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
longitudenumberBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
timezoneyesIANA 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 o…

No output schema declared.

{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}
post_human_design_channels ~727

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
longitudenumberBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
timezoneyesIANA 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 o…

No output schema declared.

{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}
post_human_design_connection ~247

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
personAobjectyesBirth moment of the first person in the connection.
personBobjectyesBirth moment of the second person in the connection.

No output schema declared.

{"personA":{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"},"personB":{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}}
post_human_design_gates ~731

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
longitudenumberBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
timezoneyesIANA 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 o…

No output schema declared.

{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}
post_human_design_penta ~310

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
membersarrayyesBirth moments of the three to five people in the group. Below three no Penta forms; above five a second Penta emerges.

No output schema declared.

No examples provided.

post_human_design_profile ~717

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
longitudenumberBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
timezoneyesIANA 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 o…

No output schema declared.

{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}
post_human_design_transit ~349

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.

NameTypeReqDescription
birthDataobjectyesBirth moment whose natal bodygraph the transit is overlaid on.
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringTransit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
timestringTransit 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.

No output schema declared.

{"birthData":{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}}
post_human_design_type ~718

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
longitudenumberBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
timezoneyesIANA 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 o…

No output schema declared.

{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}
post_human_design_variables ~806

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.

NameTypeReqDescription
compactbooleanSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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.
langstringResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
longitudenumberBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
nodeTypestringLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
timezoneyesIANA 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 o…

No output schema declared.

{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}
Common questions

What is the Human Design MCP Server by RoxyAPI server?

Human Design MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/human-design. Human Design bodygraph, type, authority, profile, gates and channels for AI agents. This page covers its hosted endpoint (https://roxyapi.com/mcp/human-design).

Is the Human Design MCP Server by RoxyAPI server safe to use?

Human Design MCP Server by RoxyAPI scores 87 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 Human Design MCP Server by RoxyAPI server expose?

Human Design MCP Server by RoxyAPI exposes 12 tools: post_human_design_bodygraph, post_human_design_connection, post_human_design_penta, post_human_design_transit, post_human_design_type, and 7 more. Their descriptions and schemas cost roughly 6,492 tokens of context every time the server is loaded.

Does the Human Design MCP Server by RoxyAPI server require authentication?

No. We connected to Human Design MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Human Design MCP Server by RoxyAPI server still maintained?

Human Design MCP Server by RoxyAPI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.