Home / MCP registry index / dev.urantia/urantia-papers
Urantia Papers
dev.urantia/urantia-papers in the official MCP registry.
Endpoint https://api.urantia.dev/mcp. Source: github.com/urantia-hub/urantia-dev-api.
The registry describes it as: The Urantia Papers in English and Spanish, with cross-references to the Bible and 21 texts. No key.
We read its 26 tools on 2026-10-28. 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
toc.get papers.list papers.get papers.sections paragraphs.random paragraphs.get paragraphs.context search.fulltext search.semantic entities.list entities.get entities.paragraphs audio.get bible.books bible.book bible.chapter bible.verse bible.verse.urantia_parallels bible.search.semantic works.list works.search works.search.semantic works.read works.urantia_parallels quotes.verify cite.get
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-urantia-urantia-papers)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.