U Ministry Utility
50“"Eloquent is a free & open-source application for research and study of God and His Word" and "compatible with an uncountable number of…”
source unavailable
mdbergmann/Eloquent
Eloquent is a bible study tool for macOS
Trust Score
39.2
Last full review 2026-09-27 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
50“"Eloquent is a free & open-source application for research and study of God and His Word" and "compatible with an uncountable number of…”
source unavailable
M Maturity
50“latest tag 2.6.8 published 2025-12-28 — api.releases; pushed_at 2026-04-10 — api.repos; README accurate to current state. Meets baseline…”
source unavailable
45.0 → 41.2 (-3.8 over window)
ranked #9 of 14 in M4
mdbergmann/Eloquent looks like a candidate for bible study & scripture tools; Single dominant contributor (110 of 111 contributions) — bus-factor risk.
Use it with
Selected: Gloo AI Studio
Tool names and logos belong to their owners; shown so you can pick your own client. Not affiliated.
Step 1 — Connect Refinry once (prompt only)
Gloo AI Studio does not document external MCP server setup. Use this prompt with the copied Refinry research brief in Studio.
https://studio.ai.gloo.com/I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s plain-language agent feed — https://refinry.dev/docs.md — then help me evaluate mdbergmann/Eloquent: summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Some clients need manual setup. Follow the plain-language steps on the Docs page.
Step 2 — Plan your first step
Tell the AI what you want to do; edit this to match your situation.
I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s public review of mdbergmann/Eloquent (https://refinry.dev) and help me assess it for using mdbergmann/Eloquent for bible study & scripture tools in my ministry. Summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites, separating reviewed evidence from what still needs verification. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Prefer a hand-off that works without a connection? Copy the research brief: every reviewed fact, all caution flags, and a feasibility-only first assignment.
S Security / License
50license 75 · security 50
“license.spdx_id: BSD-3-Clause — api.repos (permissive, but no evidence of dependency license scan => 75). osv_vulns: [] — security, but…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“"Releases can be downloaded under this link: " — README. No build instructions, no Dockerfile, no config docs, no troubleshooting. A macOS…”
source
C Community Trust
25“stargazers_count: 126, forks_count: 22 — api.repos, but contributors show only 2 (mdbergmann 110, erickhchan 1 — api.contributors). No…”
source unavailable
I AI-Agent Integrability
25“README is sparse: description, download link, screenshots only — no API description, no build docs, no CLI surface. License identifiable…”
source unavailable