U Ministry Utility
75“README: "Enable churches to read and study Scripture and OBS in their own language using all the opensource materials from git.door43.org"…”
source unavailable
hiscoder-com/obt
Open Bible Text
Trust Score
51.8
Last full review 2026-09-28 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
75“README: "Enable churches to read and study Scripture and OBS in their own language using all the opensource materials from git.door43.org"…”
source unavailable
M Maturity
50“api.releases: "latest tag v1.10.5 published 2022-12-03T06:02:22Z"; latest_commit: "2025-12-18T10:38:10Z"; api.contributors: "foxprogs 711…”
source unavailable
53.8 → 53.8 (+0.0 over window)
ranked #1 of 11 in M9
hiscoder-com/obt looks like a candidate for ministry data & theology resources; No security policy file present (security_md.present false).
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 hiscoder-com/obt: 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 hiscoder-com/obt (https://refinry.dev) and help me assess it for using hiscoder-com/obt for ministry data & theology resources 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"; security: "osv_vulns": [], "security_md": {"present": false} (fetch date 2026-09-28)”
source unavailable
A Ease of Adoption
50dev 50 · volunteer 25
“README: "Getting Started" and "Installation" sections present; no one-command or GUI install path mentioned in excerpt (fetch date…”
source unavailable
C Community Trust
25“api.contributors: "foxprogs 711, Valyukhov 559, Vorobushec 113" (fetch date 2026-09-28)”
source unavailable
I AI-Agent Integrability
50“README: "An application for advanced Bible study using opensource materials from git.door43.org" and "View Production" link; no…”
source unavailable