# Vedaword (remote · mcp.vedaword.com)

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

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.vedaword.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-vedaword-library/mcp.md), [page](https://verifymcp.io/servers/com-vedaword-library/mcp)

## Channel facts

- Endpoint: `https://mcp.vedaword.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2543 tokens (~317/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Vedaword MCP server?

Vedaword is a hosted endpoint at https://mcp.vedaword.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-vedaword-library 'https://mcp.vedaword.com/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-vedaword-library": {
      "url": "https://mcp.vedaword.com/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-vedaword-library": {
      "type": "http",
      "url": "https://mcp.vedaword.com/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-vedaword-library]
url = "https://mcp.vedaword.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vedaword-library": {
      "type": "remote",
      "url": "https://mcp.vedaword.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-vedaword-library --url 'https://mcp.vedaword.com/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-vedaword-library:
    url: "https://mcp.vedaword.com/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-vedaword-library": {
      "Transport": "http",
      "Url": "https://mcp.vedaword.com/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-vedaword-library -t streamable-http -u 'https://mcp.vedaword.com/'
```

### Other

```json
{
  "mcpServers": {
    "com-vedaword-library": {
      "type": "http",
      "url": "https://mcp.vedaword.com/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, 0)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `search_texts` (~452 tokens)

Search the scriptures

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.

Input parameters:

- `full_text` (boolean): Return each passage whole instead of an excerpt. Use when you intend to quote; excerpts are for deciding what to quote.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.
- `limit` (integer): Passages to return. Default 8.
- `parts` (array): Which part of a verse to search: `verse` is the Sanskrit source text, `translation` the literary translation, `word_by_word` the gloss table, `commentary` Vedaword's own exposition, `bhashya` an ācār…
- `query` (string, required): A question, a phrase, a Sanskrit term, or a citation such as "BG 2.47". Any language, and Sanskrit in Devanāgarī or IAST. Quote the string to require the exact wording.
- `works` (array): Restrict to these works by slug — see list_works. Omit to search all.

### `get_verse` (~316 tokens)

Read one verse in full

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.

Input parameters:

- `context` (integer): Verses to include either side, within the same chapter. Use 1–2 when the argument depends on what surrounds the verse. Default 0.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.
- `verse` (string, required): A citation — "BG 2.47", "Бхагавад-гита 2.47", "Mahabharata 1.1.1", "Upanishads Mundaka 2.2.8" — or a `unit_id` from an earlier result.

### `lookup_sanskrit_term` (~225 tokens)

Look up a Sanskrit word

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.

Input parameters:

- `examples` (integer): Verses to cite as examples. Default 5.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.
- `term` (string, required): In IAST (śeṣa, diacritics optional) or Devanāgarī (शेष). A word written in another script is not in this dictionary — the headwords are Sanskrit — but search_texts will still find it in the prose.

### `find_similar_verses` (~255 tokens)

Find parallel passages

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.

Input parameters:

- `exclude_same_work` (boolean): Skip passages from the same work, so what comes back corroborates rather than repeats. Default false.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.
- `limit` (integer): Passages to return. Default 8.
- `verse` (string, required): A citation ("BG 2.47") or a `unit_id` from an earlier result.

### `get_vaishnava_calendar` (~254 tokens)

Vaishnava calendar at a place

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.

Input parameters:

- `days` (integer): How many days ahead, from today at the place. Default 30.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.
- `latitude` (number, required): Latitude of the place, degrees.
- `longitude` (number, required): Longitude of the place, degrees.
- `place_name` (string): The place's name, echoed back.
- `timezone` (string, required): IANA timezone, e.g. "Europe/Moscow".

### `list_works` (~266 tokens)

List the works in the library

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.

Input parameters:

- `author` (string): Only the works credited to this author id (see list_authors).
- `category` (string): Only the works on this shelf.
- `include_descriptions` (boolean): Add a paragraph describing each work. Default false.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.

### `list_authors` (~140 tokens)

List the authors in the library

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.

Input parameters:

- `era` (string): Only the authors of this period.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.

### `browse_work` (~351 tokens)

Browse a work in order

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.

Input parameters:

- `chapter` (integer): The chapter's `index` in the section's listing; it opens that chapter's verses.
- `language` (string): Preferred language of the translations returned. Not a filter: works that exist only in Russian are returned in Russian, and each result says which language it is actually in. Default: en.
- `limit` (integer): Verses per page. Default 20, at most 50.
- `offset` (integer): Where in the chapter to start, counting verses from 0. Default 0.
- `page` (integer): Which page of a section's chapters. Default 1.
- `page_size` (integer): Chapters per page. Default 50, at most 100.
- `section` (string): A section slug from the work's listing (a parva, a canto, an upaniṣad).
- `work` (string, required): A work slug, as list_works gives it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-vedaword-library/mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72

## Common questions

### What is the Vedaword MCP server?

Vedaword is an MCP server listed in the public MCP registry as com.vedaword/library. Sanskrit scripture search: Mahabharata, Upanishads, Gita; cited verses, honest no-answer. This page covers its hosted endpoint (https://mcp.vedaword.com).

### Is the Vedaword MCP server safe to use?

Vedaword scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Vedaword MCP server expose?

Vedaword exposes 8 tools: search_texts, get_verse, lookup_sanskrit_term, find_similar_verses, get_vaishnava_calendar, and 3 more. Their descriptions and schemas cost roughly 2,259 tokens of context every time the server is loaded.

### Does the Vedaword MCP server require authentication?

No. We connected to Vedaword without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Vedaword MCP server still maintained?

Vedaword is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.vedaword.com/
- Website: https://vedaword.com/en/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-vedaword-library/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vedaword-library/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-vedaword-library/mcp