U Ministry Utility
75“README: 'Syntax trees, morphology, and linguistic annotations for the Hebrew Bible' with 'Word sense data' from UBS MARBLE, 'Semantic…”
source unavailable
Clear-Bible/macula-hebrew
Syntax trees, morphology, and linguistic annotations for the Hebrew Bible
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: 'Syntax trees, morphology, and linguistic annotations for the Hebrew Bible' with 'Word sense data' from UBS MARBLE, 'Semantic…”
source unavailable
M Maturity
50“api.releases: 'latest tag 26.04.13 published 2026-04-13'; latest_commit 2026-04-24; three contributors (ryderwishart 171, jacobwegner 108…”
source unavailable
Clear-Bible/macula-hebrew looks like a candidate for data & text corpora; License is NOASSERTION with multi-source copyright layering (public-domain WLC, CC BY 4.0 parts, Cherith Analytics copyright) — S fail-closed to 0 pending classification of LICENSE.md; this is the dominant adoption blocker and also fires license-ambiguous.
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 Clear-Bible/macula-hebrew: 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 Clear-Bible/macula-hebrew (https://refinry.dev) and help me assess it for using Clear-Bible/macula-hebrew for data & text corpora 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
0license 0 · security 50
“api.repos.license.spdx_id: 'NOASSERTION'; README cites mixed terms per source ('public domain by the Groves Center', 'CC BY 4.0'…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“README documents three data formats ('WLC/nodes ... WLC/lowfat ... WLC/tsv') and licensing pointers — a developer can consume this directly…”
source unavailable
C Community Trust
50“api.repos: 68 stars, 18 forks; three distinct long-term contributors; README credits multiple external institutions ('Clear Bible, Inc…”
source unavailable
I AI-Agent Integrability
75“README: data offered in nested 'Node' elements 'suitable for many NLP systems', 'lowfat' for 'query systems', and TSV 'simpler for many…”
source unavailable