Skip to main content
Glama

Celestium: Cosmic Compass

by io.github.nacrissi
OverviewDiscussionsAdmin

Server Details

Real astrology for AI agents: cosmic weather, synastry, timing, astrocartography, and divination.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no risk of confusion between tools. The single tool's actions are listed within its description, but the tool itself is unambiguous.

Naming Consistency3/5

With only one tool named 'celestium', there is no pattern to evaluate. The name is a single noun, not following a verb_noun convention, but it is not inconsistent with any other tool names.

Tool Count1/5

Having a single tool that bundles over 30 actions is a severe mismatch for the server's broad scope. It violates the principle of one tool per distinct operation, making it difficult for agents to discover and invoke specific capabilities.

Completeness4/5

The tool appears to cover a comprehensive set of astrology and divination features, including ephemeris, charts, synastry, tarot, and more. Minor gaps may exist (e.g., unsupported advanced techniques), but the surface is largely complete for the domain.

Available Tools

1 tool
celestiumA
Read-only
Inspect

Celestium: Cosmic Compass — accurate astrology & divination for AI agents, with engine-authored interpretations attached (not LLM guesswork; real ephemeris, verified arcminute-accurate). Includes practice actions: check_in (sky + moment verdict + matched ritual), ritual (step-by-step moon-phase practices), tarot (auditable draws), review (temporal review of a period against your chart). Actions: cosmic_weather, chart, positions, moon, moment_quality, retrograde, voc, planetary_hours, sunrise, ritual, tarot, check_in, natal_reading, iching, mayan, numerology, true_sky, event_debrief, composite, davison, relocation, relocation_score, travel, transits, synastry, timing, progressions, electional, horary, returns, timeline, synthesis, perfections, midpoints, harmonic, antiscia, declination, sidereal, heliacal, review, bazi, year_ahead, correlate, common_threads. Free tier: cosmic_weather, chart, positions, moon, moment_quality, retrograde, voc, planetary_hours, sunrise, ritual, tarot, check_in, natal_reading, iching, mayan, numerology, true_sky, event_debrief. Celestium Pro unlocks depth + relationship charts (synastry/composite/davison), astrocartography (relocation/travel), advanced techniques, and review.

