Remote Vegas is listed as active in the registry but did not answer our last check. It exposes 10 tools.
Remote work spots in Las Vegas: cafés, lobbies, libraries with Wi-Fi, outlets, noise and hours.
Uptime history
5 days of history · worst day 0%
5 days agonow
1.1%
Uptime 24h
1 of 91 checks
10
Tools
read from the server
496 ms
Response time
average over 24h
open, no key
Access
streamable-http
Remote Vegas does not always answer
Over the last week it answered 26.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add remote-vegas --transport http https://remote.vegas/api/mcpSettings → Connectors → Add custom connector, then paste this address
https://remote.vegas/api/mcp~/.codex/config.toml
[mcp_servers.remote-vegas]
url = "https://remote.vegas/api/mcp".cursor/mcp.json
{
"mcpServers": {
"remote-vegas": {
"url": "https://remote.vegas/api/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"remote-vegas": {
"type": "http",
"url": "https://remote.vegas/api/mcp"
}
}
}Available tools 10
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
spot
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, access tips (parking, purchase rules), approved community check-ins, credited creator posts, and links to the venue, Google Maps and Yelp.
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, notes, access_tips. Trusted tokens apply immediately, others are queued; every edit is audited with before/after. Never copy facts from Yelp or Google.
ask
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…) with reasons and URLs to cite; mode "summarize" adds a one-line summary.
check
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…). Queued for human moderation before it counts. Never invent or infer values.
media
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 downloaded or rehosted) and moderated before it shows.
recommend
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 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.
spots
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, 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.
suggest
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.
zone
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.
zones
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 when the user's area is ambiguous or before passing a zone to other tools.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://remote.vegas/api/mcp | streamable-http | answering | 61 ms | 8 min ago |
Alternatives to Remote Vegas
same job, measured the same wayFTP SSH MCP
by chris221
Work with a remote host over FTP/FTPS/SFTP, SSH, and MySQL.
Jellyfin MCP
by mrfentmen
MCP server for Jellyfin: server info, users, libraries. Works with any self-hosted instance.
Emby MCP
by mrfentmen
MCP server for Emby: server info, users, libraries. Works with any instance.
Spotby Business Registry
by spotby
Find local businesses with owner-verified hours, services, prices and contacts, for AI agents.
Klarefi
by klarefi
Complete regulated intake work and retrieve cited case files without deciding the case.
Heyspark
by heyspark-mcp
Search and discover local businesses. 30+ categories with verified contact info, hours, and reviews.
Drafta
by rpegorov
Search, read and write notes in your local Drafta library over local stdio.
F
Field Notes podcast library
by abarto666
Which podcasts and talks a person appeared on, with summaries and chapters. AI, investing, crypto.
Remote Vegas — questions
Answers built from our own checks of this server.
What can Remote Vegas do?
It exposes 10 tools, read directly from the server on our last check. Among them: add_media_link, ask, check_in, get_spot, get_zone, list_zones and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Remote Vegas working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 496 ms. The bar chart above shows every period we have measured.
The registry lists Remote Vegas as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Remote Vegas?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Remote Vegas need an API key?
No. Remote Vegas completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Remote Vegas?
It answers our handshake in 496 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.