Vedaword
Sanskrit scripture search: Mahabharata, Upanishads, Gita; cited verses, honest no-answer.
| Endpoint | https://mcp.vedaword.com (streamable-http) |
|---|---|
| Registry version | 1.0.1 |
| Now | 8 tools · grade A (96) · pin ts_507256eeb6601f90c7511c5fb7a6a873 · protocol 2025-06-18 |
| First / last listed | 2026-10-27 02:39 UTC / 2026-10-27 02:39 UTC |
| Grade over time | 2026-10-27: A (96), 8 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: search_texts get_verse lookup_sanskrit_term find_similar_verses get_vaishnava_calendar list_works list_authors browse_work
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_simila params: query*, language, works, parts, limit, full_text |
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 instea params: verse*, language, context |
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 w params: term*, language, examples |
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 subje params: verse*, language, limit, exclude_same_work |
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 ci params: latitude*, longitude*, timezone*, place_name, days, language |
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 sh params: language, category, author, include_descriptions |
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. params: language, era |
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 it params: work*, section, chapter, page, page_size, offset, limit, language |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.