Vedaword MCP server

• Registry namecom.vedaword/libraryverified in the MCP registry

The registry name sits under vedaword.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools8
• Server calls itselfvedaword
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 520 ms.

• Its tools do every use case we checked: study Sanskrit verses through word-by-word breakdowns; read Bhagavad Gita chapters with transliteration and commentary; follow devotional texts verse by verse with notes.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score100 of 100answers 100 · does the job 100 · definitions 100 · context 99 · connects 100
• What an agent can do with it3 of 3 use cases
• Answered100% of days8 of 8 daily checks
• Median first answer550 ms
• Space in an agent's context≈ 3,131 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…