Home / MCP registry index / io.github.heavyblotto/caelus-mcp

io.github.heavyblotto/caelus-mcp

io.github.heavyblotto/caelus-mcp in the official MCP registry. Endpoint https://www.ephemengine.com/api/mcp. Source: github.com/heavyblotto/caelus.

The registry describes it as: 34-tool Caelus MCP for validated astrology: charts, transits, Vedic, facts, sky view, synthetic.

We read its 35 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http caelus-mcp https://www.ephemengine.com/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "caelus-mcp": {
      "url": "https://www.ephemengine.com/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"caelus-mcp","type":"http","url":"https://www.ephemengine.com/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

natal_chart current_sky sky_view sky_view_sequence synthetic_validate synthetic_positions synthetic_sky_view transits synastry find_aspect_dates rectification_grid sky_events planetary_hours void_of_course returns progressions composite dignities lots profections firdaria releasing directions nakshatras dasha vargas yogas aspect_patterns parans chart_signature chart_facts counterfactual_chart similar_skies electional_search cosmic_weather

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-heavyblotto-caelus-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-heavyblotto-caelus-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.