Vastu Shastra MCP Server by RoxyAPI
com.roxyapi/vasturoxyapi.comstreamable-httpv1.0.1Scanned
Vastu entrance padas, the 81 pada mandala, plot and room analysis, Ayadi and griha pravesh timing.
10 tools: 6 change things and 4 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 6
- 6 findings
Tools listed without sign-in. Remote posture
With Anlyon
6 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 Vastu Shastra MCP Server by RoxyAPI can do
The Vastu Shastra MCP Server by RoxyAPI is published by roxyapi.com, a domain the MCP Registry verified. It has 10 tools. It can create or change data (6 tools: post_vastu_entrance, post_vastu_mandala, post_vastu_plot, post_vastu_ayadi and 2 more), but cannot delete data. 4 tools only read.
2 tools read private data (get_vastu_directions and get_vastu_devatas); 6 tools can send data out of your system (post_vastu_entrance, post_vastu_mandala, post_vastu_plot and 3 more).
The fixed checks matched 6 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
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.
10 tools
Changes things 6Claude Code: ask
post_vastu_ayadiAyadi shadvarga calculator for a building or a room: send the dimensions and the API returns all six proportional formulas with the multiplier, the divisor and the remainder shown,…Can send data out1 finding
Why it is in this group
- The name "post_vastu_ayadi" 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_vastu_ayadi" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_vastu_ayadi" 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_vastu_ayadi" says "post": a word for a change.
Description, as the server wrote it Ayadi shadvarga calculator for a building or a room: send the dimensions and the API returns all six proportional formulas with the multiplier, the divisor and the remainder shown, the member each remainder names, and the two verdict rules the texts state. Choose between three text families, which genuinely disagree, and choose your own cubit length, because every remainder is unit sensitive. Built for practitioner tools, plan checking software and anyone who has to justify a dimension rather than assert it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
post_vastu_entranceVastu entrance analysis for a main door: send the plot and where the door sits, and the API returns which of the 32 perimeter padas it falls on, the devata of that square, the effe…Can send data out1 finding
Why it is in this group
- The name "post_vastu_entrance" 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_vastu_entrance" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_vastu_entrance" 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_vastu_entrance" says "post": a word for a change.
Description, as the server wrote it Vastu entrance analysis for a main door: send the plot and where the door sits, and the API returns which of the 32 perimeter padas it falls on, the devata of that square, the effect the classical chapter gives that pada, and the favourable padas on the same side to move toward. Every verdict carries the chapter and verse it comes from as a typed field, and the reading holds on either the 81 pada or the 64 pada division. Built for property and interior design tools, practitioner reports, and any product that has to say whether a front door is well placed.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
post_vastu_mandalaVastu Purusha Mandala projected over a real plot: send the ground and the API returns every square with the devata holding it, the brahmasthan as a polygon you can draw, the marma …Can send data out1 finding
Why it is in this group
- The name "post_vastu_mandala" 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_vastu_mandala" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_vastu_mandala" 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_vastu_mandala" says "post": a word for a change.
Description, as the server wrote it Vastu Purusha Mandala projected over a real plot: send the ground and the API returns every square with the devata holding it, the brahmasthan as a polygon you can draw, the marma points, the six vamsa diagonals named by their devatas and the nine atimarma crossings. Choose the 81 pada Paramasayika or the 64 pada Manduka, and the response says which verses each part rests on. Built for floor plan overlays, practitioner reports and any tool that has to place rooms against the classical grid.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
post_vastu_plotVastu plot analysis from typed geometry: send the outline, the facing, where the ground falls and where the water is, and the API returns a verdict on the shape, the proportion, th…Can send data out1 finding
Why it is in this group
- The name "post_vastu_plot" 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_vastu_plot" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_vastu_plot" 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_vastu_plot" says "post": a word for a change.
Description, as the server wrote it Vastu plot analysis from typed geometry: send the outline, the facing, where the ground falls and where the water is, and the API returns a verdict on the shape, the proportion, the ground level under two schools, each corner extension and cut, the road and the water. Every verdict names the chapter and verse behind it, or says plainly that it is convention, which matters because the ground level verses and the widely taught modern rule genuinely disagree. Built for listing and land assessment tools, practitioner site reports and buyer facing checks.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
post_vastu_roomsVastu room direction check for a whole floor plan: send the plot and a list of rooms, by quarter or by outline, and the API returns a verdict per room with the quarters it belongs …Can send data out1 finding
Why it is in this group
- The name "post_vastu_rooms" 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_vastu_rooms" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_vastu_rooms" 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_vastu_rooms" says "post": a word for a change.
Description, as the server wrote it Vastu room direction check for a whole floor plan: send the plot and a list of rooms, by quarter or by outline, and the API returns a verdict per room with the quarters it belongs in, the quarters to keep it out of, a remedy when it is misplaced, and a composite score with the weights published. Four of the twelve room types carry a chapter and verse and the other eight are labelled convention, so a report can say which half of it is classical. Built for floor plan tools, listing checks and practitioner reports.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
post_vastu_timing_griha_praveshGriha pravesh muhurta search over a date window: send the window and the place, and the API returns every day that clears the classical day-level rules, with the nakshatra, tithi, …Can send data out1 finding
Why it is in this group
- The name "post_vastu_timing_griha_pravesh" 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_vastu_timing_griha_pravesh" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "post_vastu_timing_griha_pravesh" 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_vastu_timing_griha_pravesh" says "post": a word for a change.
Description, as the server wrote it Griha pravesh muhurta search over a date window: send the window and the place, and the API returns every day that clears the classical day-level rules, with the nakshatra, tithi, weekday and solar position that qualified it and the rule ids that admitted it. Two Muhurta texts disagree on the admissible nakshatras and you choose which one leads, and the rules a date search cannot settle are published rather than dropped. Built for house warming date pickers, practitioner scheduling and agent assistants that have to answer when a family should move in.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
Only reads 4Show 4 read-only tools
get_vastu_devatasReference table of the 45 devatas of the Vastu Purusha Mandala: which squares of the 81 pada grid each one holds, which ring and which side, how many padas, and the verses that pla…Reads private dataNo findings
Why it is in this group
- The name "get_vastu_devatas" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it Reference table of the 45 devatas of the Vastu Purusha Mandala: which squares of the 81 pada grid each one holds, which ring and which side, how many padas, and the verses that place it. A pure reference endpoint with no plot required, for building a mandala diagram or a glossary. Where the sources contradict each other, and they do on several rows, the row says so instead of quietly picking a side.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_vastu_devatas_idLook up one devata of the Vastu Purusha Mandala: the squares it holds, its ring and side, its pada count, the entrance pada it governs where it sits on the perimeter, and the verse…No findings
Why it is in this group
- The name "get_vastu_devatas_id" says "get": a word for reading.
Description, as the server wrote it Look up one devata of the Vastu Purusha Mandala: the squares it holds, its ring and side, its pada count, the entrance pada it governs where it sits on the perimeter, and the verses that place it. Case and punctuation in the id are folded, so indra-outer, Indra_Outer and INDRA OUTER all resolve.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_vastu_directionsReference table of the eight Vastu directions: the dikpala who rules each quarter of the horizon, the squares of the mandala it covers with their devatas, what the chapter places o…Reads private dataNo findings
Why it is in this group
- The name "get_vastu_directions" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it Reference table of the eight Vastu directions: the dikpala who rules each quarter of the horizon, the squares of the mandala it covers with their devatas, what the chapter places on that side, and what standing water there brings. A pure reference endpoint with no plot required, for building a picker or a directions guide. Every row says which verse each part comes from and labels the element as the later convention it is.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_vastu_directions_idLook up one Vastu direction: its dikpala, the mandala squares it covers with their devatas, what the chapter places there, and what standing water in that quarter brings.No findings
Why it is in this group
- The name "get_vastu_directions_id" says "get": a word for reading.
Description, as the server wrote it Look up one Vastu direction: its dikpala, the mandala squares it covers with their devatas, what the chapter places there, and what standing water in that quarter brings. Case and punctuation in the id are folded, so north-east, northeast and NorthEast all resolve to the same entry, and the id space is the one the feng shui and I Ching endpoints use.
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 untrusted-input.
- Reads private data2
- 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 out6
- 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:28 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
- 6
- 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 6 tools that change things (6 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/vastu: tools/list returned 10 tools to an anonymous client, including post_vastu_entrance (write), post_vastu_mandala (write), post_vastu_plot (write), post_vastu_ayadi (write), post_vastu_rooms (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "post_vastu_entrance" 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_vastu_entrance" says "post": a word for a change.
The server marks "post_vastu_mandala" 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_vastu_mandala" says "post": a word for a change.
- Warnpost_vastu_plot
The server marks "post_vastu_plot" 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_vastu_plot" says "post": a word for a change.
- Warnpost_vastu_ayadi
The server marks "post_vastu_ayadi" 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_vastu_ayadi" says "post": a word for a change.
- Warnpost_vastu_rooms
The server marks "post_vastu_rooms" 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_vastu_rooms" says "post": a word for a change.
The server marks "post_vastu_timing_griha_pravesh" 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_vastu_timing_griha_pravesh" says "post": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:post_vastu_entranceChanges thingsinputSchema
- Changed:post_vastu_mandalaChanges thingsinputSchema
- Changed:post_vastu_plotChanges thingsinputSchema
- Changed:post_vastu_roomsChanges thingsinputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http vastu https://roxyapi.com/mcp/vastu --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http vastu https://roxyapi.com/mcp/vastu --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__vastu__get_vastu_directions",
"mcp__vastu__get_vastu_directions_id",
"mcp__vastu__get_vastu_devatas",
"mcp__vastu__get_vastu_devatas_id"
],
"ask": [
"mcp__vastu__post_vastu_entrance",
"mcp__vastu__post_vastu_mandala",
"mcp__vastu__post_vastu_plot",
"mcp__vastu__post_vastu_ayadi",
"mcp__vastu__post_vastu_rooms",
"mcp__vastu__post_vastu_timing_griha_pravesh"
],
"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 vastu. Review it before you use it.
Capability tags behind 8 rules
- mcp__vastu__post_vastu_entrance outbound
- mcp__vastu__post_vastu_mandala outbound
- mcp__vastu__post_vastu_plot outbound
- mcp__vastu__post_vastu_ayadi outbound
- mcp__vastu__post_vastu_rooms outbound
- mcp__vastu__post_vastu_timing_griha_pravesh outbound
- mcp__vastu__get_vastu_directions private-data
- mcp__vastu__get_vastu_devatas private-data
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/vastu/verify?hash=4c00d69bc85c4e501e7bfe7130b37543a13ae37ed05cdf5ef4fd1e132b720c65" | jq -e '.changed == false'Pinned hash 4c00d69bc85c, from Nov 17, 2026, 19: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/vastu/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.roxyapi/vastu)Source: MCP Registry. Synced Oct 21, 2026, 18:02 UTC.
Vastu Shastra MCP Server by RoxyAPI: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Vastu Shastra MCP Server by RoxyAPI safe?
- No scan can promise that. What its definitions show: 10 tools, 6 of which can change, send or delete something, and 6 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 Vastu Shastra 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 Vastu Shastra 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 Vastu Shastra MCP Server by RoxyAPI have?
- 10 tools: 6 write, 4 read. post_vastu_entrance, post_vastu_mandala, post_vastu_plot, post_vastu_ayadi, post_vastu_rooms, post_vastu_timing_griha_pravesh, get_vastu_directions, get_vastu_directions_id and 2 more.
Does the Vastu Shastra MCP Server by RoxyAPI need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Vastu Shastra MCP Server by RoxyAPI send data to outside services?
- 6 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): post_vastu_entrance, post_vastu_mandala, post_vastu_plot, post_vastu_ayadi, post_vastu_rooms and post_vastu_timing_griha_pravesh.
Has the Vastu Shastra MCP Server by RoxyAPI changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.