Skip to content

Remote Vegas MCP server

Which MCP servers are Remote Vegas's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-04

← Back to Remote Vegas

Whose server it is
  • Registry namevegas.remote/remote-vegasverified in the MCP registry

The registry name sits under remote.vegas. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-04
  • Stateanswerschecked 2026-11-04
  • Tools10
  • Server calls itselfremote-vegas
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-11-04 the server answered initialize and tools/list without a sign-in. First answer in 144 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • add_media_link, update_spot_facts change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 4 of 10 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-11-04
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer324 ms
  • Space in an agent's context≈ 2,228 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 93 of 100
  • Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 10

Worth a look

  • Tools that change data, on a server that answers without a sign-in: add_media_link, update_spot_facts

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-11-04
  • recommend_spot

    Use this FIRST when the user asks where to work, study or take calls in Las Vegas/Henderson/Summerlin (e.g. "quiet café with outlets near the Strip, open late"). Returns the top spots for that need, ranked by a deterministic score over…

  • search_spots

    Use this to list or filter Las Vegas work spots by explicit criteria (zone, category, Wi-Fi, outlets, quiet, calls, open now / at a time, near a point) or by name/keyword. Returns compact rows: name, category, area, hours…

  • get_spot

    Use this after search_spots/recommend_spot (or when the user names a specific place) to get everything about ONE spot by slug: address, structured opening hours, Wi-Fi/outlets/noise/calls with the evidence behind each, best time to go…

  • list_zones

    Use this to learn which zone names/slugs exist (quadrants, named areas such as the Strip, Downtown, Arts District, Chinatown, Summerlin, Henderson, and landmark waypoints like UNLV or the airport), with aliases and spot counts. Call it…

  • get_zone

    Use this when the user wants ALL the work spots in one area (e.g. "everything in the Arts District"). Returns the zone and a compact list of its spots with slugs and urls.

  • ask

    NLWeb-style natural-language query over Remote Vegas. Use it for open questions that don't map cleanly to filters (e.g. "somewhere with a view to work on a Sunday morning"). Returns schema.org places (CafeOrCoffeeShop, Library, Hotel…)…

  • check_in

    Partner agents only: needs a Remote Vegas agent token in the HTTP Authorization header; without one it returns an error. Use only to report conditions the user observed IN PERSON at a spot today (workability 1-5, Wi-Fi, outlets, noise…)…

  • suggest_spot

    Partner agents only (agent token required). Use when the user names a Las Vegas place that is good for laptop work and search_spots does not find it. A human reviews every suggestion.

  • add_media_link

    Partner agents only (agent token required). Attach a PUBLIC Instagram post/reel, TikTok, YouTube video/Short, X or Threads post that shows a spot's work area, credited to its creator. Stored as the platform's official embed (never…

  • update_spot_facts

    Partner agents only (agent token required). Correct first-hand facts for one spot: hours (e.g. "Mon–Fri 6am–5pm; Sat–Sun 8am–4pm"), wifi yes|spotty|no, outlets yes|limited|no, noise quiet|mixed|loud, calls yes|limited|no, best_time…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "remote-vegas": {
      "type": "http",
      "url": "https://remote.vegas/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http remote https://remote.vegas/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://remote.vegas/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.