mcpbeat Sign in

Vedaword MCP Server

answering

Vedaword is answering right now. Last checked 10 min ago. It exposes 8 tools.

Sanskrit scripture search: Mahabharata, Upanishads, Gita; cited verses, honest no-answer.

Uptime history 11 days of history · worst day 46%
11 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
221 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 October 2026. No other catalogue keeps this.

16 Oct 3 tool descriptions were rewritten5 times that day find_similar_verses, get_verse, search_texts
16 Oct a tool appeared browse_work
and 2 more, back to 16 October 2026

Vedaword does not always answer

Over the last week it answered 98.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add library --transport http https://mcp.vedaword.com
Settings → Connectors → Add custom connector, then paste this address
https://mcp.vedaword.com
~/.codex/config.toml
[mcp_servers.library]
url = "https://mcp.vedaword.com"
.cursor/mcp.json
{
  "mcpServers": {
    "library": {
      "url": "https://mcp.vedaword.com"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "library": {
      "type": "http",
      "url": "https://mcp.vedaword.com"
    }
  }
}

Available tools 8

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

authors
list_authors
List the authors the tradition names, grouped by period, each with a short note and the books credited to them. Call it when the user asks who wrote something, or wants the works of one acharya; pass the author's `id` to list_works to see the books. Filter by `era`: shruti, classical, caitanya, successors, modern.
browse
browse_work
Walk a work's structure in order: a work gives its sections, a section its chapters, a chapter its verses (label and translation, in pages). Use it when the user wants to read a chapter or a book through, asks what comes after a verse, or what a book contains; search_texts cannot do that. Three steps, each named in the reply of the one before: `work` alone lists the sections; add `section` for its chapters; add `chapter` (the `index` from the listing) for its verses. Every reply carries `next`, the arguments of the call that continues. To quote a verse, call get_verse with its `unit_id`: it returns the citation and version hash.
lookup
lookup_sanskrit_term
Look up a Sanskrit word: its spellings across scripts, the meanings it carries in this corpus, how many verses gloss it, and examples of where it occurs. Built from the word-by-word breakdowns of some 30 000 verses, so these are the meanings translators actually assigned to the word in these texts — not a lexicon's list of everything it could mean. Use it before translating a term yourself, and whenever the user asks what a word means.
similar
find_similar_verses
Given a verse, find other passages in the library that say something close to it — by meaning, not by shared words. Start here when you already have a verse; when you only have words, a question or a term, use search_texts. Use it to check whether a teaching appears elsewhere before presenting it as the tradition's position, to gather parallel places, or to see how different works treat one subject. Set `exclude_same_work` when you want an independent witness: the next verse of the same chapter is nearly always similar and proves nothing. An empty result is a real answer — it means the library says this in one place only.
texts
search_texts
Search the Vedaword library of Sanskrit scripture by meaning as well as by wording, so a paraphrased question works and a Sanskrit term reaches passages written in another script. This is the first thing to call for any factual question about what the scriptures say. Start here when you have words: a question, a phrase, a term. When you already have a verse and want its parallels, use find_similar_verses instead; to read a known verse whole, use get_verse; to read a chapter or a book in order, use browse_work. Returns passages with an exact citation, a URL and the version hash of the text quoted. Read `confidence` before using the results. "none" means the library has no answer and the result list is empty — report that to the user instead of reaching for something related. "low" means the passages are leads, not answers. `matched_by` says how each was found: a passage found only by "vector" shares no words with the query.
vaishnava
get_vaishnava_calendar
Ekadashi fasts, festivals and the appearance and disappearance days of the acharyas in the Gaudiya Vaishnava calendar, computed for one place. Call it for any question about when an Ekadashi or a festival falls, or when to break a fast. The place is required and matters: the fast day is decided by the tithi at local sunrise, and the time to break the fast is minutes wide and different in every city. Ask the user where they are rather than guessing. Every observance links to a page with its story and the verses behind it.
verse
get_verse
Fetch one verse whole: the Sanskrit in Devanāgarī and IAST, the word-by-word breakdown with the meaning each word carries in this passage, the literary translation, the commentary, and optionally the surrounding verses. Call it after search_texts when you are going to quote, and whenever the user names a verse. The word-by-word table is what lets you explain or re-translate a line honestly instead of trusting a finished translation. Accepts citations as people write them, not only internal ids. To read a chapter or a whole book in order, use browse_work. To read on around one verse, call this again with `context` 5 and then with the `unit_id` of the last neighbour marked "after"; each reply carries the five verses on either side with their translations.
works
list_works
List the works with their sizes, shelf, author and available languages. Call it at the start of a conversation about scripture, or when you need work slugs for filtering. The list is short by default: no descriptions. Narrow it with `category` (a shelf: itihasa, purana, upanishad, vedanta, samhita, shastra, kavya, shruti, smriti; `shruti` is the upanishad shelf, `smriti` the itihasa and purana shelves) or with `author` (an id from list_authors). Set `include_descriptions` for a paragraph on each work. It also tells you what is not translated: several works exist only in Russian. Check `languages` before promising the user an English text.

Endpoints

URLTransportStateLatencyChecked
https://mcp.vedaword.com streamable-http answering 204 ms 10 min ago

Alternatives to Vedaword

same job, measured the same way
Gita & Mahabharata
by theindianappguy

Full Bhagavad Gita (Sanskrit + English) and Ganguli's Mahabharata: search verses and passages.

6 tools answering
Bhagavad Gita
by pipeworx-io

Bhagavad Gita MCP — Hindu scripture / Vedic text. Sanskrit verses (slokas) with English…

44 tools answering
Listen to Sadhu
by listentosadhu

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

21 tools answering
Bible Copilot
by mybiblecopilot

Scripture-cited answers to any Bible question, plus verse text and study pages, for AI agents.

5 tools answering
Gita Scroller
by goodturnstudio

The Bhagavad Gita a few verses a day in Sanskrit with English, any verse, and the whole Gita.

9 tools answering
NoteCube
by notecube

Your NoteCube meeting and lecture recordings: search, read transcripts, and write cited documents.

answering
SerpKite
by serpkite

Google search, news, maps, scholar, webpages, cited AI answers and deep research for AI agents.

answering
MCP Knowledge RAG
by infoinlet-marketplace

Permission-aware RAG for agents — ingest docs, hybrid search, cited answers (hosted API).

18 installs/wk local only

Vedaword — questions

Answers built from our own checks of this server.

What can Vedaword do?
It exposes 8 tools, read directly from the server on our last check. Among them: browse_work, find_similar_verses, get_vaishnava_calendar, get_verse, list_authors, list_works and 2 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 →
Is Vedaword working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 221 ms. The bar chart above shows every period we have measured.
How do I connect Vedaword?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Vedaword need an API key?
No. Vedaword completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Vedaword?
It answers our handshake in 221 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.