mcpbeat

Listen to Sadhu MCP Server

app.listentosadhu/corpus
answering

Listen to Sadhu is answering right now. Last checked 2 min ago. It exposes 21 tools.

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

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
21
Tools
read from the server
189 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add corpus --transport http https://mcp.listentosadhu.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "corpus": {
      "url": "https://mcp.listentosadhu.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.corpus]
url = "https://mcp.listentosadhu.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "corpus": {
      "url": "https://mcp.listentosadhu.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "corpus": {
      "url": "https://mcp.listentosadhu.app/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verse
verse_get
Fetch a verse's raw fields for your own reasoning (NOT for display — to show a verse to the user, use verse_render). Returns original script + transliteration as line arrays; with lang, also the canonical translation inline plus an `alternatives` manifest of other translation kinds in that language (fetch their text with verse_translation, word-by-word with verse_synonyms). Address by ref ("BG 2.13"), source+tokens, or verse id.
verse_list
List the verses of a book / chapter. Skips .0 chapter summaries; collapses merged verses into one item with a covers span.
verse_render
Show a verse to the user. THE DEFAULT way to display/read a scripture verse: renders an inline card with the original script (centered), transliteration in the requested language, the word-by-word, and the translation — all at once. Use this whenever the user asks to see, read, open, or quote a specific verse ("покажи БГ 2.13", "read Bhagavad-gita 2.13"). The other verse_* tools are for fetching raw data; for DISPLAY prefer this one. Address by ref ("BG 2.13"), source+tokens, or id; lang sets the script + translation language.
verse_synonyms
Fetch the word-by-word ("Synonyms") as a raw {word, meaning} array for one verse translation (data — verse_render already shows the word-by-word inside the card). Defaults to the canonical rendering; pass `kind` for an alternative.
verse_translation
Fetch the text of ONE translation of a verse (data, not a card — to display a verse use verse_render). Defaults to the canonical (kind=canonical); pass a `kind` from verse_get's `alternatives` manifest to fetch a specific rendering.
source
source_get
Get one book by id or code ("source_…" or "BG"/"БГ").
source_list
List all books (Caitanya-caritāmṛta is three sources).
source_resolve
Find a book by name (fuzzy): "gita", "бхагаватам", "CC Madhya".
author
author_list
List all authors.
author_resolve
Find a author by name (fuzzy).
document
document_get
Get a document (commentary/prose_chapter/letter) by id.
document_list
List documents at a reference / in a book. A verse's purport = document_list(source, tokens, kind:"commentary").
excerpt
excerpt_prepare
Generate (or fetch, if cached) the audio clip for a lecture passage and return its playable URL. This is the excerpt player's Play action — it is called for you by the player UI on demand. Agents should use excerpt_render to show the player, not call this directly. Idempotent: same track+window returns the same cached clip.
excerpt_render
Let the user HEAR a lecture passage inline. Call this when the user wants to LISTEN to a specific moment in a track — e.g. from a search(types:["track"]) hit, pass its track_id plus start_ms/end_ms. Renders an inline audio player that generates the clip on demand (public share-audio, max 10 minutes).
location
location_list
List all locations.
location_resolve
Find a location by name (fuzzy).
track
track_get
Get a track (lecture/conversation): metadata, cited references, transcript/pdf availability.
track_list
List tracks, filterable by reference (source[+tokens] = tracks citing it), author/location/kind/date/lang. No filter ⇒ recent tracks (date desc).
media
media_render
Show/play an existing corpus VIDEO clip inline. Call this when the user wants to WATCH a clip found via search(types:["media"]) — pass the hit's media_id. Renders an inline video player.
search
search
Semantic + lexical search over the corpus. Returns verses, documents, track passages and titles matching a natural-language query, each with the id needed to fetch the full record (verse_id→verse_get, document_id→document_get, track_id+start_ms/end_ms→transcript_window; media_id→media_render to play the clip). Every filter is optional. Use min_score to drop weak matches.
transcript
transcript_window
Read a track's transcript around a time window (from a search track hit or track_list). Widen with pad_ms.

Endpoints

URLTransportStateLatencyChecked
https://mcp.listentosadhu.app/mcp streamable-http answering 190 ms 2 min ago

Listen to Sadhu — questions

Answers built from our own checks of this server.

What can Listen to Sadhu do?
It exposes 21 tools, read directly from the server on our last check. Among them: author_list, author_resolve, document_get, document_list, excerpt_prepare, excerpt_render and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Listen to Sadhu mostly used for?
Its tools cluster around verse, source and excerpt. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Listen to Sadhu working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 189 ms. The bar chart above shows every period we have measured.
How do I connect Listen to Sadhu?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Listen to Sadhu need an API key?
No. Listen to Sadhu completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Listen to Sadhu?
It answers our handshake in 189 ms on average, which is faster than 65% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.