ParametersJSON Schema
NameRequiredDescriptionDefault
dataNoBirth data + params. birth: {name, birth_date (YYYY-MM-DD), birth_time (HH:MM), birth_timezone (IANA), latitude, longitude, birth_location}. partner: same birth shape (synastry/composite/davison; also adds relationship activations to cosmic_weather/check_in). For place-based actions (relocation, relocation_score, planetary_hours, sunrise, heliacal, electional), top-level latitude/longitude = the TARGET location. Plus optional date, start, end, return_type (solar|lunar), city, planet, number (harmonic), orb (antiscia), system (sidereal: lahiri|raman|kp), activity (electional: marriage|business|travel|surgery|legal_matter|creative_work|investment|medical_treatment), ritual: type + max_minutes; tarot: count (1-3) + question; iching: question; check_in: mood, focus, intent, local_hour; review: period (week|month) or start+end; horary: question + house (1-12) + latitude/longitude; bazi: gender (male|female). render: true (natal_reading only) → also returns a viewable_url: a shareable, unlisted, auto-expiring, revocable web page of the chart+reading; render:{ttl_days:N} sets the expiry (default 90d), render:{burn:true} makes it view-once, render:{e2ee:true} encrypts it at rest (key only in the link #fragment; we store ciphertext and cannot read it). Nothing is stored unless you opt in with render; without it, calls are pure compute.
actionYesThe astrology/divination action to run.
identityNoCaller email/identity (resolves entitlement tier; optional in free tier).

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description exceeds annotations by detailing ephemeris accuracy, pure compute nature, storage only on render opt-in, and rendering options (ttl, burn, e2ee). Adds significant context beyond readOnlyHint=true and destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but warranted given the tool's 50+ actions and complex parameters. It front-loads the core purpose and lists actions clearly, though a structured format (e.g., bullet points) would improve scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 3 parameters (one nested object), the description covers actions, tier limitations, ephemeris source, storage behavior, and rendering. It leaves no gaps, even without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description adds deep meaning to the 'data' parameter, explaining partner data, place-based location fields, and render options in detail, far surpassing the schema's property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as 'accurate astrology & divination for AI agents' with engine-authored interpretations. It lists all available actions, distinguishing free vs Pro, and leaves no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains free vs Pro tiers and lists actions available in each, giving implicit guidance on when to use certain actions. However, it lacks explicit 'when to use' vs alternatives, though no siblings exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedcelestium1 field changed
      • changedInput schema / properties / action / enum
        Previous value: -[
-  "cosmic_weather",
-  "chart",
-  "positions",
-  "moon",
-  "moment_quality",
-  "retrograde",
-  "voc",
-  "planetary_hours",
-  "sunrise",
-  "ritual",
-  "tarot",
-  "check_in",
-  "natal_reading",
-  "iching",
-  "mayan",
-  "numerology",
-  "true_sky",
-  "composite",
-  "davison",
-  "relocation",
-  "relocation_score",
-  "travel",
-  "transits",
-  "synastry",
-  "timing",
-  "progressions",
-  "electional",
-  "horary",
-  "returns",
-  "timeline",
-  "synthesis",
-  "perfections",
-  "midpoints",
-  "harmonic",
-  "antiscia",
-  "declination",
-  "sidereal",
-  "heliacal",
-  "review",
-  "bazi",
-  "year_ahead",
-  "correlate",
-  "common_threads"
-]New value: +[
+  "cosmic_weather",
+  "chart",
+  "positions",
+  "moon",
+  "moment_quality",
+  "retrograde",
+  "voc",
+  "planetary_hours",
+  "sunrise",
+  "ritual",
+  "tarot",
+  "check_in",
+  "natal_reading",
+  "iching",
+  "mayan",
+  "numerology",
+  "true_sky",
+  "event_debrief",
+  "composite",
+  "davison",
+  "relocation",
+  "relocation_score",
+  "travel",
+  "transits",
+  "synastry",
+  "timing",
+  "progressions",
+  "electional",
+  "horary",
+  "returns",
+  "timeline",
+  "synthesis",
+  "perfections",
+  "midpoints",
+  "harmonic",
+  "antiscia",
+  "declination",
+  "sidereal",
+  "heliacal",
+  "review",
+  "bazi",
+  "year_ahead",
+  "correlate",
+  "common_threads"
+]
  2. 1 tool update
    • Changedcelestium1 field changed
      • changedInput schema / properties / action / enum
        Previous value: -[
-  "cosmic_weather",
-  "chart",
-  "positions",
-  "moon",
-  "moment_quality",
-  "retrograde",
-  "voc",
-  "planetary_hours",
-  "sunrise",
-  "ritual",
-  "tarot",
-  "check_in",
-  "natal_reading",
-  "iching",
-  "mayan",
-  "numerology",
-  "composite",
-  "davison",
-  "relocation",
-  "relocation_score",
-  "travel",
-  "transits",
-  "synastry",
-  "timing",
-  "progressions",
-  "electional",
-  "horary",
-  "returns",
-  "timeline",
-  "synthesis",
-  "perfections",
-  "midpoints",
-  "harmonic",
-  "antiscia",
-  "declination",
-  "sidereal",
-  "heliacal",
-  "review",
-  "bazi",
-  "year_ahead",
-  "correlate"
-]New value: +[
+  "cosmic_weather",
+  "chart",
+  "positions",
+  "moon",
+  "moment_quality",
+  "retrograde",
+  "voc",
+  "planetary_hours",
+  "sunrise",
+  "ritual",
+  "tarot",
+  "check_in",
+  "natal_reading",
+  "iching",
+  "mayan",
+  "numerology",
+  "true_sky",
+  "composite",
+  "davison",
+  "relocation",
+  "relocation_score",
+  "travel",
+  "transits",
+  "synastry",
+  "timing",
+  "progressions",
+  "electional",
+  "horary",
+  "returns",
+  "timeline",
+  "synthesis",
+  "perfections",
+  "midpoints",
+  "harmonic",
+  "antiscia",
+  "declination",
+  "sidereal",
+  "heliacal",
+  "review",
+  "bazi",
+  "year_ahead",
+  "correlate",
+  "common_threads"
+]
  3. 1 tool update
    • Changedcelestium1 field changed
      • changedInput schema / properties / data / description
        Previous value: -"Birth data + params. birth: {name, birth_date (YYYY-MM-DD), birth_time (HH:MM), birth_timezone (IANA), latitude, longitude, birth_location}. partner: same birth shape (synastry/composite/davison; also adds relationship activations to cosmic_weather/check_in). For place-based actions (relocation, relocation_score, planetary_hours, sunrise, heliacal, electional), top-level latitude/longitude = the TARGET location. Plus optional date, start, end, return_type (solar|lunar), city, planet, number (harmonic), orb (antiscia), system (sidereal: lahiri|raman|kp), activity (electional: marriage|business|travel|surgery|legal_matter|creative_work|investment|medical_treatment), ritual: type + max_minutes; tarot: count (1-3) + question; iching: question; check_in: mood, focus, intent, local_hour; review: period (week|month) or start+end; horary: question + house (1-12) + latitude/longitude; bazi: gender (male|female). render: true (natal_reading only) → also returns a viewable_url: a shareable, unlisted, revocable web page of the chart+reading; pass render:{ttl_days:N} to auto-expire it. Nothing is stored unless you opt in with render; without it, calls are pure compute."New value: +"Birth data + params. birth: {name, birth_date (YYYY-MM-DD), birth_time (HH:MM), birth_timezone (IANA), latitude, longitude, birth_location}. partner: same birth shape (synastry/composite/davison; also adds relationship activations to cosmic_weather/check_in). For place-based actions (relocation, relocation_score, planetary_hours, sunrise, heliacal, electional), top-level latitude/longitude = the TARGET location. Plus optional date, start, end, return_type (solar|lunar), city, planet, number (harmonic), orb (antiscia), system (sidereal: lahiri|raman|kp), activity (electional: marriage|business|travel|surgery|legal_matter|creative_work|investment|medical_treatment), ritual: type + max_minutes; tarot: count (1-3) + question; iching: question; check_in: mood, focus, intent, local_hour; review: period (week|month) or start+end; horary: question + house (1-12) + latitude/longitude; bazi: gender (male|female). render: true (natal_reading only) → also returns a viewable_url: a shareable, unlisted, auto-expiring, revocable web page of the chart+reading; render:{ttl_days:N} sets the expiry (default 90d), render:{burn:true} makes it view-once, render:{e2ee:true} encrypts it at rest (key only in the link #fragment; we store ciphertext and cannot read it). Nothing is stored unless you opt in with render; without it, calls are pure compute."
  4. 1 tool update
    • First observedcelestium

Related MCP Connectors

Related MCP Servers

  • astro-mcp

    DrewCyber
    A
    license
    Not graded
    quality
    B
    maintenance
    High-precision astrology tools for LLM agents, including natal charts, transits, progressions, synastry, and more, backed by Swiss Ephemeris.
    1
    MIT

  • Astro MCP Server

    aryaminus
    F
    license
    Not graded
    quality
    C
    maintenance
    Multi-tradition astrology engine that computes real birth charts, transits, and synastry for AI agents via MCP tools.
    8
    -
  • Asterwise by asterwise

    Asterwiseofficial

    asterwise
    A
    license
    A
    quality
    A
    maintenance
    Vedic and Western astrology for AI agents: 103 read-only tools for natal charts, dasha, kundali matching with Rajju and Vedha vetoes, panchanga, numerology and tarot, backed by Swiss Ephemeris and verified against NASA JPL Horizons.
    8
    103
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources