U Ministry Utility
75“README: 'Private, invite-only prayer-request app for church communities' with prayer-specific workflows — 'Prayer feed with three filters…”
source unavailable
CriticalPathTech/prayer
A quiet, invite-only prayer wall for a single church. Public source, free to self-host, or hosted at prays.online.
Trust Score
45.0
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
75“README: 'Private, invite-only prayer-request app for church communities' with prayer-specific workflows — 'Prayer feed with three filters…”
source unavailable
M Maturity
75“api.releases: 'latest tag v1.7.0 published 2026-08-05'; latest_commit: 'chore: bump 1.8.0 → 1.8.1 (#155)' dated 2026-08-05, within months…”
source unavailable
CriticalPathTech/prayer looks like a candidate for prayer & discipleship; License ladder: README states Elastic License 2.0; api.repos reports NOASSERTION (GitHub does not classify ELv2) — scored from README's explicit statement, not the NOASSERTION; do not fire license-ambiguous since the license is clearly named.
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 CriticalPathTech/prayer: 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 CriticalPathTech/prayer (https://refinry.dev) and help me assess it for using CriticalPathTech/prayer for prayer & discipleship 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 25 · security 75
“License: README: 'Source-available under the Elastic License 2.0 (see [LICENSE](LICENSE))' — restrictive for redistribution/SaaS ambitions…”
source unavailable
A Ease of Adoption
75dev 75 · volunteer 75
“README: 'Quickstart (Docker, ~2 min)' — 'docker compose up -d --build', 'pnpm bootstrap --slug hope' seeds '5 users + 10 sample posts'…”
source unavailable
C Community Trust
25“api.repos: 'stargazers_count': 1, 'forks_count': 1; contributors are essentially one human ('YiyangLi' 96 vs 'QwertyLucas' 2) plus…”
source unavailable
I AI-Agent Integrability
50“README is accurate with install/use sections ('Quickstart (Docker, ~2 min)', service table), license identifiable ('Elastic License 2.0')…”
source unavailable