U Ministry Utility
75“README: 'Church Cap is an open-source, local-first live caption app for churches. Visitors scan a QR code, open a local web page on the…”
source unavailable
Church-Cap/Live-Church-Captions
Open-source real-time captions for churches, powered by Whisper and local-first by design.
Trust Score
48.8
Last full review 2026-10-06 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
75“README: 'Church Cap is an open-source, local-first live caption app for churches. Visitors scan a QR code, open a local web page on the…”
source unavailable
M Maturity
25“api.releases: 'latest tag v0.8.0 published 2026-08-25T21:34:43Z'; latest_commit 2026-08-25. But api.contributors shows a single…”
source unavailable
Church-Cap/Live-Church-Captions looks like a candidate for media & streaming; Bus-factor risk: all 19 contributions from one account (api.contributors).
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 Church-Cap/Live-Church-Captions: 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 Church-Cap/Live-Church-Captions (https://refinry.dev) and help me assess it for using Church-Cap/Live-Church-Captions for media & streaming 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
“api.repos: 'license.spdx_id: MIT' (permissive); security: {'osv_vulns': [], 'security_md': {'present': false}} — clean OSV but no security…”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 75
“README: 'download the notarized DMG, drag Church Cap to Applications' / 'download and run the setup executable' — GUI installer path; 'For…”
source unavailable
C Community Trust
25“api.repos: 'stargazers_count': 10, 'forks_count': 0; api.contributors shows only author 'Church-Cap'. Single-witness project, honest but no…”
source unavailable
I AI-Agent Integrability
50“README: structured 'Project Layout' section ('app/ — shared Church Cap web application...', 'docs/ — user guides, architecture...') and…”
source unavailable