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.

Daytrip

REMOTE · MCP.DAYTRIP.COM

Search, quote and book Daytrip private door-to-door car transfers in 130+ countries.

Available components

+5 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 4 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 Security74
Transport & Reachability100
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2253 tokens (~450/item across 5 items; 3 tools + 2 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 Management30
  • Stability observed for 9 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 4 Nov 26 +2
    • MCP protocol: fail → pass ▲ functional
    • The server no longer declares the “completions” capability functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
  • 3 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.

  • 1 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.

  • 30 Oct 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.

  • 28 Oct 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.

  • 27 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 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 4 Nov 2026 · Probed https://mcp.daytrip.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.daytrip.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 25 Sept 2026 10 Apr 2027 RSA 2048 SHA256-RSA a3b83b4ecfbb38ff256d05113fbbc5f
SANs: *.daytrip.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.daytrip.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
daytrip.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://mcp.daytrip.com/mcp Verified 200
http (plaintext) http://mcp.daytrip.com/mcp HTTPS enforced 301 https://mcp.daytrip.com/mcp
MCP tools · 3 exposed · ~1,732 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
get_booking_link ~564

Prepare a search_trips option on daytrip.com and return a link where the traveler finishes the booking themselves. Nothing is charged and no personal data is needed: on the link the traveler enters their name, email and phone, optional pickup address and flight number, and pays. Use this when the traveler prefers to finish on the website, or when book_trip is not available to you. It does not create a booking. Returns one of: - status "handover": give handoverUrl to the traveler and tell them to open it, complete their details and pay. summary describes the trip; the quoted price is held until expiresAt (the link keeps working afterwards, but the price may be re-quoted). - status "price_changed" (PRICE_CHANGED): the price moved since the search. Tell the traveler the new price; if they accept, call get_booking_link again with the returned offerId. - status "offer_expired" (OFFER_EXPIRED): call search_trips again and offer the fresh options. - status "route_not_available" (ROUTE_NOT_AVAILABLE): the trip can no longer be booked; call search_trips again or suggest alternatives. - status "invalid_input" (INVALID_INPUT): the vehicleType or a stop does not belong to that offer, or a customStops place could not be resolved; the message says what to fix. Stops: pass availableStops entries as stops (price is known from the search) or other places as customStops (re-priced). The returned price is the total including stops. Nothing is reserved or charged by this tool: the booking exists only once the traveler pays on the website. Never mention ids, tool names or internal steps to the traveler. Each call creates a new booking draft; call it once per confirmed choice.

NameTypeReqDescription
additionalLuggageinteger–Suitcases beyond one per passenger.
adultsintegeryesNumber of adult passengers, including the lead traveler.
childreninteger–Number of children.
currencystring–ISO 4217 code to show the price in as well; use the one from search_trips.
customStopsarray–Stops at places not in availableStops. The trip is then routed and priced through them, so the price will differ from the search.
localestring–Language of the traveler's pages and emails (en, de, es, fr, pt).
offerIdstringyesofferId of the chosen search_trips option.
stopsarray–Sightseeing stops from the search's availableStops the customer wants to add, in any order.
vehicleTypestringyesvehicle.type of the chosen search_trips option (a class identifier such as sedan or van).

No output schema declared.

No examples provided.

get_quote ~437

Price one search_trips option exactly as it will be booked: the chosen vehicle, the party and any stops. Returns everything the traveler must see before committing (seller, total price and currency, what is included, when they are charged, cancellation policy and free-cancellation deadline) and a single-use quoteId for book_trip. Returns one of: - status "quoted": present price, cancellationTerms and paymentTiming to the traveler; if previousPrice is set, the price differs from the search option and must be confirmed again. The quote can be booked until expiresAt; afterwards call get_quote again. - status "offer_expired" (OFFER_EXPIRED): the search option is gone; call search_trips again. - status "route_not_available" (ROUTE_NOT_AVAILABLE): the trip can no longer be priced; call search_trips again or suggest alternatives. - status "invalid_input" (INVALID_INPUT): the vehicleType or a stop does not belong to that offer, or a customStops place could not be resolved; the message says what to fix. Nothing is reserved and no personal data is needed. Each call prices the trip afresh.

NameTypeReqDescription
additionalLuggageinteger–Suitcases beyond one per passenger.
adultsintegeryesNumber of adult passengers, including the lead traveler.
childreninteger–Number of children.
currencystring–ISO 4217 code to show the price in as well; use the one from search_trips.
customStopsarray–Stops at places not in availableStops. The trip is then routed and priced through them, so the price will differ from the search.
localestring–Language of the traveler's pages and emails (en, de, es, fr, pt).
offerIdstringyesofferId of the chosen search_trips option.
stopsarray–Sightseeing stops from the search's availableStops the customer wants to add, in any order.
vehicleTypestringyesvehicle.type of the chosen search_trips option (a class identifier such as sedan or van).

No output schema declared.

No examples provided.

search_trips ~731

Search Daytrip private door-to-door car transfers between two places (city to city, airport to city, …) and get bookable prices for every vehicle class. Returns one of: - status "ok": options[] (one per vehicle class) with price, capacity, duration and expiresAt, plus the resolved origin/destination and departureAt (local time). Present the options that fit the party (fitsPassengers) to the customer; when they choose, call get_quote with the option's offerId and vehicle.type (then book_trip with the quote), or get_booking_link with the same arguments for the traveler to finish on daytrip.com. availableStops[] lists sightseeing stops on the way with their extra cost per vehicle class (priceByVehicle, keyed by vehicle.type) and default time at the stop; offer them and pass the chosen ones to get_quote or get_booking_link. Only options with stopsAllowed can take stops (Lite classes are direct rides). - status "ambiguous_location" (code AMBIGUOUS_LOCATION): field says whether origin or destination was unclear, candidates[] lists the places it could mean. Ask the customer, then call search_trips again passing the chosen candidate's label verbatim in that field. - status "location_not_found" (LOCATION_NOT_FOUND): ask for a city, airport or IATA code. - status "invalid_departure" (INVALID_DEPARTURE): fix the date/time and retry. - status "route_not_available" (ROUTE_NOT_AVAILABLE): Daytrip does not serve that trip; suggest a nearby city/airport or another date. - status "price_unavailable" (PRICE_UNAVAILABLE): nothing could be priced for that date; suggest another date. When talking to the customer, describe options by vehicle name and price and never mention ids, tool names or internal steps. Prices are per vehicle (not per person), all-inclusive and valid until expiresAt. price is in the trip's pricing currency; when a currency was requested and priceInRequestedCurrency is present, that is the amount the checkout charges, so quote that one to the customer. Only one-wa…

NameTypeReqDescription
additionalLuggageinteger–Suitcases beyond one per passenger; each passenger already has one suitcase and one carry-on included.
adultsintegeryesNumber of adult passengers (the lead traveler counts as one).
childreninteger–Number of children (under 12).
currencystring–ISO 4217 code the customer prefers (eur, usd, gbp, …). Adds priceInRequestedCurrency and makes the checkout charge in it.
departureAtstringyesPickup date and time, ISO 8601. Without an offset it is local time at the pickup place (e.g. 2026-10-01T09:00); with an offset or Z it is converted to the pickup place's local time.
destinationstringyesDrop-off place, same rules as origin.
localestring–Customer language (en, de, es, fr, pt). Used for the handover link.
originstringyesPickup place as the customer said it: a city, airport, IATA code or "City, Country". To pick an ambiguous_location candidate, pass its label verbatim.

No output schema declared.

No examples provided.

Install

How do I install the Daytrip MCP server?

Daytrip is a hosted endpoint at https://mcp.daytrip.com/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 · mcp.daytrip.com

# add to Claude Code
claude mcp add --transport http com-daytrip-mcp 'https://mcp.daytrip.com/mcp'
Common questions

What is the Daytrip MCP server?

Daytrip is an MCP server listed in the public MCP registry as com.daytrip/mcp. Search, quote and book Daytrip private door-to-door car transfers in 130+ countries. This page covers its hosted endpoint (https://mcp.daytrip.com/mcp).

Is the Daytrip MCP server safe to use?

Daytrip 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 Daytrip MCP server expose?

Daytrip exposes 3 tools: search_trips, get_quote, get_booking_link. Their descriptions and schemas cost roughly 1,732 tokens of context every time the server is loaded.

Does the Daytrip MCP server require authentication?

No. We connected to Daytrip without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Daytrip MCP server still maintained?

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