# Remote Vegas (remote · remote.vegas)

Remote work spots in Las Vegas: cafés, lobbies, libraries with Wi-Fi, outlets, noise and hours.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `remote.vegas`: 70/100 (this document), [markdown](https://verifymcp.io/servers/vegas-remote-remote-vegas/api-mcp.md), [page](https://verifymcp.io/servers/vegas-remote-remote-vegas/api-mcp)

## Channel facts

- Endpoint: `https://remote.vegas/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1836 tokens (~131/item across 14 items; 10 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Remote Vegas MCP server?

Remote Vegas is a hosted endpoint at https://remote.vegas/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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "vegas-remote-remote-vegas": {
      "url": "https://remote.vegas/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.vegas-remote-remote-vegas]
url = "https://remote.vegas/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vegas-remote-remote-vegas": {
      "type": "remote",
      "url": "https://remote.vegas/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vegas-remote-remote-vegas --url 'https://remote.vegas/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vegas-remote-remote-vegas:
    url: "https://remote.vegas/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vegas-remote-remote-vegas": {
      "Transport": "http",
      "Url": "https://remote.vegas/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vegas-remote-remote-vegas -t streamable-http -u 'https://remote.vegas/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70)

First indexed and scored.

## MCP tools (10)

### `recommend_spot` (~279 tokens)

Recommend where to work in Las Vegas

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 Remote Vegas's hand-checked data, with a short reason for each pick. Understands quiet/focus, calls, outlets, Wi-Fi, open late/now, free, coffee vs hotel lobby vs library, and zone names written in the text. Not for places outside the Las Vegas valley.

Input parameters:

- `limit` (integer): How many picks (default 5)
- `near` (string): Optional "lat,lng" to rank by distance
- `need` (string, required): The user's need in plain words, e.g. "quiet place with outlets for 2 hours of calls near summerlin, open late"
- `open_at` (string): Optional time to be open: ISO datetime (no offset = Vegas local) or "sat 14:00"
- `zone` (string): Zone slug, name or alias: a quadrant (central, northwest, northeast, southwest, southeast), an area (e.g. the-strip, downtown, arts-district, chinatown, summerlin, henderson) or a landmark waypoint.…

### `search_spots` (~372 tokens)

Search and filter Las Vegas work 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, Wi-Fi/outlets/noise/calls, and the spot's slug and url. For "what's best for me" questions prefer recommend_spot; for one place's full details call get_spot with the slug.

Input parameters:

- `calls` (boolean): true = only call-friendly spots
- `category` (string): Coffee, Library, Hotel lobby, Lounge, Cowork, Other
- `limit` (integer): Max rows (default 10)
- `near` (string): "lat,lng" to search around
- `open_at` (string): Open at a time: ISO datetime (no offset = Vegas local) or "sat 14:00"
- `open_now` (boolean): true = only spots open right now (Las Vegas time)
- `outlets` (boolean): true = only spots with outlets
- `q` (string): Free text: name, neighborhood or vibe, e.g. "matcha", "arts district", "Pop Cafe"
- `quiet` (boolean): true = only quiet spots
- `radius_km` (number): Radius for near, km (default 5, max 50)
- `wifi` (boolean): true = only spots with good Wi-Fi
- `zone` (string): Zone slug, name or alias: a quadrant (central, northwest, northeast, southwest, southeast), an area (e.g. the-strip, downtown, arts-district, chinatown, summerlin, henderson) or a landmark waypoint.…

### `get_spot` (~116 tokens)

Get full details for one work 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, access tips (parking, purchase rules), approved community check-ins, credited creator posts, and links to the venue, Google Maps and Yelp.

Input parameters:

- `slug` (string, required): Spot slug from search_spots or recommend_spot, e.g. "pop-cafe"

### `list_zones` (~90 tokens)

List Las Vegas 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 when the user's area is ambiguous or before passing a zone to other tools.

Input parameters:

- `kind` (string): Optional: only one kind of zone

### `get_zone` (~109 tokens)

List every spot in one 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.

Input parameters:

- `slug` (string, required): Zone slug, name or alias: a quadrant (central, northwest, northeast, southwest, southeast), an area (e.g. the-strip, downtown, arts-district, chinatown, summerlin, henderson) or a landmark waypoint.…

### `ask` (~112 tokens)

Ask Remote Vegas a free-form question

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…) with reasons and URLs to cite; mode "summarize" adds a one-line summary.

Input parameters:

- `mode` (string)
- `query` (string, required): The question in plain words
- `top_k` (integer): Max results (default 5)

### `check_in` (~171 tokens)

Check in at a spot (needs agent token)

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…). Queued for human moderation before it counts. Never invent or infer values.

Input parameters:

- `calls` (string)
- `crowd` (string)
- `light` (string)
- `noise` (string)
- `note` (string)
- `outlets` (string)
- `seating` (string)
- `slug` (string, required): Spot slug
- `speed_mbps` (number): Measured download speed
- `wifi` (string)
- `workability` (integer, required): 1 = couldn't work, 5 = perfect

### `suggest_spot` (~94 tokens)

Suggest a missing spot (needs agent token)

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.

Input parameters:

- `address` (string)
- `lat` (number)
- `lng` (number)
- `name` (string, required): Place name
- `why` (string, required): Why it is good for laptop work (first-hand)

### `add_media_link` (~112 tokens)

Link a creator post to a spot (needs agent token)

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 downloaded or rehosted) and moderated before it shows.

Input parameters:

- `credit` (string): Creator @handle
- `credit_name` (string): Creator display name
- `slug` (string, required): Spot slug
- `url` (string, required): Public post URL

### `update_spot_facts` (~215 tokens)

Correct a spot's facts (needs agent token)

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, notes, access_tips. Trusted tokens apply immediately, others are queued; every edit is audited with before/after. Never copy facts from Yelp or Google.

Input parameters:

- `access_tips` (string)
- `best_time` (string)
- `calls` (string)
- `hours` (string)
- `noise` (string)
- `notes` (string)
- `outlets` (string)
- `reason` (string): What was observed, and when
- `slug` (string, required): Spot slug
- `source_url` (string): Optional first-party source (venue site/post)
- `wifi` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vegas-remote-remote-vegas/api-mcp#diagnostics

## Score history

- 2026-11-04: 70

## Common questions

### What is the Remote Vegas MCP server?

Remote Vegas is an MCP server listed in the public MCP registry as vegas.remote/remote-vegas. Remote work spots in Las Vegas: cafés, lobbies, libraries with Wi-Fi, outlets, noise and hours. This page covers its hosted endpoint (https://remote.vegas/api/mcp).

### Is the Remote Vegas MCP server safe to use?

Remote Vegas scores 70 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 Remote Vegas MCP server expose?

Remote Vegas exposes 10 tools: recommend_spot, search_spots, get_spot, list_zones, get_zone, and 5 more. Their descriptions and schemas cost roughly 1,670 tokens of context every time the server is loaded.

### Does the Remote Vegas MCP server require authentication?

No. We connected to Remote Vegas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Remote Vegas MCP server still maintained?

Remote Vegas is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://remote.vegas/api/mcp
- Website: https://remote.vegas/data
- Changelog RSS feed: https://verifymcp.io/servers/vegas-remote-remote-vegas/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/vegas-remote-remote-vegas/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/vegas-remote-remote-vegas/api-mcp