Antalya Transfers
REMOTE · API.ANTALYATRANSFERS.CO
Quote and request private airport transfers in Antalya, Turkey. Operator confirms each request.
Available components
Last scanned (20 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
Recent critical change
Authorization (14 Oct 2026). See the changelog before you install this server.
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
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_transfer_request). See how to fix → View diagnostics → Fail
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1434 tokens (~358/item across 4 items; 4 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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 current MCP spec version (2026-07-28).Pass
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.
- 17 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.
- 15 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_transfer_request” rewrote its description, which is the text the model reads security
- Schema quality: 324 → 358 ▼ functional
- Server version: 1.2.0 → 1.3.0 functional
- “create_transfer_request” added an optional parameter “idempotencyKey” cosmetic
- 14 Oct 26 −6
- Authorization: partial → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- New tool “cancel_transfer_request”, which the server declares destructive security
- Schema quality: 1029 → 1298 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.2.0 functional
- “get_price_quote” reworded the description of “vehicleType” cosmetic
- 13 Oct 26 71
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://api.antalyatransfers.co/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=antalyatransfers.co | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3f122c9c252944980ef87a6b2678e84b |
| SANs: antalyatransfers.co, *.antalyatransfers.co | ||||||
| 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 api.antalyatransfers.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| antalyatransfers.co. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.antalyatransfers.co/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.antalyatransfers.co/api/mcp | HTTPS enforced | 301 | https://api.antalyatransfers.co/api/mcp |
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 →
cancel_transfer_request Cancel a pending transfer request ~222
Use this only when the customer has explicitly asked to cancel their transfer request and you have the booking reference returned by create_transfer_request and the email used for it. Cancels a request that is still pending or assigned, tells the operator (WhatsApp/email) and emails the customer a cancellation notice. Calling it again for an already-cancelled request is harmless and returns cancelled=true without notifying anyone again. Destructive and sends real messages: never call it to explore, to "test", or because the customer is merely unsure or wants to change details. Do not use for a request the operator has already confirmed (it is refused: the customer must contact the operator), for changing time/passengers/vehicle (contact the operator), or for refunds. Use get_request_status to check the current state first if unsure.
| Name | Type | Req | Description |
|---|---|---|---|
| customerEmail | string | yes | Email address used when the request was submitted |
| reason | string | – | Optional short reason given by the customer |
| reference | string | yes | Booking reference, e.g. AT-20260605-0001 |
| Name | Type | Req | Description |
|---|---|---|---|
| alreadyCancelled | boolean | – | true when it had been cancelled before this call (no new notification sent) |
| cancelled | boolean | yes | true: the request is cancelled |
| message | string | yes | – |
| operatorNotified | boolean | – | – |
| reference | string | yes | – |
| status | string | yes | – |
No examples provided.
create_transfer_request Submit transfer request (pending operator confirmation) ~554
Use this only after the customer has chosen a route, time and vehicle and has given their name, email and phone, and explicitly asked to send the request. Submits a transfer REQUEST that is stored as pending and reviewed by the operator, who confirms the ride and final price by email/WhatsApp. This does NOT confirm a booking, assign a driver or take payment — never tell the customer the ride is confirmed. Writes data: do not call it to explore prices (use get_price_quote) and do not retry on success. Pass idempotencyKey to make retries safe: the same key for the same customer returns the original reference (duplicate=true) and never creates a second request; to change details, cancel and submit a new request with a new key. Without a key, repeating identical details also returns the original request. At most 5 requests per phone number per day. Capacity is checked: parties larger than the vehicle are rejected with a suggested vehicle.
| Name | Type | Req | Description |
|---|---|---|---|
| childSeats | integer | – | Child seats required |
| customerEmail | string | yes | Where the reference and confirmation are sent |
| customerName | string | yes | Full name of the lead passenger |
| customerPhone | string | yes | International format with country code, e.g. +905551234567 |
| dropoffAddress | string | yes | Drop-off place or hotel name with its area |
| flightNumber | string | – | Flight number without spaces, e.g. TK2548 |
| idempotencyKey | string | – | Optional. A unique value (e.g. a UUID) you generate once per customer request and reuse on every retry. A retry with the same key and same customer email/phone returns the original reference with dup… |
| language | string | – | Customer language code, e.g. en, ru, de, tr |
| luggage | integer | – | Large suitcases |
| notes | string | – | Extra instructions for the operator (hotel address, special needs) |
| passengers | integer | yes | Total passengers including children |
| pets | integer | – | Pets travelling (the operator confirms whether they can be carried) |
| pickupAddress | string | yes | Pickup place, e.g. "Antalya Airport (AYT) Terminal 2" |
| scheduledAt | string | yes | ISO 8601 date-time of pickup in Antalya local time, e.g. 2026-11-20T10:00:00+03:00. If no timezone is given, Antalya time (UTC+3) is assumed. For arrivals use flight landing time plus ~30 minutes. |
| vehicleType | string | yes | Vehicle class; must fit passengers, luggage and child seats |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate | boolean | – | true: no new request was created; the original is returned |
| estimatedPrice | string|null | – | – |
| message | string | yes | – |
| operatorConfirmed | boolean | yes | false: this is a request, not a confirmed ride |
| priceStatus | string | – | – |
| reference | string | – | Booking reference for get_request_status |
| status | string | yes | New requests are pending. With duplicate=true this is the original request's current status. Only operatorConfirmed=true means the ride is confirmed. |
No examples provided.
get_price_quote Get airport transfer price quote ~392
Use this when a traveller asks how much a private airport transfer costs between Antalya Airport (AYT) and Antalya-area destinations (Konyaaltı, Antalya city/Kaleiçi, Lara, Belek, Side, Alanya, Kemer, Kaş) or between those resorts. Returns a fixed-price estimate in EUR, whether the party fits the chosen vehicle, and a suggested vehicle if not. Read-only: it does not create a request or reserve anything. Do not use for flights, car rental, tours, or destinations outside the Antalya region. If a route has no fixed price, priced=false and the operator quotes it.
| Name | Type | Req | Description |
|---|---|---|---|
| childSeats | integer | – | Number of child seats needed (optional) |
| dropoffAddress | string | yes | Drop-off place, same format as pickupAddress, e.g. "Kemer". |
| luggage | integer | – | Number of large suitcases (optional) |
| passengers | integer | yes | Total passengers including children |
| pickupAddress | string | yes | Pickup place: "Antalya Airport (AYT)", a resort area or a hotel name, e.g. "Rixos Premium Belek". |
| scheduledAt | string | – | Optional pickup time. ISO 8601 date-time of pickup in Antalya local time, e.g. 2026-11-20T10:00:00+03:00. If no timezone is given, Antalya time (UTC+3) is assumed. If omitted a daytime price is retur… |
| vehicleType | string | – | Optional: if omitted the smallest vehicle that fits the party is quoted. Capacity: sedan 3 pax/2 large bags; minivan 8 pax/6 large bags; vip_sedan 3 pax/2 large bags; minibus 16 pax/12 large bags; bu… |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | – | Defaults applied for missing optional inputs |
| capacity | object | – | – |
| currency | string | yes | – |
| estimatedPrice | string|null | – | Formatted EUR price, e.g. "€80.00" |
| nightSurchargeApplied | boolean | – | +30% for pickups 22:00–06:00 Antalya time |
| note | string | yes | – |
| priceCents | integer|null | – | – |
| priced | boolean | yes | false when this route has no fixed price; the operator will quote it |
| route | string|null | – | – |
| vehicleType | string | – | – |
No examples provided.
get_request_status Check transfer request status ~112
Use this when the customer asks whether their transfer request was confirmed, assigned or cancelled. Requires the booking reference returned by create_transfer_request and the email used for the request. Read-only. pending means the operator has not confirmed yet; only operatorConfirmed=true means the ride is confirmed. Do not use to create or change a request.
| Name | Type | Req | Description |
|---|---|---|---|
| customerEmail | string | yes | Email address used when the request was submitted |
| reference | string | yes | Booking reference, e.g. AT-20260605-0001 |
| Name | Type | Req | Description |
|---|---|---|---|
| dropoffAddress | string | – | – |
| estimatedPrice | string|null | – | – |
| operatorConfirmed | boolean | yes | – |
| pickupAddress | string | – | – |
| priceStatus | string | – | – |
| reference | string | yes | – |
| scheduledAt | string | – | – |
| status | string | yes | – |
| statusMeaning | string | yes | – |
No examples provided.
How do I install the Antalya Transfers MCP server?
Antalya Transfers is a hosted endpoint at https://api.antalyatransfers.co/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 · api.antalyatransfers.co
claude mcp add --transport http co-antalyatransfers-transfers 'https://api.antalyatransfers.co/api/mcp'
What is the Antalya Transfers MCP server?
Antalya Transfers is an MCP server listed in the public MCP registry as co.antalyatransfers/transfers. Quote and request private airport transfers in Antalya, Turkey. Operator confirms each request. This page covers its hosted endpoint (https://api.antalyatransfers.co/api/mcp).
Is the Antalya Transfers MCP server safe to use?
Antalya Transfers scores 67 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 Antalya Transfers MCP server expose?
Antalya Transfers exposes 4 tools: get_price_quote, create_transfer_request, get_request_status, cancel_transfer_request. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.
Does the Antalya Transfers MCP server require authentication?
No. We connected to Antalya Transfers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Antalya Transfers MCP server still maintained?
Antalya Transfers 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.