protogrid

Search / com.vedaword/library

Vedaword

R0· no sign-in

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

v1.0.1 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality81new
Trust82of 100
Uptime, 30 days94%
Latency p50485 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "library": {
      "type": "http",
      "url": "https://mcp.vedaword.com"
    }
  }
}
claude mcp add --transport http library https://mcp.vedaword.com
[mcp_servers.library]
url = "https://mcp.vedaword.com"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "library": {
      "type": "remote",
      "url": "https://mcp.vedaword.com",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "library": {
      "type": "http",
      "url": "https://mcp.vedaword.com"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=library&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnZlZGF3b3JkLmNvbSJ9"
}
{
  "servers": {
    "library": {
      "type": "http",
      "url": "https://mcp.vedaword.com"
    }
  }
}
{
  "mcpServers": {
    "library": {
      "httpUrl": "https://mcp.vedaword.com"
    }
  }
}
extensions:
  "library":
    enabled: true
    name: "library"
    type: streamable_http
    uri: "https://mcp.vedaword.com"
    timeout: 300

Quality 81 / 100new

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene86 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations8 of 8 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: search_texts (destructiveHint, idempotentHint); lookup_sanskrit_term (destructiveHint, idempotentHint); find_similar_verses (destructiveHint, idempotentHint); …
  • pass
    tools.token_costabout 3,108 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool history recorded for 4 of the 7 days needed
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

8 tools, about 3,108 tokens to load them all · tool set 4530c11754f9 · tools last changed 2026-10-16 · checked 2026-10-19 10:20 UTC

Tool changes

  • browse_workadded

    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.

  • find_similar_verseschangeddescription
    before

    Given a verse, find other passages in the library that say something close to it — by meaning, not by shared words. 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.

    after · 90% of words in common

    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.

  • get_versechangeddescription
    before

    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.

    after · 73% of words in common

    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.

  • search_textschangeddescription
    before

    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. 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.

    after · 78% of words in common

    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.

  • list_authorsadded

    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.

  • list_workschangeddescription, input schema
    before

    List the works with their sizes, structure and available languages. Call it once at the start of a conversation about scripture, or when you need work slugs for filtering. It also tells you what is not translated: several works exist only in Russian. Check `languages` before promising the user an English text.

    after · 60% of words in common

    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.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 82 / 100

no-repository
provenance55
liveness98
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-94% +updated-5d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://mcp.vedaword.com streamable-httpnoneyes94%485 ms2025-11-252026-10-19

Tools (8)

browse_workread-onlyWalk 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.
find_similar_versesread-onlyGiven 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.
get_vaishnava_calendarread-onlyEkadashi 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.
get_verseread-onlyFetch 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.
list_authorsread-onlyList 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.
list_worksread-onlyList 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.
lookup_sanskrit_termread-onlyLook 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.
search_textsread-onlySearch 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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.vedaword/library",
  "icons": [
    {
      "src": "https://vedaword.com/icon.svg",
      "sizes": [
        "any"
      ],
      "mimeType": "image/svg+xml"
    },
    {
      "src": "https://vedaword.com/icon.png",
      "sizes": [
        "512x512"
      ],
      "mimeType": "image/png"
    }
  ],
  "title": "Vedaword",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.vedaword.com",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.1",
  "websiteUrl": "https://vedaword.com/en/mcp",
  "description": "Sanskrit scripture search: Mahabharata, Upanishads, Gita; cited verses, honest no-answer."
}