Ext Ops Panel
Open dashboard
Comparison

patristic vs io.github.ldshaf/daily-scripture-mcp

patristic is a plugin bundle for AI coding tools published by logospatrum. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.ldshaf/daily-scripture-mcp is an MCP server published by ldshaf. 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
Marketplacepatristicio.github.ldshaf/daily-scripture-mcp
Claude Code: claude-plugins-community Listed
Version: 0.1.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

patristic vs io.github.ldshaf/daily-scripture-mcp
Factpatristicio.github.ldshaf/daily-scripture-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (logospatrum.com/api/mcp)Remote server (hxoqbbfgkrbzumjczeef.supabase.co/functions/v1/mcp-daily-scripture)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/logospatrum/patristic-plugingithub.com/ldshaf/daily-scripture-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checkResponded 3 days agoResponded 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

patristic

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

Search and cite the Russian Orthodox patristic corpus (azbyka.ru) from any MCP-capable agent. Indexes ~2,100 works by 86 Church Fathers and ascetic writers (726K paragraphs, 1.98M bge-m3 embedding windows) in a Postgres + pgvector backend. Ships: - HTTP MCP server with 6 tools: read_passage, lexical_search, semantic_search, list_authors, list_works, expand_concept (Church-Slavonic / archaic synonym expansion). - "teo-search" subagent — restricted to search tools, returns candidate citations with snippets so the main agent can't quote without verifying. - "theology-router" skill — auto-activates on patristic/theological questions and enforces the search-then-read pattern. All passages return verbatim with canonical slugs of the form author/work/chapter/paragraph, linked back to azbyka.ru. Self-hostable — swap the MCP URL to your own backend.

io.github.ldshaf/daily-scripture-mcp

In its own words, on Official MCP Registry:

Daily Bible verse and reflection for morning briefs. Conservative evangelical perspective. ESV.

How to run each

patristic As a Claude Code plugin

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

io.github.ldshaf/daily-scripture-mcp As a remote MCP server

Claude Code
claude mcp add --transport http daily-scripture-mcp https://hxoqbbfgkrbzumjczeef.supabase.co/functions/v1/mcp-daily-scripture

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

Both endpoints responded at the last daily 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: patristic · What it can do: io.github.ldshaf/daily-scripture-mcp · 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