Vastu Shastra MCP Server by RoxyAPI
by roxyapi.com · remote · no sign-in to list tools · v1.0.1 · published by com.roxyapi
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.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things6Claude Code: ask: see these tools
- Only reads4Claude Code: allow: see these tools
6 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http vastu https://roxyapi.com/mcp/vastu --header 'X-API-Key: <your-x-api-key>'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.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
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,…1 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.
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…1 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.
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 …1 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.
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…1 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.
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 …1 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.
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, …1 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.
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 4Claude Code: allow
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…No findings
Why it is in this group
- The name "get_vastu_devatas" says "get": a word for reading.
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…No findings
Why it is in this group
- The name "get_vastu_directions" says "get": a word for reading.
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.
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>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change, 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. It assumes the server is installed as vastu. Review it before you use it.