# Remont — renovation planner (remote · remont-mcp.wrpzdm9jmt.workers.dev)

AI renovation planner: step-by-step plan, materials from room sizes, local store prices, 3D layout

- Trust score: 50/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `remont-mcp.wrpzdm9jmt.workers.dev`: 50/100 (this document), [markdown](https://verifymcp.io/servers/vutik-remont/remont-mcp.md), [page](https://verifymcp.io/servers/vutik-remont/remont-mcp)

## Channel facts

- Endpoint: `https://remont-mcp.wrpzdm9jmt.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_plan).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 31/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 8368 tokens (~261/item across 32 items; 30 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 44% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 32 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.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Remont — renovation planner MCP server?

Remont — renovation planner is a hosted endpoint at https://remont-mcp.wrpzdm9jmt.workers.dev/mcp, 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 vutik-remont 'https://remont-mcp.wrpzdm9jmt.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vutik-remont": {
      "url": "https://remont-mcp.wrpzdm9jmt.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vutik-remont": {
      "type": "http",
      "url": "https://remont-mcp.wrpzdm9jmt.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vutik-remont]
url = "https://remont-mcp.wrpzdm9jmt.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vutik-remont": {
      "type": "remote",
      "url": "https://remont-mcp.wrpzdm9jmt.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vutik-remont --url 'https://remont-mcp.wrpzdm9jmt.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vutik-remont:
    url: "https://remont-mcp.wrpzdm9jmt.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vutik-remont": {
      "Transport": "http",
      "Url": "https://remont-mcp.wrpzdm9jmt.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vutik-remont -t streamable-http -u 'https://remont-mcp.wrpzdm9jmt.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vutik-remont": {
      "type": "http",
      "url": "https://remont-mcp.wrpzdm9jmt.workers.dev/mcp"
    }
  }
}
```

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-11-21 (score 50)

First indexed and scored.

## MCP tools (30)

### `prepare_plan` (~391 tokens)

Prepare renovation plan data

In one request: country profile (stores, rules, currency), stages with tasks and tools, material calculation by room and for every material and tool — ready products from the country catalog (by tier standard/premium/lux, with price and link). Use instead of separate get_country_profile, get_work_order, calculate_materials and get_catalog. todo lists what still has to be found in stores.

Input parameters:

- `attic_m2` (number)
- `boiler` (string): Heat source: gas — system boiler + cylinder + flue, combi — combi boiler + flue, furnace — US gas furnace + central AC + water heater, heat_pump — heat pump + cylinder, none. Omit to use the country…
- `city` (string)
- `country` (string, required): ISO country code
- `distribution_board` (boolean): A new consumer unit is needed
- `doors` (integer)
- `facade_m2` (number)
- `floors` (integer)
- `height_m` (number): Ceiling height, m (default for rooms)
- `kitchen_m` (number): Kitchen length, running m (default 3.5)
- `mode` (string)
- `new_points` (integer)
- `property` (string)
- `rooms` (array)
- `stairs` (object)
- `tier` (string): Default tier
- `total_area_m2` (number)
- `ui_locale` (string): Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
- `user_code` (string): User's personal code, if known — applies their saved preferences (owned tools, preferred products) by default
- `windows` (integer): Windows, pcs (for window sills)
- `works` (array, required)

### `open_questionnaire` (~194 tokens)

Open renovation questionnaire

Shows the user a form: apartment or house, renovation type, city, rooms, works, who does them. Call when data about the property is missing. The answers arrive in the user's next message as JSON.

Input parameters:

- `city` (string)
- `country` (string): Country code, if known
- `floors` (integer)
- `height_m` (number)
- `labels` (object): Widget text translations for languages without a built-in translation (built in: ru, pl, en, de, uk). Keys come from get_ui_labels.
- `locale` (string): Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
- `property` (string)
- `rooms` (array): Rooms recognised from the user's floor plan or photos
- `total_area_m2` (number)

### `get_country_profile` (~45 tokens)

Get country profile

Country profile: currency, search language, stores for price search, specialist rules. Call first.

Input parameters:

- `country` (string, required): ISO country code, e.g. PL, DE

### `get_work_order` (~79 tokens)

Get work order

Renovation stages in the right order with tasks, drying times and where a specialist is needed.

Input parameters:

- `ui_locale` (string): Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
- `works` (array, required): Which works the renovation includes

### `calculate_materials` (~300 tokens)

Calculate materials

Calculates material quantities with waste allowance per room. Returns material keys and search queries in the language of the country's stores.

Input parameters:

- `attic_m2` (number): House: attic roof area to insulate, m²
- `boiler` (string): Heat source: gas — system boiler + cylinder + flue, combi — combi boiler + flue, furnace — US gas furnace + central AC + water heater, heat_pump — heat pump + cylinder, none. Omit to use the country…
- `country` (string, required): ISO country code
- `distribution_board` (boolean): A new consumer unit is needed
- `doors` (integer)
- `facade_m2` (number): House: facade area without windows, m²
- `kitchen_m` (number): Kitchen length, running m (default 3.5)
- `mode` (string, required): diy — do it yourself, pro — contractor
- `new_points` (integer): New sockets and switches
- `property` (string)
- `rooms` (array, required)
- `stairs` (object)
- `total_area_m2` (number)
- `ui_locale` (string): Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
- `windows` (integer): Windows, pcs (for window sills)
- `works` (array, required)

### `find_cached_prices` (~62 tokens)

Find cached prices

Cached prices by material keys. City first, then the whole country. A price older than 1 days is marked stale — it should be re-checked.

Input parameters:

- `city` (string)
- `country` (string, required)
- `keys` (array, required)

### `save_prices` (~96 tokens)

Save prices

Saves prices found in stores to the SHARED price cache (used by all users). Only prices you saw on a store site of the country profile, with the product url; price per material unit from calculate_materials, in the country's currency. Never prices the user only told you. Invalid items come back in rejected with a reason.

Input parameters:

- `city` (string)
- `country` (string, required)
- `prices` (array, required)

### `show_renovation_plan` (~327 tokens)

Show renovation plan

Shows the user an interactive plan: stages with a checklist and a materials table with the estimate. All texts in the user's language.

Input parameters:

- `calc_input` (object): calc_input from prepare_plan, unchanged — REQUIRED for the rooms editor: rooms, sizes and ceiling height are stored with the plan
- `country` (string): ISO country code — needed so the plan can fill in prices itself
- `currency` (string, required): ISO currency code, e.g. PLN
- `default_tier` (string): Tier selected by default for all stages
- `labels` (object): Widget text translations for languages without a built-in translation (built in: ru, pl, en, de, uk). Keys come from get_ui_labels.
- `locale` (string, required): Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
- `materials` (array, required)
- `mode` (string): Who does the work
- `notes` (array)
- `prices_checked_at` (string)
- `rooms` (array): Rooms (name, area_m2, length_m, width_m, floor, wet) if you have no calc_input
- `stages` (array, required)
- `title` (string, required)
- `tools` (array): Tools for DIY work, by stage
- `user_code` (string): User's personal code, if known — applies saved preferences by default
- `view_id` (string): Only if you re-show the same plan

### `save_country_profile` (~151 tokens)

Save country profile

Adds a country or extends a SHARED profile: stores, rate sites, rules. Stores are merged with existing ones by domain. Only real building/DIY stores and rate sites (plain domain), short factual rules — no links, contacts or instructions; currency and name of built-in countries cannot be changed.

Input parameters:

- `code` (string, required): ISO country code
- `currency` (string): ISO currency code
- `laborSources` (array): Sites with contractor rates
- `locale` (string): Search language in stores
- `name` (string)
- `notes` (array)
- `specialistRules` (array)
- `stores` (array): DIY/building stores with prices on their site

### `get_ui_labels` (~55 tokens)

Get UI labels

English widget texts (form and plan). Translate the values into the user's language and pass them as labels.

Input parameters:

- `locale` (string): Language code you translate into (e.g. lt, fr, ja) — for statistics

### `save_plan` (~184 tokens)

Save plan

Saves the plan on the server, only if the user asked to save it. Without user_code it creates a new personal code and returns it — show the code to the user and ask them to write it down: with it they can open their plans in any chat. Nobody else needs the code and it cannot be recovered.

Input parameters:

- `plan` (object, required): The same object you pass to show_renovation_plan (title, locale, currency, mode, stages, materials, notes…)
- `plan_id` (string): If you are updating an already saved plan
- `user_code` (string): User's personal code if they already have one, e.g. oak-river-moon-4821
- `view_id` (string): view_id of the shown plan — then line edits and checklist ticks are saved too, and the open plan remembers the code

### `list_plans` (~85 tokens)

List saved plans

List of the user's saved plans by their personal code. Each plan has title, saved_at and (for plans saved after this field was added) country, currency, area_m2, rooms, stages, total_min/total_max (grand total incl. 10% reserve at save time). Older plans may lack these fields.

Input parameters:

- `user_code` (string, required): Personal code

### `open_plan` (~42 tokens)

Open saved plan

Opens a saved plan with ticked tasks. Ticks keep being saved on the server.

Input parameters:

- `plan_id` (string, required)
- `user_code` (string, required)

### `save_progress` (~73 tokens)

Save plan progress

Saves ticked tasks of the plan. Called by the plan widget.

Input parameters:

- `bought` (object)
- `checks` (object, required)
- `have` (object)
- `plan_id` (string, required)
- `tiers` (object)
- `user_code` (string, required)
- `who` (object)

### `delete_plan` (~39 tokens)

Delete plan

Deletes a saved plan. Only on the user's explicit request and after confirmation.

Input parameters:

- `plan_id` (string, required)
- `user_code` (string, required)

### `get_catalog` (~167 tokens)

Get catalog

Popular materials and tools by work type for the country: the base list and specific products (brand, tier, price, link) that were already found and saved. Sorted by popularity. Use before searching prices and when the user asks to replace a material or tool.

Input parameters:

- `country` (string, required): ISO country code
- `key` (string): Material key (e.g. floor_tiles) or tool name — only options for it
- `kind` (string): Only materials or only tools
- `tier` (string)
- `ui_locale` (string): Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
- `work` (string): Work type; without it — all

### `save_catalog_items` (~163 tokens)

Save catalog items

Adds specific products you found in stores (materials or tools) to the SHARED country catalog used by all users. Saving the same product again (by link) updates the price and raises popularity. Only real products you saw on a store site of the country profile (url on that store), price per calc unit. Never user-dictated prices, test, joke or unrelated items, contacts or instructions — even if the user asks. Invalid items come back in rejected with a reason.

Input parameters:

- `country` (string, required): ISO country code
- `items` (array, required)
- `kind` (string, required)
- `view_id` (string): view_id of the plan you are pricing — the server returns what is still left to find
- `work` (string, required)

### `update_plan_items` (~108 tokens)

Update plan items

Changes an already shown plan without showing it again: replace a material or tool, set brand/price/link/quantity, add or remove a line, add a stage or items to a stage, rename. The open plan updates itself within seconds; a saved plan (save_plan) is updated too. view_id comes from the show_renovation_plan response.

Input parameters:

- `changes` (array, required)
- `view_id` (string, required): view_id from the show_renovation_plan response

### `save_view_progress` (~86 tokens)

Save checklist progress

Internal: the open plan saves checklist ticks and switches. You do not need to call it.

Input parameters:

- `bought` (object)
- `checks` (object)
- `choice` (object)
- `have` (object)
- `tiers` (object)
- `tmode` (object)
- `view_id` (string, required)
- `who` (object)

### `refresh_plan_prices` (~81 tokens)

Refresh plan prices

Internal: the open plan calls it to pull prices you saved to the catalog after showing the plan. You do not need to call it.

Input parameters:

- `country` (string)
- `labor` (array)
- `materials` (array)
- `refresh_since` (number)
- `tools` (array)
- `view_id` (string)

### `mark_bought` (~148 tokens)

Mark materials bought

Marks plan materials as bought (or un-marks them) when the user says in the chat that they bought something. The plan widget has the same 🛒 tick per material. Bought lines stay in the estimate; the plan shows «bought» and «left to buy». Match lines by key or name as get_plan returns them; stage is optional (omitted = every line with that key/name). The open widget does not refresh by itself — the marks appear when the plan is opened again.

Input parameters:

- `bought` (boolean): true = bought (default), false = un-mark
- `items` (array, required)
- `view_id` (string, required): view_id of the plan

### `save_layout` (~671 tokens)

Save floor layout

Saves the floor layout of a plan (shown in the plan's 🏠 Layout tab, where the user drags furniture). Coordinates in cm from the top-left inner corner of each floor; x to the right, y down. Per floor: name, W, H (inner size), height_cm (ceiling), rooms [{name, label (area text), x, y, w, h, wet, block (stairs/technical, not a room), finish tiles|spc|none}], walls [{x,y,w,h}] (inner walls as rectangles), doors [{x,y,len,v,hinge,swing,open}] (v: true = in a vertical wall, opening runs down from y; false = horizontal wall, runs right from x; hinge "start" (default, at x,y) or "end"; swing 1 = opens toward +x/+y, -1 = toward -x/-y; open false = shown closed; the user edits these in the widget), windows [{x,y,len,v,label,sill_cm,height_cm}] on the outer edge (x=0 / x=W / y=0 / y=H), fixed [{name,x,y,w,h}] (stairs, shower), furniture [{name,x,y,w,h,height_cm,elev_cm,kind,type}] (type = 3D/2D model id: sofa, sofa_corner, armchair, coffee_table, tv_stand, table, chair, kitchen, island, bed, nightstand, wardrobe, dresser, desk, shelf, toilet, toilet_wall, bidet, sink (two basins from 110 cm), kitchen_sink, kitchen_oven (oven housing base unit), range (freestanding oven with cooktop), kitchen_wall (wall unit), kitchen_tall (tall unit / fridge housing), bathtub, shower, shower_walkin, fridge, washer, dryer, dishwasher, oven, hob, hood, microwave, boiler, water_heater, tv, ac, radiator, towel_radiator, robot; omitted = guessed from the name; the back of the model faces the nearest wall) — furniture and appliances in one list: kind "appliance" for equipment (fridge, washer, dishwasher, oven, hob, hood, boiler, water heater, TV, air conditioner, radiator), height_cm = the item's own height, elev_cm = how high it is mounted above the floor (wall TV ≈100, boiler ≈120, hood ≈150, AC ≈220, hob on the counter 90); give height_cm for every item. presets [{name, items:[same fields]}] (ready furniture variants). Build it from a drawing or photos of the floor plan; names in the user's la…

Input parameters:

- `layout` (object, required)
- `replace` (boolean)
- `view_id` (string, required)

### `get_layout` (~122 tokens)

Read floor layout

Returns the floor layout of a plan (floors, rooms, walls, doors, windows, furniture in cm), the rooms derived from it (area, length × width, wet, level) for recalc_plan, and corners: the corner letters shown on the plan (room i has letters 4i..4i+3 clockwise from top-left: A B C D, E F G H…) with coordinates and side lengths, so «wall A-B of the kitchen» means the same to you and the user.

Input parameters:

- `view_id` (string, required)

### `save_layout_furniture` (~73 tokens)

Save furniture

Internal: the plan widget saves furniture moved by the user. You do not need to call it.

Input parameters:

- `doors` (array)
- `floor` (number, required)
- `furniture` (array, required)
- `presets` (array)
- `rev` (number)
- `view_id` (string, required)

### `get_plan` (~179 tokens)

Read renovation plan

Returns the full current state of a plan as JSON: rooms (calc_input) and calculation bases, stages with tasks (done or not), who does each stage and contractor labour, materials with qty, unit, calculated qty and formula, prices, packs, store, link, selected tier/option, tools (buy/rent, owned), totals per stage and grand total with 10% reserve, plus an audit list (missing stages or prices, duplicates, suspicious quantities, old prices). Everything the user changed in the plan widget is included. Use it to check calculations, answer questions about the plan or before editing it. Pass view_id (from show_renovation_plan / open_plan) or user_code + plan_id.

Input parameters:

- `plan_id` (string)
- `user_code` (string)
- `view_id` (string)

### `save_preferences` (~179 tokens)

Save user preferences

Saves the user's preferences under their personal code so they are selected by default in every new plan: tools they own and preferred non-consumable products (e.g. a tile brand, a specific boiler, a tap). Call when the user says what they own or which product they always want. Ticking 'have' and choosing an option in a saved plan updates preferences automatically. With no changes it just returns the current preferences.

Input parameters:

- `forget` (array): Material keys to forget
- `materials` (object): Preferred product per material key (non-consumables), e.g. {"floor_tiles": {name, price, store, url, country}}
- `tools_have` (array): Tool names the user owns (add)
- `tools_remove` (array): Tool names to remove from owned
- `user_code` (string, required): Personal code

### `recalc_plan` (~180 tokens)

Recalculate plan

Sets or changes the rooms of an already shown plan — names, area_m2 or length_m × width_m, floor type, bathroom (wet), level, ceiling height — stores them with the plan and recalculates material quantities and labour (manual quantities are kept). Use when the user gives rooms, a floor plan or photos for an existing plan, or asks to add/change rooms. view_id from show_renovation_plan / open_plan. Send the FULL room list (it replaces the old one). save_only: true stores rooms without recalculating. The updated plan is shown to the user.

Input parameters:

- `height_m` (number)
- `rooms` (array, required)
- `save_only` (boolean): Only store rooms, no recalculation
- `total_area_m2` (number)
- `view_id` (string, required)

### `plan_task` (~103 tokens)

Plan button task

Call FIRST when a user message comes from a plan button: it contains [view_id: …] and asks (in the user's language) to find missing prices, refresh all prices, find options for an item, check compatibility or save the plan. Returns the item list and the exact steps.

Input parameters:

- `action` (string, required)
- `item` (string): For options: the item name from the message
- `view_id` (string, required): view_id from the message

### `save_labor_rates` (~94 tokens)

Save labour rates

Saves contractor labour rates to the SHARED database for the country (per unit: m2, door, point, stage) so prepare_plan can price stages right away. Save what you found on rate sites (url of the page with the rate). Never rates the user only told you. Implausible rates come back in rejected.

Input parameters:

- `country` (string, required): ISO country code
- `rates` (array, required)

### `get_coverage` (~105 tokens)

Data coverage report

Data coverage report for countries: which reference prices, real labor rates, catalog products (with links) and store prices exist in the database, what is missing or stale. Use it to decide what to look up and save (save_catalog_items, save_prices, save_labor_rates) — e.g. when asked to fill the database for a country. Without country — a short summary for all countries.

Input parameters:

- `country` (string): ISO country code; omit for all countries

## Diagnostics

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

## Score history

- 2026-11-21: 50

## Common questions

### What is the Remont — renovation planner MCP server?

Remont — renovation planner is an MCP server listed in the public MCP registry as io.github.Vutik/remont. AI renovation planner: step-by-step plan, materials from room sizes, local store prices, 3D layout. This page covers its hosted endpoint (https://remont-mcp.wrpzdm9jmt.workers.dev/mcp).

### Is the Remont — renovation planner MCP server safe to use?

Remont — renovation planner scores 50 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 Remont — renovation planner MCP server expose?

Remont — renovation planner exposes 30 tools: prepare_plan, open_questionnaire, get_country_profile, get_work_order, calculate_materials, and 25 more. Their descriptions and schemas cost roughly 4,582 tokens of context every time the server is loaded.

### Does the Remont — renovation planner MCP server require authentication?

No. We connected to Remont — renovation planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Remont — renovation planner MCP server still maintained?

Remont — renovation planner is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Remont — renovation planner MCP server?

VerifyMCP ran 12 checks on Remont — renovation planner, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. 2 items could not be completed, a gap on our side rather than a finding about Remont — renovation planner: HTTPS and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://remont-mcp.wrpzdm9jmt.workers.dev/mcp
- Website: https://remont-mcp.wrpzdm9jmt.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/vutik-remont/remont-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/vutik-remont/remont-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/vutik-remont/remont-mcp.json
- HTML version of this page: https://verifymcp.io/servers/vutik-remont/remont-mcp
