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/traveldex

NPM · @RENETURCIOS/TRAVELDEX · 2 COMPONENTS

Search 2.5M travel places and place photos: details, booking routes, photo quotes and wallet.

71 Trust /100

Last scanned (15 hours ago)

Scores higher than 42% 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 Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1094 tokens (~156/item across 7 items; 7 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 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/traveldex@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 · 7 exposed · ~1,094 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
num_get_place ~231

Full record for one place, by the place_id that num_search_places returned, including HOW TO BOOK IT on the venue's own terms. `booking.method` is one of: request (the venue takes requests through NUM and confirms each one itself), venue_system (send the traveller to booking.url, prefilled when you pass party_size, date and time), phone (the number is for the traveller to call), not_through_num, closed, unknown. Follow booking.guidance exactly. If open_status.closed is true, NUM holds evidence the place has gone: do not send anyone there. accolades carry their source; menu is the owner's own list and prices. Each call counts against the daily read quota.

NameTypeReqDescription
datestring–Optional: YYYY-MM-DD, to prefill the venue's booking page.
party_sizeinteger–Optional: people in the party, to prefill the venue's booking page.
place_idstringyesThe place_id returned by num_search_places.
timestring–Optional: HH:MM 24-hour, local to the venue.

No output schema declared.

No examples provided.

num_list_destinations ~43

Every destination NUM covers, with its country. Use a destination's name or slug as num_search_places city. Free, unmetered, and needs no key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

num_list_submissions ~75

Lists the businesses and promotions this account has submitted, with the reviewer's decision on each. Free and unmetered.

NameTypeReqDescription
limitinteger–Maximum number of submissions to return.
offsetinteger–Number of submissions to skip, for paging.
statusstring–Only submissions with this review status.

No output schema declared.

No examples provided.

num_photo_wallet ~65

This account's photo wallet balance (US cents, plus test credit), what it spent today against the daily cap, and the licenses it holds. Free and unmetered. Adding credit is POST /api/agent/photos/topup, which returns a checkout link a person pays.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

num_quote_photo ~84

The current price in US cents and the full license terms for one use of one photo. Nothing is charged. Counts against the daily read quota.

NameTypeReqDescription
photo_idstringyesFrom num_search_photos.
usestringyesThe use to price: social (one post), web (one page), ad (one campaign) or ai_training (one dataset).

No output schema declared.

No examples provided.

num_search_photos ~329

Search photos of real places taken by NUM travelers and offered for licensing per use. Each result has a photo_id, a preview URL, the place (name, city, area, category), the month it was taken, the photographer's public name and the price in US cents for each use: social (one post), web (one page), ad (one campaign) and ai_training (one dataset). A price of null means that use cannot be bought right now. Business uses sell in live drops: a limited number of licenses over 3 days, the price rising 10% after each one; drop shows licenses left, the end time and the next price. Every photo shows a place with no recognisable person and was checked by a person; results never include coordinates or exact dates. use=ai_training returns only photos whose photographer allows AI training. Each call counts against the daily read quota.

NameTypeReqDescription
categorystring–e.g. 'Restaurant', 'Bar', 'Hotel'.
citystring–A NUM destination or neighbourhood, e.g. 'London' or 'Silom'.
kindstring–Only photos of this kind, e.g. 'storefront' or 'interior'.
limitinteger–Maximum number of photos to return.
offsetinteger–Number of photos to skip, for paging.
place_idstring–Only photos of this place (from num_search_places).
qstring–Free text matched against the place name.
usestring–Only photos offered for this use.

No output schema declared.

No examples provided.

num_search_places ~267

Search NUM's travel directory: more than 2.5 million places — restaurants, bars, hotels, spas, tours and shops, deepest in Thailand and the UK. Say where to look: city (one of NUM's destinations — see num_list_destinations) or country; then narrow with q, area and category. Places NUM knows have closed are never returned. Returns name, category, address, phone, website, coordinates and whether the owner has claimed the listing; call num_get_place for how to book one. Each call counts against the daily read quota.

NameTypeReqDescription
areastring–A neighbourhood inside the destination, e.g. 'Kata' or 'Soho'.
categorystring–e.g. 'Restaurant', 'Bar', 'Hotel', 'Spa', 'Tour'.
citystring–A NUM destination, e.g. 'Phuket', 'Edinburgh', 'Bangkok', 'London'. Required unless country is given.
countrystring–ISO-2 code or name, e.g. 'TH' or 'Thailand'. Searches every NUM destination in that country.
limitinteger–Max results, default 20, cap 50.
qstring–Free text matched against the place name.

No output schema declared.

No examples provided.

Install

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

io.github.CloudCorpRecords/traveldex runs locally as an npm package, launched with npx -y @reneturcios/traveldex 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/traveldex

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

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

io.github.CloudCorpRecords/traveldex is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/traveldex. Search 2.5M travel places and place photos: details, booking routes, photo quotes and wallet. This page covers its npm package (@reneturcios/traveldex).

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

io.github.CloudCorpRecords/traveldex scores 71 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/traveldex MCP server expose?

io.github.CloudCorpRecords/traveldex exposes 7 tools: num_search_places, num_list_destinations, num_get_place, num_list_submissions, num_search_photos, and 2 more. Their descriptions and schemas cost roughly 1,094 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/traveldex 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/traveldex MCP server under?

io.github.CloudCorpRecords/traveldex 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/traveldex MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/traveldex, 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.