Ayurveda MCP Server by RoxyAPI
com.roxyapi/ayurvedaroxyapi.comstreamable-httpv1.0.1Scanned
Ayurvedic constitution from a birth chart, dinacharya, ritucharya and dosha catalogues for agents.
8 tools: 3 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 3
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Ayurveda MCP Server by RoxyAPI can do
The Ayurveda MCP Server by RoxyAPI is published by roxyapi.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (3 tools: post_ayurveda_constitution, post_ayurveda_dinacharya and post_ayurveda_ritucharya), but cannot delete data. 5 tools only read.
3 tools can send data out of your system (post_ayurveda_constitution, post_ayurveda_dinacharya and post_ayurveda_ritucharya).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 3Claude Code: ask
post_ayurveda_constitutionRead the Ayurvedic constitution from a sidereal birth chart and return the vata, pitta and kapha shares with a verse behind every factor.Can send data out1 finding
Why it is in this group
- The name "post_ayurveda_constitution" says "post": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe name "post_ayurveda_constitution" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_ayurveda_constitution" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "post_ayurveda_constitution" says "post": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
post_ayurveda_dinacharyaCompute 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.Can send data out1 finding
Why it is in this group
- The name "post_ayurveda_dinacharya" says "post": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe name "post_ayurveda_dinacharya" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_ayurveda_dinacharya" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "post_ayurveda_dinacharya" says "post": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
post_ayurveda_ritucharyaResolve the ritucharya, the Ayurvedic season, for a date from the real solar ingress instants and return the regimen the primary text gives for it.Can send data out1 finding
Why it is in this group
- The name "post_ayurveda_ritucharya" says "post": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe name "post_ayurveda_ritucharya" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_ayurveda_ritucharya" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "post_ayurveda_ritucharya" says "post": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
Only reads 5Show 5 read-only tools
get_ayurveda_dailyGet 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 …No findings
Why it is in this group
- The name "get_ayurveda_daily" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_ayurveda_doshasReturn vata, pitta and kapha with the qualities, seats and five sub-doshas each carries, and the three states the seasonal cycle moves them through.No findings
Why it is in this group
- The name "get_ayurveda_doshas" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_ayurveda_doshas_idReturn one dosha with its elements, qualities, seats, five sub-doshas and three states.No findings
Why it is in this group
- The name "get_ayurveda_doshas_id" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_ayurveda_qualitiesReturn 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 …No findings
Why it is in this group
- The name "get_ayurveda_qualities" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_ayurveda_tastesReturn the six rasas, the tastes of Ayurveda, with the complete eighteen-cell matrix of which taste lowers and raises which dosha, in both directions.No findings
Why it is in this group
- The name "get_ayurveda_tastes" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://roxyapi.com/mcp/ayurveda: tools/list returned 8 tools to an anonymous client, including post_ayurveda_constitution (write), post_ayurveda_dinacharya (write), post_ayurveda_ritucharya (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "post_ayurveda_constitution" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "post_ayurveda_constitution" says "post": a word for a change.
The server marks "post_ayurveda_dinacharya" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "post_ayurveda_dinacharya" says "post": a word for a change.
The server marks "post_ayurveda_ritucharya" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "post_ayurveda_ritucharya" says "post": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http ayurveda https://roxyapi.com/mcp/ayurveda --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http ayurveda https://roxyapi.com/mcp/ayurveda --header 'X-API-Key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ayurveda__get_ayurveda_daily",
"mcp__ayurveda__get_ayurveda_doshas",
"mcp__ayurveda__get_ayurveda_doshas_id",
"mcp__ayurveda__get_ayurveda_tastes",
"mcp__ayurveda__get_ayurveda_qualities"
],
"ask": [
"mcp__ayurveda__post_ayurveda_constitution",
"mcp__ayurveda__post_ayurveda_dinacharya",
"mcp__ayurveda__post_ayurveda_ritucharya"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ayurveda. Review it before you use it.
Capability tags behind 3 rules
- mcp__ayurveda__post_ayurveda_constitution outbound
- mcp__ayurveda__post_ayurveda_dinacharya outbound
- mcp__ayurveda__post_ayurveda_ritucharya outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.roxyapi/ayurveda/verify?hash=f549f18db74ef69806b89a02e5b4d60c0a0cb85525a89d27384b0e67d9bf292a" | jq -e '.changed == false'Pinned hash f549f18db74e, from Nov 17, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.roxyapi/ayurveda/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.roxyapi/ayurveda)Source: MCP Registry. Synced Oct 21, 2026, 18:02 UTC.
Ayurveda MCP Server by RoxyAPI: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ayurveda MCP Server by RoxyAPI safe?
- No scan can promise that. What its definitions show: 8 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Ayurveda MCP Server by RoxyAPI delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Ayurveda MCP Server by RoxyAPI do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Ayurveda MCP Server by RoxyAPI have?
- 8 tools: 3 write, 5 read. post_ayurveda_constitution, post_ayurveda_dinacharya, post_ayurveda_ritucharya, get_ayurveda_daily, get_ayurveda_doshas, get_ayurveda_doshas_id, get_ayurveda_tastes and get_ayurveda_qualities.
Does the Ayurveda MCP Server by RoxyAPI need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Ayurveda MCP Server by RoxyAPI send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): post_ayurveda_constitution, post_ayurveda_dinacharya and post_ayurveda_ritucharya.
Has the Ayurveda MCP Server by RoxyAPI changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.