RELTO
mcp remote · streamable-http · v1.0.0 · source: crawl
https://relto.app/api/mcp
AI virtual staging that doesn't change the house.
Works
100
Verified Oct 31, 2026 · p50 684 ms · p95 705 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'relto-mcp' |
| tools_listed | 15 | pass | 3 tools |
| schema_complete | 15 | pass | 3 of 3 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 684 ms |
| latency_p95 | 5 | pass | p95 705 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (3)
| Name | Description | Schema |
|---|---|---|
stage_room | 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 aga | typed |
get_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 | typed |
get_verification | 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_s | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/app-relto-relto)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.