# Vastu Shastra MCP Server by RoxyAPI (remote · roxyapi.com) Vastu entrance padas, the 81 pada mandala, plot and room analysis, Ayadi and griha pravesh timing. - Trust score: 80/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - remote · `roxyapi.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-roxyapi-vastu/mcp-vastu.md), [page](https://verifymcp.io/servers/com-roxyapi-vastu/mcp-vastu) ## Channel facts - Endpoint: `https://roxyapi.com/mcp/vastu` - 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**: 70/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 4752 tokens (~475/item across 10 items; 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 10 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 Vastu Shastra MCP Server by RoxyAPI server? Vastu Shastra MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/vastu, 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-vastu 'https://roxyapi.com/mcp/vastu' ``` ### Cursor ```json { "mcpServers": { "com-roxyapi-vastu": { "url": "https://roxyapi.com/mcp/vastu" } } } ``` ### VS Code ```json { "servers": { "com-roxyapi-vastu": { "type": "http", "url": "https://roxyapi.com/mcp/vastu" } } } ``` ### Codex ```toml [mcp_servers.com-roxyapi-vastu] url = "https://roxyapi.com/mcp/vastu" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-roxyapi-vastu": { "type": "remote", "url": "https://roxyapi.com/mcp/vastu", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-roxyapi-vastu --url 'https://roxyapi.com/mcp/vastu' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-roxyapi-vastu: url: "https://roxyapi.com/mcp/vastu" ``` ### Netclaw ```json { "McpServers": { "com-roxyapi-vastu": { "Transport": "http", "Url": "https://roxyapi.com/mcp/vastu" } } } ``` ### Vellum ```bash assistant mcp add com-roxyapi-vastu -t streamable-http -u 'https://roxyapi.com/mcp/vastu' ``` ### Other ```json { "mcpServers": { "com-roxyapi-vastu": { "type": "http", "url": "https://roxyapi.com/mcp/vastu" } } } ``` 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 80, +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 79, +1) - [cosmetic] “post_vastu_timing_griha_pravesh” reworded the description of “timezone” ### 2026-09-15 (score 78, +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 77, +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 76, +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 75, +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-06 (score 74, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-05 (score 73, 0) - [functional improvement] Stability: unverified → 0.03 - [cosmetic] “post_vastu_entrance” reworded the description of “doorPosition” ## MCP tools (10) ### `post_vastu_entrance` (~721 tokens) Calculate entrance pada - Vastu main door direction API 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. 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. - `door` (object): Where the main door sits, in plot coordinates. The point is snapped to the nearest boundary of the plot, so a coordinate read off a drawing that lands slightly inside or outside still resolves. Send… - `doorPosition` (number): Where the main door sits along the facing side, as a fraction from 0 to 1 measured from the corner the chapter starts that side at: the north-east for an east facing, the south-east for a south facin… - `facing` (string): Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, n… - `facingDegrees` (number): Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoint… - `grid` (string): Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the c… - `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… - `plot` (object, required): The ground the mandala is projected over. Send width and depth for a compass-aligned rectangle, or polygon for anything else. The x axis runs east and the y axis north, and the mandala is aligned to… ### `post_vastu_mandala` (~380 tokens) Generate Vastu Purusha Mandala - 81 pada and 64 pada grid API 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. 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. - `grid` (string): Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the c… - `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… - `plot` (object, required): The ground the mandala is projected over. Send width and depth for a compass-aligned rectangle, or polygon for anything else. The x axis runs east and the y axis north, and the mandala is aligned to… ### `post_vastu_plot` (~779 tokens) Analyse a plot - Vastu land and site assessment API 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. 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. - `cuts` (array): Quarters where a corner is missing from the rectangle. Every cut verdict is convention, for the same reason as the extensions. - `extensions` (array): Quarters where the plot bulges out beyond a rectangle. Every extension verdict is convention: the chapter states no rule for a named corner and the nearest verses speak of a figure with a limb wantin… - `facing` (string): Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, n… - `facingDegrees` (number): Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoint… - `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… - `plot` (object, required): The ground the mandala is projected over. Send width and depth for a compass-aligned rectangle, or polygon for anything else. The x axis runs east and the y axis north, and the mandala is aligned to… - `road` (string): Which side a road runs along. The verdict is convention: the chapter states no rule for the side a road is on, only that an obstruction facing the gate brings misery unless it lies beyond twice the h… - `slopeLowDirection` (string): Which quarter of the plot the ground falls toward, that is where the LOW point is. The chapter states its rules in terms of the side that stands HIGHER, so the opposite of this value is what the vers… - `slopeSchool` (string): Which reading of the ground level to lead with. brihat-samhita applies verses 115 to 117 as written, where a higher north-east is a loss, a higher east or north is permitted when level ground is unav… - `water` (string): Which quarter holds standing water, a well, a tank or a sump. This one IS sourced: 53.119 gives a distinct effect for each of the eight directions and calls only the north and the north-east favourab… ### `post_vastu_ayadi` (~785 tokens) Calculate Ayadi shadvarga - Vastu proportion and yoni calculator API 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. Input parameters: - `ayadiText` (string): Which family of Ayadi formulas to apply. manasara takes length, breadth and circumference separately and is double sourced. perimeter-texts runs every formula on the perimeter alone and is the family… - `breadth` (number, required): Breadth of the building or room, in the unit given. Under the Manasara family this is the measure the vyaya and yoni formulas multiply. - `circumference` (number): Circumference or height, if the Manasara vara and tithi formulas should read something other than the perimeter. Defaults to the perimeter, which is what a rectangular plan supplies. - `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. - `hastaInches` (number): Length of one hasta, the classical cubit, in inches. Defaults to 18, which is 24 angula at three quarters of an inch each and is the value three independent sources agree on. Raise it if your lineage… - `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… - `length` (number, required): Length of the building or room, in the unit given. Under the Manasara family this is the measure the aya and rksha formulas multiply; under the perimeter family it only feeds the perimeter. - `perimeter` (number): Perimeter of the plan, if it is not simply twice the length plus twice the breadth. The perimeter family runs every formula on this one measure, so it is the number that decides all six remainders th… - `unit` (string): Unit the Ayadi dimensions are given in. Every remainder is unit sensitive, so this is an input and never assumed: the same building measured in cubits and in feet gives different remainders. hasta is… - `vyayaFormula` (string): Which vyaya formula the perimeter family uses. The printed table gives two joined by the word or and states no rule for choosing. p9-10 multiplies by nine and divides by ten, which is the only diviso… ### `post_vastu_rooms` (~437 tokens) Check room placement - Vastu room direction compliance API 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. 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. - `facing` (string): Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, n… - `facingDegrees` (number): Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoint… - `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… - `plot` (object, required): The ground the mandala is projected over. Send width and depth for a compass-aligned rectangle, or polygon for anything else. The x axis runs east and the y axis north, and the mandala is aligned to… - `rooms` (array, required): The rooms to check, 1 to 24 of them. Each carries a type and either the quarter it sits in or its outline. ### `post_vastu_timing_griha_pravesh` (~652 tokens) Find griha pravesh dates - Vastu house warming muhurta API 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. 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. - `endDate` (string, required): Last day of the search window, in YYYY-MM-DD, inclusive. The window is capped at 93 days, which is a full season and the same cap the Vedic auspicious day search carries. - `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 of the house, in decimal degrees, positive north. Sunrise decides where one day ends and the next begins, so a nakshatra running out during the morning changes which day it counts for. - `longitude` (number, required): Longitude of the house, in decimal degrees, positive east. - `muhurtaText` (string): Which Muhurta text supplies the admissible nakshatras for entering a new house. muhurta-chintamani admits eight and kalaprakasika admits twelve; seven overlap and are the high confidence core, one is… - `startDate` (string, required): First day of the search window, in YYYY-MM-DD. Every limb is read at sunrise of the local day, because the Hindu day begins at sunrise rather than at midnight. - `timezone` (required): IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the o… ### `get_vastu_directions` (~255 tokens) List the eight directions - Vastu dikpala and direction reference API 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. 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-8, default 8. - `offset` (integer|null): Number of items to skip for pagination. Default 0. ### `get_vastu_directions_id` (~239 tokens) Look up one direction - Vastu dikpala reference API 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. 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): Direction id, one of North, Northeast, East, Southeast, South, Southwest, West, Northwest. Case and punctuation are folded. - `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_vastu_devatas` (~259 tokens) List the 45 devatas - Vastu Purusha Mandala reference API 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. 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-45, default 45. - `offset` (integer|null): Number of items to skip for pagination. Default 0. ### `get_vastu_devatas_id` (~245 tokens) Look up one devata - Vastu mandala devata reference API 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. 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): Devata id, lower case transliteration. The two Indras are indra-outer for the east perimeter square and indra-inner for the inner ring one. Case and punctuation are folded. - `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… ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-roxyapi-vastu/mcp-vastu#diagnostics ## Score history - 2026-09-20: 80 - 2026-09-19: 80 - 2026-09-18: 79 - 2026-09-17: 79 - 2026-09-16: 78 - 2026-09-15: 78 - 2026-09-14: 77 - 2026-09-13: 77 - 2026-09-12: 76 - 2026-09-11: 76 - 2026-09-10: 75 - 2026-09-09: 75 - 2026-09-08: 74 - 2026-09-07: 74 - 2026-09-06: 74 - 2026-09-05: 73 - 2026-09-04: 73 ## Common questions ### What is the Vastu Shastra MCP Server by RoxyAPI server? Vastu Shastra MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/vastu. Vastu entrance padas, the 81 pada mandala, plot and room analysis, Ayadi and griha pravesh timing. This page covers its hosted endpoint (https://roxyapi.com/mcp/vastu). ### Is the Vastu Shastra MCP Server by RoxyAPI server safe to use? Vastu Shastra MCP Server by RoxyAPI scores 80 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 Vastu Shastra MCP Server by RoxyAPI server expose? Vastu Shastra MCP Server by RoxyAPI exposes 10 tools: post_vastu_entrance, post_vastu_mandala, post_vastu_plot, post_vastu_ayadi, post_vastu_rooms, and 5 more. Their descriptions and schemas cost roughly 4,752 tokens of context every time the server is loaded. ### Does the Vastu Shastra MCP Server by RoxyAPI server require authentication? No. We connected to Vastu Shastra MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the Vastu Shastra MCP Server by RoxyAPI server still maintained? Vastu Shastra 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/vastu - Authorisation metadata: https://roxyapi.com/.well-known/oauth-protected-resource/mcp/vastu - Website: https://roxyapi.com/products/vastu-api - Changelog RSS feed: https://verifymcp.io/servers/com-roxyapi-vastu/mcp-vastu.xml - Changelog JSON feed: https://verifymcp.io/servers/com-roxyapi-vastu/mcp-vastu.json - HTML version of this page: https://verifymcp.io/servers/com-roxyapi-vastu/mcp-vastu