Remote Vegas
REMOTE · REMOTE.VEGAS
Remote work spots in Las Vegas: cafés, lobbies, libraries with Wi-Fi, outlets, noise and hours.
Available components
Last scanned (1 day ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability62
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
- 4 Nov 26 70
First indexed and scored.
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 4 Nov 2026 · Probed https://remote.vegas/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=remote.vegas | CN=YR2,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | RSA 2048 | SHA256-RSA | 6a38ff20f7b5862d4c43fe9483d347f871d |
| SANs: remote.vegas | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of remote.vegas. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| vegas. | present | 13336 | 8 | Verified |
| remote.vegas. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://remote.vegas/api/mcp | Verified | 200 | |
| http (plaintext) | http://remote.vegas/api/mcp | HTTPS enforced | 308 | https://remote.vegas/api/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 →
add_media_link Link a creator post to a spot (needs agent token) ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| credit | string | – | Creator @handle |
| credit_name | string | – | Creator display name |
| slug | string | yes | Spot slug |
| url | string | yes | Public post URL |
No output schema declared.
No examples provided.
ask Ask Remote Vegas a free-form question ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| query | string | yes | The question in plain words |
| top_k | integer | – | Max results (default 5) |
No output schema declared.
No examples provided.
check_in Check in at a spot (needs agent token) ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | string | – | – |
| crowd | string | – | – |
| light | string | – | – |
| noise | string | – | – |
| note | string | – | – |
| outlets | string | – | – |
| seating | string | – | – |
| slug | string | yes | Spot slug |
| speed_mbps | number | – | Measured download speed |
| wifi | string | – | – |
| workability | integer | yes | 1 = couldn't work, 5 = perfect |
No output schema declared.
No examples provided.
get_spot Get full details for one work spot ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Spot slug from search_spots or recommend_spot, e.g. "pop-cafe" |
No output schema declared.
No examples provided.
get_zone List every spot in one zone ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 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.… |
No output schema declared.
No examples provided.
list_zones List Las Vegas zones ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional: only one kind of zone |
No output schema declared.
No examples provided.
recommend_spot Recommend where to work in Las Vegas ~279
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many picks (default 5) |
| near | string | – | Optional "lat,lng" to rank by distance |
| need | string | yes | 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.… |
No output schema declared.
No examples provided.
search_spots Search and filter Las Vegas work spots ~372
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.… |
No output schema declared.
No examples provided.
suggest_spot Suggest a missing spot (needs agent token) ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| lat | number | – | – |
| lng | number | – | – |
| name | string | yes | Place name |
| why | string | yes | Why it is good for laptop work (first-hand) |
No output schema declared.
No examples provided.
update_spot_facts Correct a spot's facts (needs agent token) ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Spot slug |
| source_url | string | – | Optional first-party source (venue site/post) |
| wifi | string | – | – |
No output schema declared.
No examples provided.
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.
remote · remote.vegas
claude mcp add --transport http vegas-remote-remote-vegas 'https://remote.vegas/api/mcp'
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.