# LEVA building cost estimates (remote · leva-seo-worker.long-cloud-d006.workers.dev)

Cost of an ADU, shed, barndominium and more from LEVA priced 3D configurators

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

## Components

- remote · `leva-seo-worker.long-cloud-d006.workers.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/levabythe-leva/leva-seo-worker.md), [page](https://verifymcp.io/servers/levabythe-leva/leva-seo-worker)

## Channel facts

- Endpoint: `https://leva-seo-worker.long-cloud-d006.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.10.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**: 63/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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 945 tokens (~105/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 9 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the LEVA building cost estimates MCP server?

LEVA building cost estimates is a hosted endpoint at https://leva-seo-worker.long-cloud-d006.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 levabythe-leva 'https://leva-seo-worker.long-cloud-d006.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "levabythe-leva": {
      "url": "https://leva-seo-worker.long-cloud-d006.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "levabythe-leva": {
      "type": "http",
      "url": "https://leva-seo-worker.long-cloud-d006.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.levabythe-leva]
url = "https://leva-seo-worker.long-cloud-d006.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "levabythe-leva": {
      "type": "remote",
      "url": "https://leva-seo-worker.long-cloud-d006.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add levabythe-leva --url 'https://leva-seo-worker.long-cloud-d006.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  levabythe-leva:
    url: "https://leva-seo-worker.long-cloud-d006.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "levabythe-leva": {
      "Transport": "http",
      "Url": "https://leva-seo-worker.long-cloud-d006.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add levabythe-leva -t streamable-http -u 'https://leva-seo-worker.long-cloud-d006.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "levabythe-leva": {
      "type": "http",
      "url": "https://leva-seo-worker.long-cloud-d006.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-20 (score 69, +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-18 (score 68, +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-15 (score 67, +1)

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

### 2026-11-14 (score 66, +7)

- [security improvement] Authorization: unverified → partial

### 2026-11-13 (score 59, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 58)

First indexed and scored.

## MCP tools (9)

### `estimate_build` (~257 tokens)

Estimate a building of a given size

What a LEVA building of a given size costs to build: total, materials, labour (execution) and hours in USD with a low-high range, from LEVA's priced reference designs of that product, plus the nearest reference design and a link that opens LEVA's 3D configurator at exactly that size with an itemized bill of materials. Use it for questions like 'how much does a 20 x 30 ft ADU / 12 x 16 shed / barndominium cost to build'. Estimates, not quotes.

Input parameters:

- `area` (number): instead of width and length: the floor area (sq ft, or m2 with unit m)
- `length` (number): footprint length
- `market` (string): optional two-letter country code for local material prices, e.g. DE, GB, CA
- `product` (string, required): the product handle from list_products, e.g. adu, barndominium, shed, sauna-1
- `roof` (string): optional roof shape: gable, hip, halfhip, mono, flat
- `unit` (string): unit of width / length / area (default ft)
- `width` (number): footprint width

### `list_products` (~50 tokens)

LEVA configurable products

List LEVA's configurable building products (A-frame, ADU, shed, sauna, barndominium ...) with their configurator type, the number of priced reference designs and whether their options are described.

### `get_product` (~86 tokens)

One LEVA product

One LEVA product by its handle (e.g. a-frames, adu): description, plan price, configuration options (sizes, roof, foundation ...) and LEVA's reference designs with their itemized budgets (materials, execution/labour, hours, $/sq ft; USD estimates, not quotes).

Input parameters:

- `handle` (string, required): the product handle, from list_products

### `get_project` (~89 tokens)

One public LEVA project

One public LEVA project by the id from its link (?p=<id>): a LEVA reference design or a budget its author made public -- plan size, rooms, roof, place, and the budget (total, materials, execution, hours; USD estimates, not quotes).

Input parameters:

- `id` (string, required): the ?p= id of a project link, 6-12 lowercase letters / digits

### `get_product_prices` (~91 tokens)

A LEVA product's material prices over time

What the materials of a LEVA product's reference design (or default design) cost at the cheapest store offers, day by day, in 19 countries (local currency and USD), with coverage and the change over time. Materials only; estimates, not quotes.

Input parameters:

- `handle` (string, required): the product handle, from list_products (e.g. adu, barndominium, sauna-1)

### `get_project_prices` (~67 tokens)

A LEVA reference design's material prices over time

One LEVA reference design's own bill of quantities priced at the cheapest store offers, day by day, in every country (USD), with coverage. Materials only; estimates, not quotes.

Input parameters:

- `id` (string, required): the ?p= id of a reference design (see get_product)

### `search_items` (~88 tokens)

Search LEVA's material catalogue

Find items of LEVA's material catalogue (doors, windows, lumber, insulation, fasteners, membranes ...) by words, e.g. 'interior door', 'exterior door 36', 'window'. Gives ids for get_item_prices.

Input parameters:

- `limit` (number): at most this many (1-50, default 20)
- `q` (string, required): words to look for

### `get_item_prices` (~79 tokens)

One catalogue item's cheapest price over time

The cheapest offer found for one LEVA catalogue item, per unit, in each country's currency and USD, over time; checked against LEVA's own price and the other countries (pack prices replaced).

Input parameters:

- `id` (string, required): the item id from search_items
- `market` (string): optional two-letter country code, e.g. US

### `get_latest_project` (~55 tokens)

The newest public LEVA project of a user

The newest public project a LEVA user shared (not a LEVA reference design): product, author, place, size and the budget (total, materials, execution, hours; USD estimates, not quotes), with its link.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/levabythe-leva/leva-seo-worker#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 67
- 2026-11-14: 66
- 2026-11-13: 59
- 2026-11-12: 58

## Common questions

### What is the LEVA building cost estimates MCP server?

LEVA building cost estimates is an MCP server listed in the public MCP registry as io.github.LevaByThe/leva. Cost of an ADU, shed, barndominium and more from LEVA priced 3D configurators. This page covers its hosted endpoint (https://leva-seo-worker.long-cloud-d006.workers.dev/mcp).

### Is the LEVA building cost estimates MCP server safe to use?

LEVA building cost estimates scores 69 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 LEVA building cost estimates MCP server expose?

LEVA building cost estimates exposes 9 tools: estimate_build, list_products, get_product, get_project, get_product_prices, and 4 more. Their descriptions and schemas cost roughly 862 tokens of context every time the server is loaded.

### Does the LEVA building cost estimates MCP server require authentication?

No. We connected to LEVA building cost estimates without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LEVA building cost estimates MCP server still maintained?

LEVA building cost estimates 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 LEVA building cost estimates MCP server?

VerifyMCP ran 13 checks on LEVA building cost estimates, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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://leva-seo-worker.long-cloud-d006.workers.dev/mcp
- Website: https://www.theleva.com/
- Changelog RSS feed: https://verifymcp.io/servers/levabythe-leva/leva-seo-worker.xml
- Changelog JSON feed: https://verifymcp.io/servers/levabythe-leva/leva-seo-worker/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/levabythe-leva/leva-seo-worker.json
- HTML version of this page: https://verifymcp.io/servers/levabythe-leva/leva-seo-worker
