_ registry / mcp streamable-http · checked 33m ago

airport-transfer-connect-transfers

https://www.airporttransferconnect.com

Registry code: 56d7c568b75e7cf7

api record

Use get_quote to price a private transfer (airport ↔ hotel/address) with Airport Transfer Connect. Prices are EUR per vehicle, VAT included, live. Use request_booking only after the user confirms and gives name, email and phone; then give them the booking_url to confirm/pay.

endpoint
https://www.airporttransferconnect.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is airport-transfer-connect-transfers live?
Yes — it answered the hub's last check (checked 33m ago). It answered 100% of checks over the last 30 days.
Is airport-transfer-connect-transfers free to use?
Yes — the hub reached it with no key and no payment.
What tools does airport-transfer-connect-transfers have?
3 tools: check_availability, request_booking, get_quote.
Is airport-transfer-connect-transfers safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,741ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_availability unknown 33m ago

    Check whether a private transfer can be booked for the given route, date/time and number of passengers, and which vehicles fit.

    mcp-tool

    {
  "type": "object",
  "required": [
    "from",
    "to",
    "date"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Drop-off: airport IATA code, hotel name + city, or full address."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Pickup date, YYYY-MM-DD (local time at pickup)."
    },
    "from": {
      "type": "string",
      "description": "Pickup: airport IATA code (CDG, ORY, BVA, LBG, OTP, NCE, LHR…), hotel name + city, or full address."
    },
    "time": {
      "type": "string",
      "default": "12:00",
      "description": "Pickup time HH:MM 24h local. For airport pickups use the flight landing time."
    },
    "luggage": {
      "type": "integer",
      "maximum": 20,
      "minimum": 0,
      "description": "Number of suitcases, defaults to passengers (alias accepted: bags)."
    },
    "passengers": {
      "type": "integer",
      "default": 2,
      "maximum": 16,
      "minimum": 1,
      "description": "Number of passengers (alias accepted: pax)."
    },
    "return_date": {
      "type": "string",
      "description": "Optional return date YYYY-MM-DD for a round trip."
    },
    "return_time": {
      "type": "string",
      "description": "Optional return pickup time HH:MM."
    },
    "flight_number": {
      "type": "string",
      "description": "Optional flight number, e.g. AF1234."
    }
  }
}
    arguments 53 lines
  • request_booking unknown never probed

    Register a booking request for the passenger (name, email, phone required; only with the user's explicit consent). Returns a reference and a prefilled booking_url where the passenger confirms and pays (card or pay the driver).

    mcp-tool

    {
  "type": "object",
  "required": [
    "from",
    "to",
    "date",
    "name",
    "email",
    "phone"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Drop-off: airport IATA code, hotel name + city, or full address."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Pickup date, YYYY-MM-DD (local time at pickup)."
    },
    "from": {
      "type": "string",
      "description": "Pickup: airport IATA code (CDG, ORY, BVA, LBG, OTP, NCE, LHR…), hotel name + city, or full address."
    },
    "name": {
      "type": "string",
      "description": "Lead passenger full name."
    },
    "time": {
      "type": "string",
      "default": "12:00",
      "description": "Pickup time HH:MM 24h local. For airport pickups use the flight landing time."
    },
    "email": {
      "type": "string",
      "format": "email"
    },
    "notes": {
      "type": "string",
      "description": "Optional: child seat, extra stop, name sign text…"
    },
    "phone": {
      "type": "string",
      "description": "Mobile in international format, e.g. +14155550123 (WhatsApp preferred)."
    },
    "luggage": {
      "type": "integer",
      "maximum": 20,
      "minimum": 0,
      "description": "Number of suitcases, defaults to passengers (alias accepted: bags)."
    },
    "vehicle": {
      "type": "string",
      "description": "Optional preferred vehicle: \"E Class\", \"V Class\", \"S Class\"."
    },
    "passengers": {
      "type": "integer",
      "default": 2,
      "maximum": 16,
      "minimum": 1,
      "description": "Number of passengers (alias accepted: pax)."
    },
    "return_date": {
      "type": "string",
      "description": "Optional return date YYYY-MM-DD for a round trip."
    },
    "return_time": {
      "type": "string",
      "description": "Optional return pickup time HH:MM."
    },
    "flight_number": {
      "type": "string",
      "description": "Optional flight number, e.g. AF1234."
    }
  }
}
    arguments 76 lines
  • get_quote unknown 33m ago

    Live fixed price (EUR, per vehicle, VAT incl.) for a private transfer/chauffeur ride with Airport Transfer Connect — e.g. CDG airport to a Paris hotel. Returns prices for E-Class, V-Class, S-Class, availability and a prefilled booking_url.

    mcp-tool

    {
  "type": "object",
  "required": [
    "from",
    "to",
    "date"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Drop-off: airport IATA code, hotel name + city, or full address."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Pickup date, YYYY-MM-DD (local time at pickup)."
    },
    "from": {
      "type": "string",
      "description": "Pickup: airport IATA code (CDG, ORY, BVA, LBG, OTP, NCE, LHR…), hotel name + city, or full address."
    },
    "time": {
      "type": "string",
      "default": "12:00",
      "description": "Pickup time HH:MM 24h local. For airport pickups use the flight landing time."
    },
    "luggage": {
      "type": "integer",
      "maximum": 20,
      "minimum": 0,
      "description": "Number of suitcases, defaults to passengers (alias accepted: bags)."
    },
    "passengers": {
      "type": "integer",
      "default": 2,
      "maximum": 16,
      "minimum": 1,
      "description": "Number of passengers (alias accepted: pax)."
    },
    "return_date": {
      "type": "string",
      "description": "Optional return date YYYY-MM-DD for a round trip."
    },
    "return_time": {
      "type": "string",
      "description": "Optional return pickup time HH:MM."
    },
    "flight_number": {
      "type": "string",
      "description": "Optional flight number, e.g. AF1234."
    }
  }
}
    arguments 53 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 56d7c568b75e7cf7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/56d7c568b75e7cf7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/56d7c568b75e7cf7/badge.svg)](https://brick.blue/agent/56d7c568b75e7cf7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.