U Ministry Utility
75“README: 'provides the same features as the web version including online giving, self-check-in for attendance, live streaming of services…”
source unavailable
ChurchApps/B1Mobile
ReactNative mobile application for B1.church
Trust Score
47.5
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: 'provides the same features as the web version including online giving, self-check-in for attendance, live streaming of services…”
source unavailable
M Maturity
25“api.repos pushed_at 2026-08-17 (within 12 months), latest_commit 2026-08-17 'Fix lint/tests after JWT/WebView wave'; api.releases: 'no…”
source unavailable
ChurchApps/B1Mobile looks like a candidate for communication; M capped at 25 by anchor: no tagged release ever despite active commits.
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 ChurchApps/B1Mobile: 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 ChurchApps/B1Mobile (https://refinry.dev) and help me assess it for using ChurchApps/B1Mobile for communication 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, but no dep-license scan in pack). Security: security.osv_vulns [] (no known unfixed vulns)…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“README: 'Copy dotenv.sample.txt to .env' and 'Run `npm i` to install dependencies' plus link to 'development guide' at churchapps.org/dev —…”
source unavailable
C Community Trust
50“api.contributors top: jzongker 281, Payalpie 29, pranavmalvawala 20 — multiple external contributors; README: 'We have a great community…”
source unavailable
I AI-Agent Integrability
50“README is accurate with install/build/use sections; license machine-readable via api.repos license.spdx_id 'MIT'; described API/backend…”
source unavailable