← All servers

Daytrip

warnings

mcp.daytrip.com

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

https://mcp.daytrip.com/mcpWebsiteOAuthMCP 2025-06-18v1.0.0last checked 27 Oct 2026spoke MCP on 1 of 1 check (30 days)initialize in 330 ms

Last checked 27 Oct 2026

✓Answered the MCP handshake (MCP 2025-06-18)
✓Auth detected: OAuth
✓Lists 3 tools
!1 warning
✓Spoke MCP on 1 of 1 check (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✕Claude CodeNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude Code docs · read on 2026-08-30

✕Claude (claude.ai & Desktop)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✕ChatGPTNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

ChatGPT docs · read on 2026-08-30

✕CursorNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Cursor docs · read on 2026-08-30

✕VS Code (Copilot)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 27 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://mcp.daytrip.com
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✕None advertised MCP requires S256; a client that implements only that has no method in common with this server.
Grant types	client_credentials
Scopes	trips:read, bookings:read, bookings:write
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 3 tools listable

What the probe found

warningThe server card contradicts the server

https://mcp.daytrip.com/mcp/server-card: the card says version 1.0, the server says 1.0.0. Clients that configure themselves from the card are told something the live server does not do.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

3 tools usable without signing in

The server exposes a public surface before authorization: search_trips, get_quote, get_booking_link.

Tools

get_booking_linkget_quotesearch_trips

Contract history

27 Oct 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/daytrip/badge.svg)](https://mcpi.app/servers/daytrip)