Ext Ops Panel
Open dashboard
Comparison

mirror vs FateMCP DayMaster

mirror is a plugin bundle for AI coding tools published by AvyanshKatiyar. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). FateMCP DayMaster is an MCP server published by optimizer668. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacemirrorFateMCP DayMaster
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

mirror vs FateMCP DayMaster
FactmirrorFateMCP DayMaster
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.fatemcp.com/daymaster)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/avyanshkatiyar/mirrorgithub.com/fatemcp/daymaster
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-12

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

mirror

In its own words, on Claude Code: claude-plugins-community:

Mirror turns Claude into a psychological astrologer. Instead of listing transits and placements like a textbook, it conducts a multi-phase interactive reading — gathering birth data, calculating natal charts and transits via parallel agents, synthesizing everything into one narrative, delivering a concise portrait, then shifting into real conversation using the OARS therapeutic framework. It handles sect-aware interpretation, dispositor trees, three-layer Chiron analysis, shadow material, and honest temporal framing with real dates. The skill is designed to make people feel genuinely seen, not generically described.

FateMCP DayMaster

In its own words, on Official MCP Registry:

Day Pillar reading from your birth date — BaZi astrology.

How to run each

mirror As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mirror@claude-community

FateMCP DayMaster As a remote MCP server

Claude Code
claude mcp add --transport http daymaster https://mcp.fatemcp.com/daymaster

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only FateMCP DayMaster 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: mirror · What it can do: FateMCP DayMaster · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built