Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Placeguide is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search verified places, menus, reviews and hours across 119 travel destinations.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user placeguide-mcp '--' npx -y @reneturcios/placeguide mcp
# 2 — ask your agent for something these tools do
# search_places, concierge_answer, list_destinations and 6 more
Placeguide costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Placeguide as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user placeguide-mcp '--' npx -y @reneturcios/placeguide mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Find real, currently-operating places in a destination — restaurants, bars, beaches, spas, viewpoints, temples. Ranked by quality (rating weighted by how many reviews stand behind it). When near is a "lat,lng" coordinate pair, results are limited to about 5 km of that point, ranked by a blend of…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Destination slug or city name, e.g. "phuket", "bangkok". |
| category | string | no | restaurant | bar | beach | spa | viewpoint | temple | waterfall | cafe (any case). Omit for all. |
| near | string | no | A "lat,lng" pair (e.g. "7.8208,98.2976") for distance-ranked results, or a neighbourhood name to filter by area, e.g. "Kata Beach". |
| query | string | no | Free text, e.g. "thai seafood", "rooftop". |
| limit | integer | no | Max results, 1–20. Default 8. |
Ask Num the way a traveller would — "where should we eat tonight near Kata?", "which beach for sunset?" — and get a short concierge answer grounded in Num's verified directory, plus the places it names as structured data so you can render your own cards. This is the whole product in one tool. It…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The traveller's question, in their own words. Any language. |
| destination | string | no | Where they are, if you know it. Improves grounding. |
| near | string | no | Neighbourhood or hotel area, if known. |
| language | string | no | BCP-47 tag for the reply, e.g. "th", "ru". Defaults to the language of the question. |
Which destinations Num covers, with the number of verified places in each. Call this FIRST when you do not know whether a city is supported — it is cheaper than a failed search and stops you promising a traveller coverage that does not exist. Coverage is honest: a destination appears here only…
No parameter schema on file.
Everything Num holds on one place, by place_id from search_places: contact details, hours, rating, review count, area, category, cuisine, the venue's own short description (about), coordinates, open_now computed in the destination's timezone (true / false / null — null means Num has not…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_id | string | yes | From search_places. |
Places that are OPEN RIGHT NOW in a destination, computed in the destination's own timezone. Businesses whose own website is a dead domain or a 404 are excluded entirely — they have closed down. IMPORTANT: only venues whose opening hours Num has verified can appear here, so a short list means thin…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Destination slug, e.g. "los-angeles". |
| category | string | no | Exact category, e.g. "Restaurant". Omit for all. |
| near | string | no | Neighbourhood, e.g. "Silver Lake". |
| bookable_only | boolean | no | Only venues Num can hand off a booking page for. |
| limit | integer | no | Max results, 1–50. Default 20. |
A booking page for one place with the party size, date and time ALREADY FILLED IN. This does NOT make a reservation and Num does not hold a table — the traveller completes it on the venue's own platform (OpenTable, Resy, Tock, SevenRooms, Square and others). The response always carries `booked:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_id | string | yes | From search_places or open_places. |
| party | integer | no | Number of covers, 1–20. |
| date | string | no | YYYY-MM-DD. |
| time | string | no | HH:MM, 24-hour, local to the venue. |
The venue's own published menu or list of offerings — dishes, treatments, tours — grouped by the venue's sections in the venue's order. Free: included in the no-fee free tier, no key needed to try it. Written by the venue itself in its Num dashboard, not scraped: prices are exactly as the venue…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_id | string | yes | From search_places, place_details or directory_feed. |
A rating SUMMARY for one place, free (included in the no-fee free tier) — no review text and no reviewer identities, ever. Returns external (the public rating and review count the listing carries, with source, the site it was read from) and num_verified: the average, count and 1–5 star…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_id | string | yes | From search_places, place_details or directory_feed. |
Bulk, paged sync of every place Num lists in one destination — free (included in the no-fee free tier; one call returns up to 200 places), for keeping your own copy of the directory current instead of searching it call by call. Ordered by place_id; pass the returned next_cursor back as cursor…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Destination slug from list_destinations, e.g. "los-angeles". |
| cursor | string | no | The next_cursor from the previous page. Omit for the first page. |
| limit | integer | no | Places per page: 1–200 with an X-Partner-Key (default 100); without a key, at most 50. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Placeguide or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Placeguide can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.