Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/placeguide

NPM · @RENETURCIOS/PLACEGUIDE · 2 COMPONENTS

Search verified places, menus, reviews and hours across 119 travel destinations.

+3 this week 74 Trust /100

Last scanned (21 hours ago)

Scores higher than 49% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1836 tokens (~204/item across 9 items; 9 tools + 0 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +2
    • Stability: unverified → 0.13 ▲ functional
  • 10 Nov 26 69

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@reneturcios/placeguide@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,836 tokens

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 →

Tool Tokens
booking_link ~195

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: false` and `mode: "deeplink"`. You MUST NOT render this as a confirmation, and you MUST NOT tell a traveller a table is held. If the venue has no booking platform the response says so and returns the phone number instead — offer that rather than implying it cannot be visited.

NameTypeReqDescription
datestring–YYYY-MM-DD.
partyinteger–Number of covers, 1–20.
place_idstringyesFrom search_places or open_places.
timestring–HH:MM, 24-hour, local to the venue.

No output schema declared.

No examples provided.

concierge_answer ~206

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 answers about the place asked and NEVER substitutes a different city. If Num has no coverage there it says so rather than guessing. It does not book, charge, or take personal details — send none. You MUST display the returned `attribution`.

NameTypeReqDescription
destinationstring–Where they are, if you know it. Improves grounding.
languagestring–BCP-47 tag for the reply, e.g. "th", "ru". Defaults to the language of the question.
nearstring–Neighbourhood or hotel area, if known.
questionstringyesThe traveller's question, in their own words. Any language.

No output schema declared.

No examples provided.

directory_feed ~235

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` until it is null. Each item has the search_places fields plus cuisine, lat, lng and booking_platform. Places Num has positive evidence have closed are excluded; `trading: null` means not yet checked, NOT closed. Contains no menus, reviews or photos — call get_menu, get_reviews or place_details for those. You MUST display the returned `attribution` wherever the data is shown.

NameTypeReqDescription
cursorstring–The `next_cursor` from the previous page. Omit for the first page.
destinationstringyesDestination slug from list_destinations, e.g. "los-angeles".
limitinteger–Places per page: 1–200 with an X-Partner-Key (default 100); without a key, at most 50.

No output schema declared.

No examples provided.

get_menu ~214

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 set them, in its own currency, each with the formatted amount, the currency code and the integer minor units. A price is what the venue says it charges, NOT a quote — never tell a traveller their bill will be that figure. An item with no price has `price: null` (or only a note such as "market price"); do not estimate one. If the venue has not published a menu, `sections` is empty and `note` says so — say that, never invent dishes. Age-restricted items are never shown on this surface. You MUST display the returned `attribution`.

NameTypeReqDescription
place_idstringyesFrom search_places, place_details or directory_feed.

No output schema declared.

No examples provided.

get_reviews ~179

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 distribution of ratings from verified guests — people who booked through Num and checked in at the venue by scanning its own code. Guests the venue comped or worked with are excluded, and Num publishes no verified average until a place has 5 such ratings (below that every number is null and `note` says why). Keep the two numbers separate; do not average them together. You MUST display the returned `attribution`.

NameTypeReqDescription
place_idstringyesFrom search_places, place_details or directory_feed.

No output schema declared.

No examples provided.

list_destinations ~74

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 when it has a real, maintained directory.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_places ~202

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 hours coverage, NOT an empty city. Never tell a traveller "nothing is open" on the strength of this tool; say that these are the ones Num can confirm are open. Use search_places for the full directory.

NameTypeReqDescription
bookable_onlyboolean–Only venues Num can hand off a booking page for.
categorystring–Exact category, e.g. "Restaurant". Omit for all.
destinationstringyesDestination slug, e.g. "los-angeles".
limitinteger–Max results, 1–50. Default 20.
nearstring–Neighbourhood, e.g. "Silver Lake".

No output schema declared.

No examples provided.

place_details ~209

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 verified the hours, NOT that it is closed), the booking platform and — only where a verified owner chose it — the venue's own booking page, a recently-read published price line where Num holds one, and up to 8 approved member photos plus the listing photo, each with its own `attribution` you MUST show alongside it. Use before showing a detail page or handing a traveller a phone number. Returns only what is verified — absent fields are absent because Num does not know them, never because they were omitted for brevity. Do not fill gaps from memory; an invented phone number is worse than a missing one.

NameTypeReqDescription
place_idstringyesFrom search_places.

No output schema declared.

No examples provided.

search_places ~322

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 quality and distance — so a 4.8★ institution two streets away beats an unrated snack bar next door — and each carries `distance_m`. When `near` is a neighbourhood name it filters by area and NO distance is returned. Returns name, category, area, rating, review count, phone, address and opening hours where known. NEVER invents a place: if Num does not hold it, it is not returned. You MUST display the returned `attribution` string wherever you show these results.

NameTypeReqDescription
categorystring–restaurant | bar | beach | spa | viewpoint | temple | waterfall | cafe (any case). Omit for all.
destinationstringyesDestination slug or city name, e.g. "phuket", "bangkok".
limitinteger–Max results, 1–20. Default 8.
nearstring–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".
querystring–Free text, e.g. "thai seafood", "rooftop".

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/placeguide MCP server?

io.github.CloudCorpRecords/placeguide runs locally as an npm package, launched with npx -y @reneturcios/placeguide mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/placeguide

# add to Claude Code
claude mcp add cloudcorprecords-placeguide -- npx -y @reneturcios/placeguide mcp
Common questions

What is the io.github.CloudCorpRecords/placeguide MCP server?

io.github.CloudCorpRecords/placeguide is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/placeguide. Search verified places, menus, reviews and hours across 119 travel destinations. This page covers its npm package (@reneturcios/placeguide).

Is the io.github.CloudCorpRecords/placeguide MCP server safe to use?

io.github.CloudCorpRecords/placeguide scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/placeguide MCP server expose?

io.github.CloudCorpRecords/placeguide exposes 9 tools: search_places, concierge_answer, list_destinations, place_details, open_places, and 4 more. Their descriptions and schemas cost roughly 1,836 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/placeguide MCP server still maintained?

io.github.CloudCorpRecords/placeguide is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/placeguide MCP server under?

io.github.CloudCorpRecords/placeguide declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.CloudCorpRecords/placeguide MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/placeguide, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.