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.

RELTO

REMOTE · RELTO.APP

AI virtual staging that doesn't change the house.

Available components

+3 this week 79 Trust /100

Last scanned (18 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

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 Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

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.

  • Authorization in Endpoint SecurityAuthorisation 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.

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 +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.

  • 19 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 26 +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.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://relto.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.relto.app CN=YR2,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 RSA 2048 SHA256-RSA 53650a4518256a7240a585ba326f677522e
SANs: *.relto.app, relto.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of relto.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
relto.app. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'nonce-jAecLm/Nxv36abfFDfK6bg==' 'strict-dynamic' 'self' 'sha256-McXgDCAacxLIJl6Ixb9jK8UAHXyMsT4MHubO+Jmu1Io=' https://vercel.live https://js.stripe.com https://pusher.com https://connect.facebook.net https://www.googletagmanager.com https://cloud.umami.is https://r2.leadsy.ai https://www.clarity.ms; style-src 'self' 'unsafe-inline'; img-src 'self' data: https: blob: https://blob.vercel-storage.com https://www.facebook.com; font-src 'self' data:; connect-src 'self' https://*.supabase.co https://*.supabase.in https://vercel.live wss://*.supabase.co wss://*.pusher.com https://*.pusher.com https://*.public.blob.vercel-storage.com https://blob.vercel-storage.com https://vercel.com wss://ws-us3.pusher.com https://pusher.com https://www.facebook.com https://*.facebook.com https://www.googletagmanager.com https://www.google-analytics.com https://google-analytics.com https://stats.g.doubleclick.net https://cloud.umami.is https://r2.leadsy.ai https://*.leadsy.ai https://*.clarity.ms http
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self)

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://relto.app/api/mcp Verified 200
http (plaintext) http://relto.app/api/mcp HTTPS enforced 308 https://relto.app/api/mcp
MCP tools · 3 exposed · ~519 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
get_staging_result ~146

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.

NameTypeReqDescription
jobIdstringyesThe jobId returned by stage_room.

No output schema declared.

No examples provided.

get_verification ~132

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.

NameTypeReqDescription
jobIdstringyesThe jobId returned by stage_room.

No output schema declared.

No examples provided.

stage_room ~241

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.

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

No output schema declared.

No examples provided.

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.

remote · relto.app

# add to Claude Code
claude mcp add --transport http app-relto-relto 'https://relto.app/api/mcp'
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.