_ registry / mcp streamable-http · checked 19m ago

roomvana

https://api.roomvana.co

Registry code: d0cad38abfee85cd

api record

Roomvana is an AI home design tool: upload a photo of a house, yard or room and see it redesigned at https://roomvana.ai. Use list_room_types and list_design_styles to see what is supported, then design_a_room to hand the user a studio link with their room and style pre-selected. This server is read-only; the redesign itself happens on the website, behind sign-in.

endpoint
https://api.roomvana.co/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is roomvana live?
Yes — it answered the hub's last check (checked 19m ago). It answered 99% of checks over the last 30 days.
Is roomvana free to use?
Yes — the hub reached it with no key and no payment.
What tools does roomvana have?
3 tools: list_design_styles, design_a_room, list_room_types.
Is roomvana safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.4%· all time 99.4%

latency
233ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 313 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
lifestyle & home home & family
used for
  • get a link to redesign a room photo
  • list interior design styles
  • list room types
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_room_types reads open 8h ago

    List the room and outdoor space types Roomvana can redesign (interior rooms, house exterior, and garden/outdoor spaces).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_design_styles reads unknown never probed

    List the design styles Roomvana can render (e.g. modern, japandi, industrial), each with a short description.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • design_a_room reads unknown never probed

    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. Validates the room and style against Roomvana's catalogue.

    mcp-tool

    {
  "type": "object",
  "required": [
    "room"
  ],
  "properties": {
    "room": {
      "type": "string",
      "description": "Room or space id, e.g. 'bedroom', 'kitchen', 'backyard'."
    },
    "notes": {
      "type": "string",
      "description": "Optional free-text notes about the desired look (echoed back; not encoded in the link)."
    },
    "style": {
      "type": "string",
      "description": "Optional design style id, e.g. 'japandi', 'modern'."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d0cad38abfee85cd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d0cad38abfee85cd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d0cad38abfee85cd/badge.svg)](https://brick.blue/agent/d0cad38abfee85cd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.