Straight answers about the live MCP server.

It is the official remote agent surface for HumanDesign.ai. Compatible AI clients can use membership-aware account tools through OAuth or six calculation and reference tools through an API key.

No. MCP, Agent HTTP, REST, and HumanDesign.ai delegate chart calculations to the same authoritative service. OAuth and API keys expose different capabilities, but calculation versions and quota decisions remain centralized.

The service validates birth inputs, location, IANA timezone, and daylight-saving context before calculation, returns a versioned structured result, and rejects ambiguous or invalid input before charging. Agents are instructed not to approximate chart mathematics.

As a local wall clock time: exactly as it read on the clock where the person was born, with no Z and no UTC offset, with the zone supplied separately in timezone as an IANA identifier. "birthDateTime": "1990-05-15T14:30:00" with "timezone": "America/New_York" means half past two in the afternoon in New York. A value carrying Z or an offset does not name a wall clock time on its own, and whichever zone something reads it in changes the chart. Never convert a birth time to UTC before sending it.

Not yet. The MCP forwards the value and the API still accepts it, reading it as UTC, and announces the deprecation on its response. Those values will stop being accepted, and the date will be announced in advance. Switching to a bare local wall clock time plus an IANA timezone is the safe change, and for anyone whose value did not really mean UTC it also corrects the chart.

Six: resolve_timezone, generate_chart, generate_composite_chart, get_reference_item, get_transits, and search_celebrities. OAuth adds a separately filtered account catalog based on membership, ownership, role, server-derived capability grants, and entitlements.

Any compatible Streamable HTTP MCP client can connect. The documentation includes guides for Claude, ChatGPT, Codex, Cursor, and VS Code.

generate_chart, generate_composite_chart, and get_transits each consume one unit once a validated request reaches calculation. resolve_timezone, get_reference_item, search_celebrities, initialize, ping, tools/list, invalid input, denied access, library reads, status checks, and rendering an existing chart consume zero.

The three consuming MCP tools require a stable idempotencyKey. Reuse it only with the same normalized arguments for one intended retry. A match consumes no additional quota and may deterministically recompute; it is not byte-for-byte stored-response replay. MCP transit calls also require an explicit date.

Yes. OAuth lets a Free member preview, confirm, create, save, view, and render their own primary chart. The new calculation uses exactly one unit and rendering adds no second charge.

The API-key calculation surface can generate a new two-person composite. Eligible OAuth accounts can retrieve and render authorized saved composites. The server always enforces ownership and membership boundaries.

The server verifies the PNG or SVG before claiming success and also returns a short-lived secure download link as a fallback.

Sign in at HumanDesign.ai for platform membership and account access, or my.humandesign.ai for API keys, API-plan usage, and billing.