Skip to content
External endpointresponds

corpus

Read-only semantic search over Vedic scripture verses, commentaries, and recorded lectures.

Endpoint URL
https://mcp.listentosadhu.app/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:04 AM UTC
Check
MCP initialize · 8s limit
Latency
488 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
app.listentosadhu/corpus

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
lectorium-corpus-mcp
Version
164e873d29
Capability keys
resources, tools
Tool names
author_list, author_resolve, document_get, document_list, excerpt_prepare, excerpt_render, location_list, location_resolve, media_render, search, source_get, source_list, source_resolve, track_get, track_list, transcript_window, verse_get, verse_list, verse_render, verse_synonyms, verse_translation
Instructions excerpt

Listen to Sadhu — public, read-only access to the Lectorium corpus of Vedic scripture and recorded lectures. Scripture: verses (original Devanagari/Bengali + IAST transliteration + translations) and documents (commentaries/purports, prose chapters, letters). Lectures: transcribed talks and conversations with metadata and references. Addressing: a reference is a book code plus a position, e.g. "BG 2.13", "SB 5.5.3", "CC Madhya 8.128" (Cyrillic codes like "ШБ 5.5.3" also work). Tools that take a reference accept either the "ref" string or a resolved source id + tokens. In the tokens filter (search / track_list / verse_list), a BARE CHAPTER number covers the whole chapter — use "7" for all of chapter 7, "7.1" only for that one verse. How to use the tools: - search: semantic + lexical search over verses, documents, tracks and titles. - source_get/list/resolve, author_list/resolve, location_list/resolve: turn a name into an id used by the filters. - verse_get/list, document_get/lis

Reported Aug 17, 2026, 05:04 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 443ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 592ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 667ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 488ms