MysticAPI
REMOTE · MYSTICAPI.COM
Human Design & astrology engine: bodygraph, personal-sky SVG, today's sky. JPL ephemeris.
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 901 tokens (~128/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Oct 26 0
- Schema quality: 727 → 901 ▼ functional
- Tool coverage: 31% → 36% ▲ functional
- New tool “signature_lookup” functional
- 28 Sept 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
- 25 Sept 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
- 26 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 12 Aug 26 0
- HSTS header: fail → pass ▲ security
- 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
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 5 Nov 2026 · Probed https://mysticapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mysticapi.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b2e480c065ad8d55134b43e2fc3b6452 |
| SANs: mysticapi.com, *.mysticapi.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 mysticapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mysticapi.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=15552000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), usb=(), browsing-topics=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mysticapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://mysticapi.com/mcp | Inconclusive | 405 |
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 →
bodygraph ~131
Compute an Energy Blueprint (Human Design) chart from a UTC birth instant. Returns type, authority, strategy, profile, definition, incarnation cross, channels, defined centers, and conscious/unconscious gate maps, plus a body-graph SVG. Location is NOT needed. Convert local birth time to UTC before calling. Costs 1 call.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | – |
| hour | integer | yes | Hour 0-23 in UTC |
| minute | integer | yes | – |
| month | integer | yes | – |
| second | integer | – | – |
| year | integer | yes | 4-digit year (UTC) |
No output schema declared.
No examples provided.
ephemeris ~121
Raw geocentric ecliptic positions for any instant (UTC): 13 bodies (Sun through Pluto, Chiron, lunar nodes) with longitude and retrograde flags. JPL-validated ephemeris (Meeus + Standish 1992). Costs 1 call.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | – |
| hour | integer | yes | Hour 0-23 in UTC |
| minute | integer | yes | – |
| month | integer | yes | – |
| second | integer | – | – |
| year | integer | yes | 4-digit year (UTC) |
No output schema declared.
No examples provided.
numerology ~119
Numerology profile from a birth date (UTC): Pythagorean life path (master numbers 11/22/33 preserved), birthday number, personal year/month/day cycles, and tarot birth card. Time fields are accepted but only the date matters. Costs 1 call.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | – |
| hour | integer | yes | Hour 0-23 in UTC |
| minute | integer | yes | – |
| month | integer | yes | – |
| second | integer | – | – |
| year | integer | yes | 4-digit year (UTC) |
No output schema declared.
No examples provided.
relationship ~77
Composite/connection chart for two people from their UTC birth instants: electromagnetic channels (chemistry), dominance, companionship, and compromise channels, combined definition, and type/authority/profile dynamics. Canonical Energy Blueprint (Human Design) relationship analysis. Costs 1 call.
| Name | Type | Req | Description |
|---|---|---|---|
| personA | object | yes | – |
| personB | object | yes | – |
No output schema declared.
No examples provided.
signature_lookup ~174
Ratified Kairos' Council figure-signature canon (cross-product canon, ratified 2026-07-19): 9 signature templates and 35 carrier figures with template assignment, one-line historical argument, parameterization, and primary forge. Input: `figure` (name or slug) for one figure, or `template` (T1–T9 or name) for a template and all its carriers. Static canon data — deterministic. Costs 1 call.
| Name | Type | Req | Description |
|---|---|---|---|
| figure | string | – | Figure name or slug, e.g. "Joan of Arc" or "joan-of-arc". Returns that figure's canon record. |
| template | string | – | Signature template id (T1–T9) or name (e.g. "Last Testament"). Returns the template and every ratified carrier. |
No output schema declared.
No examples provided.
sky_personal ~124
Render a personal natal sky as an SVG from a UTC birth instant: each body placed on the wheel, retrogrades marked, fixed stars conjunct natal points lit. Deterministic (same birth → same sky). Convert local birth time to UTC before calling. Returns SVG markup. Costs 1 call.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | – |
| hour | integer | yes | Hour 0-23 in UTC |
| minute | integer | yes | – |
| month | integer | yes | – |
| second | integer | – | – |
| year | integer | yes | 4-digit year (UTC) |
No output schema declared.
No examples provided.
sky_today ~83
Today's universal sky: which planets are retrograde right now, the current moon phase and illumination, geocentric positions for 13 bodies (zodiac sign + Energy Blueprint gate/line), and a 30-day forward scan of retrograde stations and new/full moons. No input. Deterministic astronomy (JPL-validated ephemeris). Costs 1 call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the MysticAPI MCP server?
MysticAPI is a hosted endpoint at https://mysticapi.com/mcp, 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 · mysticapi.com
claude mcp add --transport http latimer-woods-tech-mysticapi 'https://mysticapi.com/mcp'
What is the MysticAPI MCP server?
MysticAPI is an MCP server listed in the public MCP registry as io.github.Latimer-Woods-Tech/mysticapi. Human Design & astrology engine: bodygraph, personal-sky SVG, today's sky. JPL ephemeris. This page covers its hosted endpoint (https://mysticapi.com/mcp).
Is the MysticAPI MCP server safe to use?
MysticAPI scores 71 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 MysticAPI MCP server expose?
MysticAPI exposes 7 tools: sky_today, bodygraph, sky_personal, ephemeris, numerology, and 2 more. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.
Does the MysticAPI MCP server require authentication?
No. We connected to MysticAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MysticAPI MCP server still maintained?
MysticAPI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.