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.

My Daily Journeys trip planning

REMOTE · APP.MYDAILYJOURNEYS.COM

Private trips in Vietnam, Thailand and Cambodia by Maya Dalal: products, seasons, prices, places.

+3 this week 75 Trust /100

Last scanned (17 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security80
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1596 tokens (~177/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 Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 72% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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 +1
    • “start_trip_request” reworded the description of “service” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 11 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_destination_season” rewrote its description, which is the text the model reads security
    • Tool “estimate_trip” rewrote its description, which is the text the model reads security
    • Schema quality: 145 → 176 ▼ functional
    • Tool coverage: 61% → 72% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “check_glasses_rental” functional
    • New tool “get_price_index” functional
    • “estimate_trip” added an optional parameter “start_month” cosmetic
  • 10 Nov 26 70

    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 · Probed https://app.mydailyjourneys.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.mydailyjourneys.com CN=YR1,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 2048 SHA256-RSA 66a362e7b9c9bc730a0c092a9e7c4a242d4
SANs: app.mydailyjourneys.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.mydailyjourneys.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
mydailyjourneys.com. No DS 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
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.mydailyjourneys.com/api/mcp Verified 200
http (plaintext) http://app.mydailyjourneys.com/api/mcp HTTPS enforced 308 https://app.mydailyjourneys.com/api/mcp
MCP tools · 9 exposed · ~1,437 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
check_destination_season ~147

Maya's own month-by-month guide (recommended / possible with caveats / not recommended) for destinations in Vietnam, Thailand, Cambodia, Laos, South Korea and Singapore, with her short advice in English (advice_en) and Hebrew (detail_he). Give a destination, a region, a month, or both. The same guide for people: https://planning.mydailyjourneys.com/tools/best-time-to-visit

NameTypeReqDescription
destinationstring–City, region or country, in English, for example "Sapa", "Hoi An", "Gulf of Thailand", "Vietnam".
monthstring–Month name or number 1 to 12.

No output schema declared.

No examples provided.

check_glasses_rental ~289

Checks MDJ's rules for an AI agent booking the smart glasses rental (voice guide MAYA) by itself: the destination must be approved, the kit handover must be at an approved place (secure locker at Ben Gurion airport, or courier delivery in central Israel), the start date must be at least 30 days away, and a kit must be free for the dates. When all pass, returns the price from the MDJ store, the checkout link and a signed AP2-style cart. When any fails, returns how the traveler contacts MDJ: Maya answers those requests case by case. Never creates a booking.

NameTypeReqDescription
delivery_areastring–Required for home_delivery: is the address in central Israel?
destinationstringyesCountry or city of the trip, for example "Vietnam" or "Hoi An".
end_datestringyesLast day of the rental, YYYY-MM-DD.
handoverstringyesairport_locker: secure locker at Ben Gurion airport. home_delivery: courier to the traveler's address.
packagestring–Optional, default smart-trip. smart-trip: the traveler planned the route. mdj-planner: Maya also plans the route. vip-experience: planning plus eSIM, video editing and home delivery.
start_datestringyesFirst day of the rental, YYYY-MM-DD.

No output schema declared.

No examples provided.

create_cart_mandate ~125

Creates an AP2-style CartMandate for one fixed-price product, signed by MDJ (ES256 JWS, public key at https://app.mydailyjourneys.com/.well-known/mdj-ap2-jwks.json). Valid for 30 minutes. Payment is completed on the normal store checkout page in checkout_url, never through this server. Ground services cannot be put in a cart.

NameTypeReqDescription
product_idstringyesAn id from list_products.
variant_idstring–Required for products with variants (custom-trip-itinerary-planning).

No output schema declared.

No examples provided.

estimate_trip ~199

A price range for a fully planned and booked MDJ trip, from the ranges MDJ publishes (per person per day, by hotel level, for a couple, everything included except international flights). The final price always comes from a supplier quote for the specific trip. The same calculation for people: https://planning.mydailyjourneys.com/tools/trip-cost-calculator

NameTypeReqDescription
daysintegeryes–
destinationstring–Country: Vietnam, Thailand or Cambodia.
hotel_levelstring–Optional. Without it, all 3 levels are returned.
start_monthstring–Optional: the month the trip starts, a month name or a number from 1 to 12. With a destination, each range is adjusted to that month where at least 5 real MDJ trips at that hotel level back it; other…
travelersintegeryes–

No output schema declared.

No examples provided.

get_business_profile ~50

Who My Daily Journeys (MDJ) is, where it operates, what it sells, how buying works, how to contact Maya, and the human service envelope that sets it apart from booking alone.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_price_index ~133

The MDJ price index is not yet published. For a price range use estimate_trip, and for a real price start_trip_request.

NameTypeReqDescription
hotel_levelstring–Optional. mix = a mix of 4-star and 5-star hotels.
partystring–Optional: solo, couple, family (with children) or group (3 or more adults).
start_monthinteger–Optional: month the trip starts, 1 to 12.
tablestring–Optional: return one whole table.
trip_daysinteger–Optional: length of the trip in days.

No output schema declared.

No examples provided.

list_products ~60

The fixed-price MDJ products with their USD prices and store page links (trip kick-off deposit, planning, apps, experience maps). Ground services are not listed: they are priced by quote only.

NameTypeReqDescription
typestring–Optional filter by product type.

No output schema declared.

No examples provided.

search_recommendations ~149

Places from Maya's city maps (attractions, hidden gems, local experiences, cafes, restaurants, nightlife, shopping) with a Google Maps link. Returns at most 10 places per call, plus the link to the full map.

NameTypeReqDescription
categorystring–Optional, for example "Cafes", "Restaurants", "Hidden gems", "Attractions".
citystringyesFor example "Hanoi", "Hoi An", "Bangkok", "Siem Reap", "Luang Prabang", "Seoul".
limitinteger––
querystring–Optional free text, for example "coffee", "rooftop", "market".

No output schema declared.

No examples provided.

start_trip_request ~285

Sends the traveler's trip request to Maya as a new lead, exactly like her website questionnaire. Use it only when the traveler asked to be contacted by MDJ and agreed to share these details. Maya or her team reply by email. Set dry_run to true to validate without sending.

NameTypeReqDescription
adultsinteger––
agent_namestring–Name of the AI assistant sending this request.
childreninteger––
children_agesstring––
countrystring–Country the traveler lives in.
departure_datestring–YYYY-MM-DD or a month.
descriptionstring–What the traveler wants, in their words.
destinationstringyes–
dry_runboolean––
emailstringyesThe traveler's email address.
first_namestringyes–
hotel_levelstring––
last_namestring––
phonestring–Optional, with country code.
return_datestring––
servicestring–full_custom: Maya plans and books the entire trip. execute_existing: the traveler already has an itinerary and wants it booked and supported.
traveler_consentbooleanyesMust be true: the traveler asked to be contacted by MDJ.
trip_lengthstring–For example "14 days".

No output schema declared.

No examples provided.

Install

How do I install the My Daily Journeys trip planning MCP server?

My Daily Journeys trip planning is a hosted endpoint at https://app.mydailyjourneys.com/api/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.mydailyjourneys.com

# add to Claude Code
claude mcp add --transport http com-mydailyjourneys-app-trip-planning 'https://app.mydailyjourneys.com/api/mcp'
Common questions

What is the My Daily Journeys trip planning MCP server?

My Daily Journeys trip planning is an MCP server listed in the public MCP registry as com.mydailyjourneys.app/trip-planning. Private trips in Vietnam, Thailand and Cambodia by Maya Dalal: products, seasons, prices, places. This page covers its hosted endpoint (https://app.mydailyjourneys.com/api/mcp).

Is the My Daily Journeys trip planning MCP server safe to use?

My Daily Journeys trip planning scores 75 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 My Daily Journeys trip planning MCP server expose?

My Daily Journeys trip planning exposes 9 tools: get_business_profile, list_products, check_destination_season, estimate_trip, search_recommendations, and 4 more. Their descriptions and schemas cost roughly 1,437 tokens of context every time the server is loaded.

Does the My Daily Journeys trip planning MCP server require authentication?

No. We connected to My Daily Journeys trip planning without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the My Daily Journeys trip planning MCP server still maintained?

My Daily Journeys trip planning 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 did VerifyMCP test on the My Daily Journeys trip planning MCP server?

VerifyMCP ran 13 checks on My Daily Journeys trip planning, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.