U Ministry Utility
50“README: 'Unofficial API and website serving liturgical data for The Episcopal Church.' (fetch date 2026-09-28)”
source unavailable
gbj/commonprayer
Unofficial API and website serving liturgical data for The Episcopal Church.
Trust Score
27.5
Last full review 2026-10-06 · Trust Score decays −2 points per month without a fresh review (never below 20)
security cap applied — score capped at 45U Ministry Utility
50“README: 'Unofficial API and website serving liturgical data for The Episcopal Church.' (fetch date 2026-09-28)”
source unavailable
M Maturity
25“api.repos: 'pushed_at': '2025-05-09T14:24:11Z'; api.releases: 'no tagged release found'; api.contributors: top contributor 'gbj' with 730…”
source unavailable
gbj/commonprayer looks like a candidate for media & streaming; No tagged release found; single dominant contributor (gbj, 730 commits) indicates 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 gbj/commonprayer: 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 gbj/commonprayer (https://refinry.dev) and help me assess it for using gbj/commonprayer 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
25license 75 · security 25
“api.repos: 'license.spdx_id': 'MIT'; security: 'security_md': {'present': false}; 'osv_vulns': [] (fetch date 2026-09-28)”
source unavailable
A Ease of Adoption
0dev 25 · volunteer 0
“README: 'Unofficial API and website serving liturgical data for The Episcopal Church.' (no install/run docs, no Dockerfile, no quickstart)…”
source unavailable
C Community Trust
25“api.contributors: 'toddfoster' 2 contributions, 'ksenzee' 1 contribution; api.repos: 'stargazers_count': 7, 'forks_count': 2 (fetch date…”
source unavailable
I AI-Agent Integrability
25“README: 'Unofficial API and website serving liturgical data for The Episcopal Church.' (sparse README, no API description, no…”
source unavailable