# Ayurveda MCP Server by RoxyAPI (remote · roxyapi.com)

Ayurvedic constitution from a birth chart, dinacharya, ritucharya and dosha catalogues for agents.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

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

## Channel facts

- Endpoint: `https://roxyapi.com/mcp/ayurveda`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-09-20.

- **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**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3408 tokens (~426/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Ayurveda MCP Server by RoxyAPI server?

Ayurveda MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/ayurveda, 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-roxyapi-ayurveda 'https://roxyapi.com/mcp/ayurveda'
```

### Cursor

```json
{
  "mcpServers": {
    "com-roxyapi-ayurveda": {
      "url": "https://roxyapi.com/mcp/ayurveda"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-roxyapi-ayurveda]
url = "https://roxyapi.com/mcp/ayurveda"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-roxyapi-ayurveda:
    url: "https://roxyapi.com/mcp/ayurveda"
```

### Netclaw

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

### Vellum

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

### Other

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

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-09-19 (score 81, +1)

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

### 2026-09-17 (score 80, +1)

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

### 2026-09-15 (score 79, +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-09-13 (score 78, +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.

### 2026-09-11 (score 77, +1)

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

### 2026-09-09 (score 76, +1)

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

### 2026-09-07 (score 75, +1)

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

### 2026-09-05 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `post_ayurveda_constitution` (~755 tokens)

Ayurvedic constitution from a birth chart - Dosha profile API

Read the Ayurvedic constitution from a sidereal birth chart and return the vata, pitta and kapha shares with a verse behind every factor. Three factors are scored, each one carrying a classical rule that it shows the native humour: the rising sign, the sign the Moon occupies, and the strongest graha by shadbala. The composite that blends them is a RoxyAPI convention rather than a classical one, so its version and its weights ship inside the response, and every response states that this is general wellness and cultural interest only.

Input parameters:

- `ayanamsa` (string): Sidereal frame the chart is cast in. "lahiri" is the traditional Vedic standard used by most software and is the default. "raman" sits about 1.45 degrees below it. "kp-newcomb" and "kp-old" are the t…
- `ayanamsaValue` (number): Custom sidereal frame value in degrees. Required when ayanamsa is "custom" and ignored otherwise. Use it to reconcile exactly against a specific reference program.
- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `date` (string, required): Birth date in YYYY-MM-DD format. It sets the sidereal positions the whole reading is built from, so an approximate date gives an approximate constitution.
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
- `latitude` (number, required): Birth latitude in decimal degrees. It sets the local sidereal time behind the rising sign, and it feeds the strength of each graha through the sunrise at that place.
- `longitude` (number, required): Birth longitude in decimal degrees. It sets the local sidereal time behind the rising sign, together with the latitude.
- `signDoshaScheme` (string): Which classical sign table the rising sign and the Moon sign are read through. "satyacharya" is the twelve-sign extract appended to Brihat Jataka 18.20, carried in two independent public-domain trans…
- `time` (string, required): Birth time in 24-hour HH:MM:SS format. The rising sign turns roughly every two hours and carries the heaviest weight of the three factors, so time is the input a reading is most sensitive to.
- `timezone`: Timezone as an IANA name such as "Asia/Kolkata", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the birth date, so a summer-time birth is placed correctl…

### `post_ayurveda_dinacharya` (~569 tokens)

Dinacharya daily routine - Brahma muhurta and dosha clock API

Compute the dinacharya daily routine for one date and one place: sunrise, sunset, the brahma muhurta window, and the six dosha periods of the day and the night. The default division cuts the actual day and the actual night into thirds, which is what the frame chapter states, and the modern clock grid is returned alongside it under its own label so a caller can show either. The brahma muhurta is a fixed window of 96 to 48 minutes before sunrise rather than a share of the night, which is the reading the classical commentary settles on.

Input parameters:

- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `date` (string, required): The local calendar date, in YYYY-MM-DD format. Sunrise and sunset are computed for this date at the given place, and the whole routine follows from them, so the answer changes through the year at any…
- `doshaClock` (string): How the six dosha periods are cut. "sunrise-anchored" divides the actual day and the actual night at this place into thirds, which is the division the frame chapter states, and is the default. "clock…
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
- `latitude` (number, required): Latitude in decimal degrees. It sets how long the day and the night actually are, which is the whole difference between this and a printed timetable: at 51 north in June the day runs about sixteen an…
- `longitude` (number, required): Longitude in decimal degrees. It sets the clock time of sunrise at this place.
- `timezone`: Timezone as an IANA name such as "Europe/London", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the requested date. It decides which local day is meant…

### `post_ayurveda_ritucharya` (~651 tokens)

Ayurveda seasonal regimen - Ritucharya and ritu resolution API

Resolve the ritucharya, the Ayurvedic season, for a date from the real solar ingress instants and return the regimen the primary text gives for it. The response carries the season with its exact opening and closing instants, the half of the year the sun is in, where each dosha stands in the seasonal cycle, the taste that grows across the season, and the behaviour items the chapter states. Season boundaries are measured in the tropical zodiac by default, which is what published almanacs use, and the sidereal reading is available as a convention and runs about 24 days later.

Input parameters:

- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `date` (string, required): The date to resolve, in YYYY-MM-DD format. The season is read at midday UTC on this date, because a season boundary is an instant and a calendar day has to be reduced to one; on a day that carries a…
- `hemisphere` (string): Which half of the world the season names are stated for. Defaults to "northern", which is the half the primary text describes. It is NEVER inferred from a latitude: a silent flip would change the ans…
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
- `rituZodiac` (string): Which zodiac the solar-month boundaries are measured in. "sayana" is the tropical reading, which is what published almanacs use for seasons and is the default. "nirayana" is the sidereal reading in t…
- `ritucharyaScheme` (string): Which six-season division the year is cut into. "sutrasthana-6" is the standard set of sisira, vasanta, grisma, varsa, sarad and hemanta, and is the default. "vimana-8" is the alternate division in w…

### `get_ayurveda_daily` (~409 tokens)

Daily Ayurveda reading - Dosha clock and brahma muhurta by location API

Get one days Ayurveda reading for a place: sunrise, the brahma muhurta window, the six dosha periods cut from the actual day and night, and the season the date falls in with where each dosha stands in its yearly cycle. It composes the routine and the season routes for one location so a widget needs one call rather than two. The default conventions apply throughout and are echoed; call those two routes directly to choose a different season scheme, zodiac, hemisphere or dosha clock.

Input parameters:

- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `date` (string): Reading date in YYYY-MM-DD format. Past and future dates are both supported, for editorial scheduling and backfill. Defaults to the current day in the timezone parameter.
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
- `latitude` (number|null): Latitude in decimal degrees. It sets how long the day and the night actually are, which is what the dosha periods are cut from.
- `longitude` (number|null): Longitude in decimal degrees. It sets the clock time of sunrise at this place.
- `timezone` (string): Selects which day counts as current when date is omitted, and which local day sunrise is computed for. Defaults to UTC, so the reading rolls over at 00:00 UTC. Accepts an IANA name (e.g. "Europe/Lond…

### `get_ayurveda_doshas` (~274 tokens)

List the three doshas - Dosha catalogue API

Return vata, pitta and kapha with the qualities, seats and five sub-doshas each carries, and the three states the seasonal cycle moves them through. Every quality is one of the twenty gunas and every state is described as a position and a quality rather than as a complaint, which is what lets the catalogue join to the tastes and qualities endpoints without a lookup table in between. Each entry carries the verse it comes from, and the second primary text is recorded where it reads the list differently.

Input parameters:

- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
- `limit` (integer): Maximum items to return per page. Range: 1-3, default 3.
- `offset` (integer|null): Number of items to skip for pagination. Default 0.

### `get_ayurveda_doshas_id` (~206 tokens)

Get one dosha - Vata pitta kapha profile API

Return one dosha with its elements, qualities, seats, five sub-doshas and three states. Use it to render a dosha card or a glossary entry without pulling the whole catalogue, and read qualityGunas to join it to the twenty qualities.

Input parameters:

- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `id` (string, required): Dosha identifier, case-insensitive. One of vata, pitta or kapha.
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…

### `get_ayurveda_tastes` (~266 tokens)

List the six tastes - Ayurveda rasa and dosha matrix API

Return the six rasas, the tastes of Ayurveda, with the complete eighteen-cell matrix of which taste lowers and raises which dosha, in both directions. The order is the one the root verse gives, which is also the order of strength it states, and it puts bitter before pungent where most modern lists reverse them. The matrix is returned on each taste and again as a per-dosha index, so a caller can read it either way without deriving one from the other.

Input parameters:

- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
- `limit` (integer): Maximum items to return per page. Range: 1-6, default 6.
- `offset` (integer|null): Number of items to skip for pagination. Default 0.

### `get_ayurveda_qualities` (~278 tokens)

List the twenty qualities - Ayurveda guna pairs API

Return the twenty gunas, the qualities of Ayurveda, as the ten opposed pairs the commentaries spell out, each member with the single action word attached to it, and the half-verse that states the like-increases-like rule the whole domain runs on. Each quality carries the doshas that hold it, so the pairs join straight to the dosha catalogue. One pair carries a recorded disagreement between the two commentaries, and the response states it rather than resolving it silently, because the choice decides which dosha that pair joins to.

Input parameters:

- `compact` (boolean): Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
- `lang` (string): Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
- `limit` (integer): Maximum items to return per page. Range: 1-10, default 10.
- `offset` (integer|null): Number of items to skip for pagination. Default 0.

## Diagnostics

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

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 74

## Common questions

### What is the Ayurveda MCP Server by RoxyAPI server?

Ayurveda MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/ayurveda. Ayurvedic constitution from a birth chart, dinacharya, ritucharya and dosha catalogues for agents. This page covers its hosted endpoint (https://roxyapi.com/mcp/ayurveda).

### Is the Ayurveda MCP Server by RoxyAPI server safe to use?

Ayurveda MCP Server by RoxyAPI scores 81 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 Ayurveda MCP Server by RoxyAPI server expose?

Ayurveda MCP Server by RoxyAPI exposes 8 tools: post_ayurveda_constitution, post_ayurveda_dinacharya, post_ayurveda_ritucharya, get_ayurveda_daily, get_ayurveda_doshas, and 3 more. Their descriptions and schemas cost roughly 3,408 tokens of context every time the server is loaded.

### Does the Ayurveda MCP Server by RoxyAPI server require authentication?

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

### Is the Ayurveda MCP Server by RoxyAPI server still maintained?

Ayurveda MCP Server by RoxyAPI is still listed as active in the MCP registry. We last reached this channel on 20 September 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://roxyapi.com/mcp/ayurveda
- Authorisation metadata: https://roxyapi.com/.well-known/oauth-protected-resource/mcp/ayurveda
- Website: https://roxyapi.com/products/ayurveda-api
- Changelog RSS feed: https://verifymcp.io/servers/com-roxyapi-ayurveda/mcp-ayurveda.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-roxyapi-ayurveda/mcp-ayurveda.json
- HTML version of this page: https://verifymcp.io/servers/com-roxyapi-ayurveda/mcp-ayurveda