Home / MCP registry index / com.macaroonnetwork/bible-evidence
Macaroon Bible Evidence
com.macaroonnetwork/bible-evidence in the official MCP registry.
Endpoint https://api.macaroonnetwork.com/mcp-faith-evidence-v1/mcp/. Source: github.com/kevmoz/macaroon-bible-evidence-mcp.
The registry describes it as: Read-only BSB and WEB Scripture evidence with provenance, context, comparison, and search.
We read its 11 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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
faith_scripture_lookup faith_passage_context_preview faith_passage_compare_preview faith_cross_references_preview faith_scripture_search_preview faith_topic_guide_preview faith_services_list faith_services_search faith_service_detail faith_service_evidence faith_service_page
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-macaroonnetwork-bible-evidence)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.