# RELTO (remote · relto.app)

AI virtual staging that doesn't change the house.

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

## Components

- remote · `relto.app`: 79/100 (this document), [markdown](https://verifymcp.io/servers/app-relto-relto/api-mcp.md), [page](https://verifymcp.io/servers/app-relto-relto/api-mcp)

## Channel facts

- Endpoint: `https://relto.app/api/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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 519 tokens (~173/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 RELTO MCP server?

RELTO is a hosted endpoint at https://relto.app/api/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 app-relto-relto 'https://relto.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-relto-relto": {
      "url": "https://relto.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-relto-relto": {
      "type": "http",
      "url": "https://relto.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-relto-relto]
url = "https://relto.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-relto-relto": {
      "type": "remote",
      "url": "https://relto.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-relto-relto --url 'https://relto.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-relto-relto:
    url: "https://relto.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-relto-relto": {
      "Transport": "http",
      "Url": "https://relto.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-relto-relto -t streamable-http -u 'https://relto.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-relto-relto": {
      "type": "http",
      "url": "https://relto.app/api/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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 73, +1)

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

### 2026-11-06 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `stage_room` (~241 tokens)

Stage a room photo with RELTO

Start a RELTO staging job for one empty room photo. RELTO furnishes the room and runs RELTOLock™ verification on its own output before delivering it. RELTOLock™ verifies RELTO's own staged outputs against the original photo, window by window and door by door; the verification mark is withheld if anything moved. It does not scan or verify photos staged by other tools. Returns immediately with a jobId and status "queued"; rendering takes about a minute. Then call get_staging_result with the jobId to collect the staged photo and its verification summary.

Input parameters:

- `idempotencyKey` (string): Optional key so a retried call returns the same job instead of creating a duplicate.
- `image` (string, required): The empty room photo: a base64 string, a data URL (data:image/...;base64,...), or a public https URL.
- `roomType` (string): Room type, for example "living-room" (the default), "bedroom", or "kitchen".
- `style` (string): Staging style, for example "Modern Minimalist" (the default) or "Scandinavian".

### `get_staging_result` (~146 tokens)

Get a RELTO staging result

Check a RELTO staging job by jobId and, when it is done, get the staged photo URL, the link to the original photo, and the RELTOLock™ verification summary (state, how many elements were measured, and any element lines that came back altered or inconclusive). RELTOLock™ verifies RELTO's own staged outputs against the original photo, window by window and door by door; the verification mark is withheld if anything moved. It does not scan or verify photos staged by other tools. If the job is still queued or processing, call again in a few seconds.

Input parameters:

- `jobId` (string, required): The jobId returned by stage_room.

### `get_verification` (~132 tokens)

Get the full RELTOLock™ verification evidence for a job

Fetch the full RELTOLock™ verification evidence recorded for a finished RELTO staging job: the structural checks run against the original photo and their outcomes. Use this when the summary from get_staging_result is not enough, for example to show exactly which windows and doors were measured and what each check found. RELTOLock™ verifies RELTO's own staged outputs against the original photo, window by window and door by door; the verification mark is withheld if anything moved. It does not scan or verify photos staged by other tools.

Input parameters:

- `jobId` (string, required): The jobId returned by stage_room.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-relto-relto/api-mcp#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
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67

## Common questions

### What is the RELTO MCP server?

RELTO is an MCP server listed in the public MCP registry as app.relto/relto. AI virtual staging that doesn't change the house. This page covers its hosted endpoint (https://relto.app/api/mcp).

### Is the RELTO MCP server safe to use?

RELTO 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 RELTO MCP server expose?

RELTO exposes 3 tools: stage_room, get_staging_result, get_verification. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

### Does the RELTO MCP server require authentication?

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

### Is the RELTO MCP server still maintained?

RELTO 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 RELTO MCP server?

VerifyMCP ran 12 checks on RELTO, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about RELTO: Authorization. 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://relto.app/api/mcp
- Authorisation metadata: https://relto.app/.well-known/oauth-protected-resource/api/mcp
- Website: https://relto.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-relto-relto/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-relto-relto/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-relto-relto/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-relto-relto/api-mcp
