astrology vs Tarot Draw
astrology is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
astrology is a plugin bundle for AI coding tools published by aryaminus. No marketplace we read lists it any more. Tarot Draw is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Tarot Draw | |
|---|---|---|
| Community marketplace aryaminus/astro | Removed on 2026-10-27 Version: 2.5.0 Forks (GitHub): 4 Stars (GitHub): 12 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.4 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | astrologyno longer listed · | Tarot Draw |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 12 | 0 |
| Forks (GitHub) (differs) | 4 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (gateway.pipeworx.io/tarot-draw/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aryaminus/astro | github.com/pipeworx-io/mcp-tarot-draw |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of astrology
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Divine API - Western Astrology
Official Divine API MCP for Western Astrology: Natal, Synastry, Transit, Composite, Progressions.
-
Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot.
-
Swiss Ephemeris astrology: natal charts, transits, synastry, solar returns and astrocartography.
-
AI Agent Astrology — natal charts, transits, cosmic weather, and forecasts for AI agents.
-
AstroWay Astrology API (full catalogue)
Every AstroWay endpoint as a tool: Western, Vedic, Chinese, Human Design, tarot, reports.
-
Astro Agents - deterministic Western + Vedic astrology
Natal, transits, kundli, KP, yogas, dashas, panchang, Gun Milan. JPL DE440, no LLM, hashed.
What each says it does
astrology
Trustworthy multi-tradition astrology. 19 modes, 3 traditions, zero deps. Computes mathematically real charts from birth data via a deterministic ephemeris engine.
Tarot Draw
tarot-draw MCP — wraps StupidAPIs (keyless — no credential needed)
How to run each
astrology
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Tarot Draw As a remote MCP server
claude mcp add --transport http tarot-draw https://gateway.pipeworx.io/tarot-draw/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Tarot Draw has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: astrology · What it can do: Tarot Draw · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.