Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

50 Trust /100

Last scanned (2 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability31
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 44% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass

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.

What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 50

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://remont-mcp.wrpzdm9jmt.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wrpzdm9jmt.workers.dev CN=YE2,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 5af51726a842986482360b07a868a3ccf45
SANs: *.wrpzdm9jmt.workers.dev, wrpzdm9jmt.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of remont-mcp.wrpzdm9jmt.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://remont-mcp.wrpzdm9jmt.workers.dev/mcp Verified 200
http (plaintext) http://remont-mcp.wrpzdm9jmt.workers.dev/mcp Inconclusive 405
MCP tools · 30 exposed · ~4,582 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
calculate_materials ~300

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

NameTypeReqDescription
attic_m2number–House: attic roof area to insulate, m²
boilerstring–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…
countrystringyesISO country code
distribution_boardboolean–A new consumer unit is needed
doorsinteger––
facade_m2number–House: facade area without windows, m²
kitchen_mnumber–Kitchen length, running m (default 3.5)
modestringyesdiy — do it yourself, pro — contractor
new_pointsinteger–New sockets and switches
propertystring––
roomsarrayyes–
stairsobject––
total_area_m2number––
ui_localestring–Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
windowsinteger–Windows, pcs (for window sills)
worksarrayyes–

No output schema declared.

No examples provided.

delete_plan ~39

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

NameTypeReqDescription
plan_idstringyes–
user_codestringyes–

No output schema declared.

No examples provided.

find_cached_prices ~62

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.

NameTypeReqDescription
citystring––
countrystringyes–
keysarrayyes–

No output schema declared.

No examples provided.

get_catalog ~167

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.

NameTypeReqDescription
countrystringyesISO country code
keystring–Material key (e.g. floor_tiles) or tool name — only options for it
kindstring–Only materials or only tools
tierstring––
ui_localestring–Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
workstring–Work type; without it — all

No output schema declared.

No examples provided.

get_country_profile ~45

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

NameTypeReqDescription
countrystringyesISO country code, e.g. PL, DE

No output schema declared.

No examples provided.

get_coverage ~105

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.

NameTypeReqDescription
countrystring–ISO country code; omit for all countries

No output schema declared.

No examples provided.

get_layout ~122

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.

NameTypeReqDescription
view_idstringyes–

No output schema declared.

No examples provided.

get_plan ~179

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.

NameTypeReqDescription
plan_idstring––
user_codestring––
view_idstring––

No output schema declared.

No examples provided.

get_ui_labels ~55

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

NameTypeReqDescription
localestring–Language code you translate into (e.g. lt, fr, ja) — for statistics

No output schema declared.

No examples provided.

get_work_order ~79

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

NameTypeReqDescription
ui_localestring–Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
worksarrayyesWhich works the renovation includes

No output schema declared.

No examples provided.

list_plans ~85

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.

NameTypeReqDescription
user_codestringyesPersonal code

No output schema declared.

No examples provided.

mark_bought ~148

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.

NameTypeReqDescription
boughtboolean–true = bought (default), false = un-mark
itemsarrayyes–
view_idstringyesview_id of the plan

No output schema declared.

No examples provided.

open_plan ~42

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

NameTypeReqDescription
plan_idstringyes–
user_codestringyes–

No output schema declared.

No examples provided.

open_questionnaire ~194

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.

NameTypeReqDescription
citystring––
countrystring–Country code, if known
floorsinteger––
height_mnumber––
labelsobject–Widget text translations for languages without a built-in translation (built in: ru, pl, en, de, uk). Keys come from get_ui_labels.
localestring–Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
propertystring––
roomsarray–Rooms recognised from the user's floor plan or photos
total_area_m2number––

No output schema declared.

No examples provided.

plan_task ~103

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.

NameTypeReqDescription
actionstringyes–
itemstring–For options: the item name from the message
view_idstringyesview_id from the message

No output schema declared.

No examples provided.

prepare_plan ~391

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.

NameTypeReqDescription
attic_m2number––
boilerstring–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…
citystring––
countrystringyesISO country code
distribution_boardboolean–A new consumer unit is needed
doorsinteger––
facade_m2number––
floorsinteger––
height_mnumber–Ceiling height, m (default for rooms)
kitchen_mnumber–Kitchen length, running m (default 3.5)
modestring––
new_pointsinteger––
propertystring––
roomsarray––
stairsobject––
tierstring–Default tier
total_area_m2number––
ui_localestring–Language of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
user_codestring–User's personal code, if known — applies their saved preferences (owned tools, preferred products) by default
windowsinteger–Windows, pcs (for window sills)
worksarrayyes–

No output schema declared.

No examples provided.

recalc_plan ~180

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.

NameTypeReqDescription
height_mnumber––
roomsarrayyes–
save_onlyboolean–Only store rooms, no recalculation
total_area_m2number––
view_idstringyes–

No output schema declared.

No examples provided.

refresh_plan_prices ~81

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.

NameTypeReqDescription
countrystring––
laborarray––
materialsarray––
refresh_sincenumber––
toolsarray––
view_idstring––

No output schema declared.

No examples provided.

save_catalog_items ~163

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.

NameTypeReqDescription
countrystringyesISO country code
itemsarrayyes–
kindstringyes–
view_idstring–view_id of the plan you are pricing — the server returns what is still left to find
workstringyes–

No output schema declared.

No examples provided.

save_country_profile ~151

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.

NameTypeReqDescription
codestringyesISO country code
currencystring–ISO currency code
laborSourcesarray–Sites with contractor rates
localestring–Search language in stores
namestring––
notesarray––
specialistRulesarray––
storesarray–DIY/building stores with prices on their site

No output schema declared.

No examples provided.

save_labor_rates ~94

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.

NameTypeReqDescription
countrystringyesISO country code
ratesarrayyes–

No output schema declared.

No examples provided.

save_layout ~671

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…

NameTypeReqDescription
layoutobjectyes–
replaceboolean––
view_idstringyes–

No output schema declared.

No examples provided.

save_layout_furniture ~73

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

NameTypeReqDescription
doorsarray––
floornumberyes–
furniturearrayyes–
presetsarray––
revnumber––
view_idstringyes–

No output schema declared.

No examples provided.

save_plan ~184

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.

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

No output schema declared.

No examples provided.

save_preferences ~179

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.

NameTypeReqDescription
forgetarray–Material keys to forget
materialsobject–Preferred product per material key (non-consumables), e.g. {"floor_tiles": {name, price, store, url, country}}
tools_havearray–Tool names the user owns (add)
tools_removearray–Tool names to remove from owned
user_codestringyesPersonal code

No output schema declared.

No examples provided.

save_prices ~96

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.

NameTypeReqDescription
citystring––
countrystringyes–
pricesarrayyes–

No output schema declared.

No examples provided.

save_progress ~73

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

NameTypeReqDescription
boughtobject––
checksobjectyes–
haveobject––
plan_idstringyes–
tiersobject––
user_codestringyes–
whoobject––

No output schema declared.

No examples provided.

save_view_progress ~86

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

NameTypeReqDescription
boughtobject––
checksobject––
choiceobject––
haveobject––
tiersobject––
tmodeobject––
view_idstringyes–
whoobject––

No output schema declared.

No examples provided.

show_renovation_plan ~327

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

NameTypeReqDescription
calc_inputobject–calc_input from prepare_plan, unchanged — REQUIRED for the rooms editor: rooms, sizes and ceiling height are stored with the plan
countrystring–ISO country code — needed so the plan can fill in prices itself
currencystringyesISO currency code, e.g. PLN
default_tierstring–Tier selected by default for all stages
labelsobject–Widget text translations for languages without a built-in translation (built in: ru, pl, en, de, uk). Keys come from get_ui_labels.
localestringyesLanguage of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.
materialsarrayyes–
modestring–Who does the work
notesarray––
prices_checked_atstring––
roomsarray–Rooms (name, area_m2, length_m, width_m, floor, wet) if you have no calc_input
stagesarrayyes–
titlestringyes–
toolsarray–Tools for DIY work, by stage
user_codestring–User's personal code, if known — applies saved preferences by default
view_idstring–Only if you re-show the same plan

No output schema declared.

No examples provided.

update_plan_items ~108

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.

NameTypeReqDescription
changesarrayyes–
view_idstringyesview_id from the show_renovation_plan response

No output schema declared.

No examples provided.

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.

remote · remont-mcp.wrpzdm9jmt.workers.dev

# add to Claude Code
claude mcp add --transport http vutik-remont 'https://remont-mcp.wrpzdm9jmt.workers.dev/mcp'
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.