io.github.TJLDC/roomvana-mcp
REMOTE · API.ROOMVANA.CO · SCANNED SEP 27
Explore Roomvana room types and styles, then open a link to redesign a room from a photo.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 327 tokens (~109/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.TJLDC/roomvana-mcp server?
io.github.TJLDC/roomvana-mcp is a hosted endpoint at https://api.roomvana.co/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 · api.roomvana.co
claude mcp add --transport http tjldc-roomvana-mcp 'https://api.roomvana.co/mcp'
{
"mcpServers": {
"tjldc-roomvana-mcp": {
"url": "https://api.roomvana.co/mcp"
}
}
} {
"servers": {
"tjldc-roomvana-mcp": {
"type": "http",
"url": "https://api.roomvana.co/mcp"
}
}
} [mcp_servers.tjldc-roomvana-mcp] url = "https://api.roomvana.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tjldc-roomvana-mcp": {
"type": "remote",
"url": "https://api.roomvana.co/mcp",
"enabled": true
}
}
} openclaw mcp add tjldc-roomvana-mcp --url 'https://api.roomvana.co/mcp' --transport streamable-http
mcp_servers:
tjldc-roomvana-mcp:
url: "https://api.roomvana.co/mcp" {
"McpServers": {
"tjldc-roomvana-mcp": {
"Transport": "http",
"Url": "https://api.roomvana.co/mcp"
}
}
} assistant mcp add tjldc-roomvana-mcp -t streamable-http -u 'https://api.roomvana.co/mcp'
{
"mcpServers": {
"tjldc-roomvana-mcp": {
"type": "http",
"url": "https://api.roomvana.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Sept 26 +5
- HTTPS: unverified → pass ▲ security
- 25 Sept 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
- 22 Sept 26 +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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +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.
- 12 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 27 Sept 2026 · Probed https://api.roomvana.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.roomvana.co | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ae05b208869158010ea2351ae1334094 |
| SANs: api.roomvana.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.roomvana.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| roomvana.co. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.roomvana.co/mcp | Verified | 200 | |
| http (plaintext) | http://api.roomvana.co/mcp | HTTPS enforced | 301 | https://api.roomvana.co/mcp |
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 →
design_a_room ~146
Turn a room + style choice into a Roomvana studio link with those options pre-selected. The user opens the link, uploads a photo of the room, and gets an AI redesign in about 30 seconds. Validates the room and style against Roomvana's catalogue.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | – | Optional free-text notes about the desired look (echoed back; not encoded in the link). |
| room | string | yes | Room or space id, e.g. 'bedroom', 'kitchen', 'backyard'. See list_room_types. |
| style | string | – | Optional design style id, e.g. 'japandi', 'modern'. See list_design_styles. |
No output schema declared.
No examples provided.
list_design_styles ~48
List the interior-design styles Roomvana can render (e.g. modern, japandi, industrial), each with a short description. Use this to pick a `style` for design_a_room.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_room_types ~47
List the room and outdoor space types Roomvana can redesign (interior rooms, house exterior, and garden/outdoor spaces). Use this to pick a `room` for design_a_room.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.TJLDC/roomvana-mcp server?
io.github.TJLDC/roomvana-mcp is listed in the public MCP registry as io.github.TJLDC/roomvana-mcp. Explore Roomvana room types and styles, then open a link to redesign a room from a photo. This page covers its hosted endpoint (https://api.roomvana.co/mcp).
Is the io.github.TJLDC/roomvana-mcp server safe to use?
io.github.TJLDC/roomvana-mcp scores 71 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 io.github.TJLDC/roomvana-mcp server expose?
io.github.TJLDC/roomvana-mcp exposes 3 tools: list_design_styles, list_room_types, design_a_room. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Does the io.github.TJLDC/roomvana-mcp server require authentication?
No. We connected to io.github.TJLDC/roomvana-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.TJLDC/roomvana-mcp server still maintained?
io.github.TJLDC/roomvana-mcp is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.