# Zovo Floor Plan (remote · floor-plan.zovo.one)

Turns room sizes into a floor plan drawn to scale, with the area of each room and the total area.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `floor-plan.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-floor-plan/floor-plan.md), [page](https://verifymcp.io/servers/theluckystrike-floor-plan/floor-plan)

## Channel facts

- Endpoint: `https://floor-plan.zovo.one/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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 71/100
  - 100% 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 1105 tokens (~368/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Floor Plan MCP server?

Zovo Floor Plan is a hosted endpoint at https://floor-plan.zovo.one/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 theluckystrike-floor-plan 'https://floor-plan.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-floor-plan": {
      "url": "https://floor-plan.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-floor-plan": {
      "type": "http",
      "url": "https://floor-plan.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-floor-plan]
url = "https://floor-plan.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-floor-plan": {
      "type": "remote",
      "url": "https://floor-plan.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-floor-plan --url 'https://floor-plan.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-floor-plan:
    url: "https://floor-plan.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-floor-plan": {
      "Transport": "http",
      "Url": "https://floor-plan.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-floor-plan -t streamable-http -u 'https://floor-plan.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-floor-plan": {
      "type": "http",
      "url": "https://floor-plan.zovo.one/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 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (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-11-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (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-11-09 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 73)

First indexed and scored.

## MCP tools (2)

### `make_floor_plan` (~580 tokens)

Make floor plan

Use this when the user wants a floor plan, room layout or apartment plan drawn to scale from room sizes, for example "draw a floor plan: living 5x4 m, kitchen 3x4 m next to it" or "plan of my house in feet". Takes rooms as rectangles (width east-west, length north-south) in metres or feet and inches, placed by x/y or right_of/below/left_of/above another room, plus optional doors and windows by wall and offset, a scale (auto, 1:50, 1:100, 1/4in=1ft) and a page size. Returns each room area, the total area, an interactive plan, and SVG, PDF and CSV downloads. Refuses overlapping rooms and openings past a wall end, naming them. Does not draw curved walls, stairs, furniture or wall thickness, and does not read images or files.

Input parameters:

- `doors` (array): Doors, up to 60, e.g. [{"room":"Living","wall":"south","offset":1,"width":0.9}]. Drawn as a gap with a swing arc.
- `north_arrow` (boolean): Draw a north arrow pointing up (default true).
- `page_size` (string): PDF and SVG paper: auto (default: A4 for metres, Letter for feet), a4, a3, letter or tabloid. Orientation is chosen to fit.
- `rooms` (array, required): Rooms as rectangles, up to 40. A room with no position goes to the right of the previous room. Example: [{"name":"Living","width":5,"length":4},{"name":"Kitchen","width":3,"length":4,"right_of":"Livi…
- `scale` (string): auto (default: the largest standard scale that fits one page), a ratio like "1:50" or "1:100", or an architect scale like "1/4in=1ft" or "1/8in=1ft".
- `title` (string): Plan title, e.g. "Ground floor". Up to 80 characters.
- `units` (string): Unit for plain numbers. m (default), cm or mm: a metric plan, sizes like 3.5, "350 cm" or "3500 mm"; ft or in: a feet-and-inches plan, sizes like 12'6", "12 ft 6 in", "12.5 ft" or "150 in". With cm,…
- `windows` (array): Windows, up to 60, e.g. [{"room":"Kitchen","wall":"east","offset":1,"width":1.2}].

Output parameters:

- `area_unit` (string)
- `checks` (object)
- `doors` (number)
- `downloads` (object)
- `label_check` (object)
- `page` (object)
- `plan_size` (object)
- `preview_count` (object)
- `room_count` (number)
- `rooms` (array)
- `scale` (string)
- `scale_check` (object)
- `title` (string)
- `total_area` (number)
- `total_area_text` (string)
- `units` (string)
- `warnings` (array)
- `windows` (number)

### `check_floor_plan` (~402 tokens)

Check floor plan

Use this when the user wants to check a room layout before drawing it, or asks why a floor plan was refused, for example "do these rooms overlap?" or "what is the total area of these rooms?". Takes the same rooms, doors and windows as make_floor_plan. Returns the area table, the sum of room areas, the floor area actually covered, and a list of problems: overlapping rooms with the overlap area, doors or windows that run past a wall end, L-shaped parts that overlap or do not touch, and rooms that do not touch the rest. Does not draw the plan and does not check building codes.

Input parameters:

- `doors` (array): Doors, up to 60, e.g. [{"room":"Living","wall":"south","offset":1,"width":0.9}]. Drawn as a gap with a swing arc.
- `rooms` (array, required): Rooms as rectangles, up to 40. A room with no position goes to the right of the previous room. Example: [{"name":"Living","width":5,"length":4},{"name":"Kitchen","width":3,"length":4,"right_of":"Livi…
- `title` (string): Plan title, e.g. "Ground floor". Up to 80 characters.
- `units` (string): Unit for plain numbers. m (default), cm or mm: a metric plan, sizes like 3.5, "350 cm" or "3500 mm"; ft or in: a feet-and-inches plan, sizes like 12'6", "12 ft 6 in", "12.5 ft" or "150 in". With cm,…
- `windows` (array): Windows, up to 60, e.g. [{"room":"Kitchen","wall":"east","offset":1,"width":1.2}].

Output parameters:

- `area_unit` (string)
- `checks_run` (array)
- `counted_twice` (number)
- `covered_area` (number)
- `plan_size` (object)
- `preview_count` (object)
- `problem_count` (number)
- `problems` (array)
- `room_count` (number)
- `rooms` (array)
- `sum_of_room_areas` (number)
- `title` (string)
- `units` (string)
- `warnings` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73

## Common questions

### What is the Zovo Floor Plan MCP server?

Zovo Floor Plan is an MCP server listed in the public MCP registry as io.github.theluckystrike/floor-plan. Turns room sizes into a floor plan drawn to scale, with the area of each room and the total area. This page covers its hosted endpoint (https://floor-plan.zovo.one/mcp).

### Is the Zovo Floor Plan MCP server safe to use?

Zovo Floor Plan scores 79 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 Zovo Floor Plan MCP server expose?

Zovo Floor Plan exposes 2 tools: make_floor_plan, check_floor_plan. Their descriptions and schemas cost roughly 982 tokens of context every time the server is loaded.

### Does the Zovo Floor Plan MCP server require authentication?

No. We connected to Zovo Floor Plan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Floor Plan MCP server still maintained?

Zovo Floor Plan 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 Zovo Floor Plan MCP server?

VerifyMCP ran 14 checks on Zovo Floor Plan, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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://floor-plan.zovo.one/mcp
- Website: https://floor-plan.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-floor-plan/floor-plan.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-floor-plan/floor-plan/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-floor-plan/floor-plan.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-floor-plan/floor-plan
