Home / MCP registry index / com.trulyrandomverse/bible-study
TrulyRandomVerse
com.trulyrandomverse/bible-study in the official MCP registry.
Endpoint https://mcp.trulyrandomverse.com/.
The registry describes it as: Bible study: many editions, Strong's Hebrew and Greek, cross-references, Matthew Henry, the Fathers
We read its 16 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_commentary_section get_verse_text get_strongs_for_verse get_strongs_detail get_word_origin get_strongs_occurrences get_person get_book_overview get_cross_references search_topic_verses get_matthew_henry get_church_fathers search_fathers keyword_search compare_versions get_site_help
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-trulyrandomverse-bible-study)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.