Celestium: Cosmic Compass
Real astrology for AI agents: cosmic weather, synastry, timing, astrocartography, and divination.
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"celestium-cosmic-compass": {
"url": "https://celestium-cosmic-compass.fly.dev/mcp"
}
}
}Puntos de conexión remotos
https://celestium-cosmic-compass.fly.dev/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (1)
🟢celestium(action, data, identity)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"action": {
"type": "string",
"enum": [
"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"
],
"description": "The astrology/divination action to run."
},
"data": {
"type": "object",
"description": "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."
},
"identity": {
"type": "string",
"description": "Caller email/identity (resolves entitlement tier; optional in free tier)."
}
},
"required": [
"action"
]
}Comunidad
Evidencia