Ext Ops Panel
Open dashboard
Comparison

Jewish Texts Reference vs Kabbalah MCP Server by RoxyAPI

Jewish Texts Reference is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Kabbalah MCP Server by RoxyAPI is an MCP server published by roxyapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceJewish Texts ReferenceKabbalah MCP Server by RoxyAPI
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
No figure published
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

Jewish Texts Reference vs Kabbalah MCP Server by RoxyAPI
FactJewish Texts ReferenceKabbalah MCP Server by RoxyAPI
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.sefaria.org/sse)Remote server (roxyapi.com/mcp/kabbalah)
Transport (differs)SSEStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/danielrosehill/jewish-texts-reference-pluginNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)not checked yetResponded 3 days ago

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

Jewish Texts Reference

In its own words, on Community GitHub marketplaces:

Look up Jewish texts and references via the Sefaria MCP server — Tanakh, Talmud, Mishnah, Halakha, Kabbalah, commentary, dictionaries, and topics. Includes nikkud add/strip skills (Dicta nakdan + removenikud APIs, offline regex, unikud fallback).

Kabbalah MCP Server by RoxyAPI

In its own words, on Official MCP Registry:

Gematria with typed transliteration, the 72 names, Tree of Life and Hebrew birthday for AI agents.

How to run each

Jewish Texts Reference As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install jewish-texts-reference@danielrosehill

Kabbalah MCP Server by RoxyAPI As a remote MCP server

Claude Code
claude mcp add --transport http kabbalah https://roxyapi.com/mcp/kabbalah --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

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

Only Kabbalah MCP Server by RoxyAPI 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: Jewish Texts Reference · What it can do: Kabbalah MCP Server by RoxyAPI · 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.

Where the data comes from: how the catalog is built