Num places
REMOTE · APP.ITSNUM.COM
Open places, menus, ratings and booking routes in 119 travel destinations. Read-only, no key needed.
Available components
Last scanned (19 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 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 Security63
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1915 tokens (~212/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 Management17
- Stability observed for 5 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 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 62
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 18 Oct 2026 · Probed https://app.itsnum.com/api/partner/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=itsnum.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | dc6d8619b682fdb10e1e86a43d06fc5b |
| SANs: itsnum.com, app.itsnum.com, *.app.itsnum.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.itsnum.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| itsnum.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.itsnum.com/api/partner/mcp | Verified | 200 | |
| http (plaintext) | http://app.itsnum.com/api/partner/mcp | Served over HTTP | 200 |
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 →
booking_link How to book a place ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD. |
| party | integer | – | Number of covers, 1–20. |
| place_id | string | yes | From search_places or open_places. |
| time | string | – | HH:MM, 24-hour, local to the venue. |
No output schema declared.
No examples provided.
concierge_answer Ask Num a travel question ~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`.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Where they are, if you know it. Improves grounding. |
| language | string | – | BCP-47 tag for the reply, e.g. "th", "ru". Defaults to the language of the question. |
| near | string | – | Neighbourhood or hotel area, if known. |
| question | string | yes | The traveller's question, in their own words. Any language. |
No output schema declared.
No examples provided.
directory_feed Page through the directory ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The `next_cursor` from the previous page. Omit for the first page. |
| destination | string | yes | Destination slug from list_destinations, e.g. "los-angeles". |
| limit | integer | – | 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 Read a place’s 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`.
| Name | Type | Req | Description |
|---|---|---|---|
| place_id | string | yes | From search_places, place_details or directory_feed. |
No output schema declared.
No examples provided.
get_reviews Read reviews of a place ~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`.
| Name | Type | Req | Description |
|---|---|---|---|
| place_id | string | yes | From search_places, place_details or directory_feed. |
No output schema declared.
No examples provided.
list_destinations List the destinations Num covers ~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 Find places open at a time ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| bookable_only | boolean | – | Only venues Num can hand off a booking page for. |
| category | string | – | Exact category, e.g. "Restaurant". Omit for all. |
| destination | string | yes | Destination slug, e.g. "los-angeles". |
| limit | integer | – | Max results, 1–50. Default 20. |
| near | string | – | Neighbourhood, e.g. "Silver Lake". |
No output schema declared.
No examples provided.
place_details Get one place in full ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| place_id | string | yes | From search_places. |
No output schema declared.
No examples provided.
search_places Search real places in a destination ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | restaurant | bar | beach | spa | viewpoint | temple | waterfall | cafe (any case). Omit for all. |
| destination | string | yes | Destination slug or city name, e.g. "phuket", "bangkok". |
| limit | integer | – | Max results, 1–20. Default 8. |
| near | string | – | 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 | – | Free text, e.g. "thai seafood", "rooftop". |
No output schema declared.
No examples provided.
How do I install the Num places MCP server?
Num places is a hosted endpoint at https://app.itsnum.com/api/partner/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 · app.itsnum.com
claude mcp add --transport http com-itsnum-places 'https://app.itsnum.com/api/partner/mcp'
What is the Num places MCP server?
Num places is an MCP server listed in the public MCP registry as com.itsnum/places. Open places, menus, ratings and booking routes in 119 travel destinations. Read-only, no key needed. This page covers its hosted endpoint (https://app.itsnum.com/api/partner/mcp).
Is the Num places MCP server safe to use?
Num places scores 65 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 Num places MCP server expose?
Num places 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.
Does the Num places MCP server require authentication?
No. We connected to Num places without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Num places MCP server still maintained?
Num places is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.