Skip to content
LiciumTalk to usFor agentsSign in

MCP server list / corpus

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

Answered:

4 of 4 checks

Status
responds
Typical response time
540 ms
Last checked
Latest check:
This server answered at its latest check.Last checked  · MCP initialize · 8s limit · HTTP 200 · answered in 488 ms.
Address
https://mcp.listentosadhu.app/mcp
Listed in:
official MCP registry mcp_registry
Registry name
app.listentosadhu/corpus
Transport
streamable HTTP streamable-http
Host
mcp.listentosadhu.app

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

What the server says about itself

We have not checked it.
Server name:
lectorium-corpus-mcp
Version:
164e873d29
MCP features it lists:
resources, tools
Tool names:
author_listauthor_resolvedocument_getdocument_listexcerpt_prepareexcerpt_renderlocation_listlocation_resolvemedia_rendersearchsource_getsource_list
and 9 moresource_resolvetrack_gettrack_listtranscript_windowverse_getverse_listverse_renderverse_synonymsverse_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 referen…

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

Check history

oldest to newest; each row is one recorded check
Recorded checks for corpus
CheckedStatusTookCheck
responds443 msMCP initialize · 8s limit · HTTP 200
responds592 msMCP initialize · 8s limit · HTTP 200
responds667 msMCP initialize · 8s limit · HTTP 200
responds488 msMCP initialize · 8s limit · HTTP 200

Need a different server, page or part?

Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.