Home / MCP registry index / io.github.balthasarspeyr/catalogue
Balthasar & Speyr Catalogue
io.github.balthasarspeyr/catalogue in the official MCP registry.
Endpoint https://mcp.balthasarspeyr.org/mcp.
The registry describes it as: Public catalogue, semantic search and source texts of Hans Urs von Balthasar and Adrienne von Speyr.
We read its 22 tools on 2026-10-27. 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
export_bibliography get_bibliography_source list_works get_work list_publications get_publications get_publication_text search_publication_text get_download_links get_catalog_options get_corpus_coverage search_works get_common_life_and_mission get_person_life_and_mission get_community_of_saint_john get_vocation_discernment_contact search_life_mission_and_community count_catalog aggregate_catalog list_journals get_topics_by_period get_topic_evidence
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-balthasarspeyr-catalogue)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.