_ registry / mcp streamable-http · checked 1h ago

vtc-aeroport-paris

https://vtc-aeroport.fr

Registry code: 238795d824ff0939

api record

VTC AEROPORT PARIS : chauffeur prive et transferts aeroport en Ile-de-France (Roissy CDG, Orly, Beauvais, Le Bourget, gares, Disneyland) depuis 2016. Marche a suivre : 1) calculer_prix avec les adresses et l heure exactes (heure de Paris) ; 2) presenter au client les vehicules disponibles et leur prix ; 3) recueillir prenom, nom, e-mail, telephone international, numero de vol ou de train, mode de paiement ; 4) recapituler et obtenir l accord explicite du client ; 5) seulement alors appeler reserver. Les prix sont fixes et calcules par le site : ne jamais en inventer ni en promettre un autre.…

endpoint
https://vtc-aeroport.fr/wp-json/sivtc/v1/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 vtc-aeroport-paris live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is vtc-aeroport-paris free to use?
Yes — the hub reached it with no key and no payment.
What tools does vtc-aeroport-paris have?
5 tools: suggerer_adresse, reserver, lire_reservation, calculer_prix, lister_vehicules.
Is vtc-aeroport-paris 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
605ms

last good check

priced tools
0

of 5 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

_ what it can do 5 tools
1 open 4 never probed 1 of 5 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.

  • lister_vehicules open 1h ago

    Liste les gammes de vehicules de VTC AEROPORT PARIS avec leur capacite (passagers, bagages) et leurs equipements.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • suggerer_adresse unknown never probed

    Propose des adresses completes a partir d un debut de saisie, pour confirmer l adresse exacte avec le client.

    mcp-tool

    {
  "type": "object",
  "required": [
    "recherche"
  ],
  "properties": {
    "recherche": {
      "type": "string",
      "description": "Debut d adresse, nom d hotel, de gare ou d aeroport."
    }
  }
}
    arguments 12 lines
  • reserver unknown never probed

    Enregistre la reservation pour le client. A appeler UNIQUEMENT apres calculer_prix et apres l accord explicite du client sur le recapitulatif. Le prix est recalcule par le site.

    mcp-tool

    {
  "type": "object",
  "required": [
    "vehicule_id",
    "depart",
    "date_heure",
    "client",
    "paiement",
    "accord_client"
  ],
  "properties": {
    "type": {
      "enum": [
        "transfert",
        "mise_a_disposition"
      ],
      "type": "string",
      "default": "transfert",
      "description": "transfert = d un point A a un point B ; mise_a_disposition = chauffeur a l heure."
    },
    "arrets": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 3,
      "description": "Optionnel : jusqu a 3 arrets intermediaires."
    },
    "client": {
      "type": "object",
      "required": [
        "prenom",
        "nom",
        "email",
        "telephone"
      ],
      "properties": {
        "nom": {
          "type": "string"
        },
        "vol": {
          "type": "string",
          "description": "Numero de vol ou de train (suivi des retards)."
        },
        "email": {
          "type": "string",
          "description": "Adresse e-mail du client, pour la confirmation."
        },
        "notes": {
          "type": "string",
          "description": "Siege bebe, pancarte, demande particuliere."
        },
        "prenom": {
          "type": "string"
        },
        "telephone": {
          "type": "string",
          "description": "Au format international, ex. +33612345678."
        }
      }
    },
    "depart": {
      "type": "string",
      "description": "Adresse complete de prise en charge (ex. « Aeroport Paris-Orly, Terminal 4 » ou « 12 rue de Rivoli, 75001 Paris »)."
    },
    "heures": {
      "type": "number",
      "minimum": 1,
      "description": "Nombre d heures, obligatoire pour une mise a disposition."
    },
    "retour": {
      "type": "string",
      "description": "Optionnel : date et heure du trajet retour (meme format) pour un aller-retour. Le prix renvoye est alors aller + retour."
    },
    "arrivee": {
      "type": "string",
      "description": "Adresse complete de destination. Inutile pour une mise a disposition."
    },
    "bagages": {
      "type": "integer",
      "default": 0,
      "maximum": 20,
      "minimum": 0
    },
    "paiement": {
      "enum": [
        "a_bord_carte",
        "a_bord_especes",
        "en_ligne"
      ],
      "type": "string",
      "description": "a_bord_carte ou a_bord_especes : regle au chauffeur, reservation confirmee ensuite par VTC AEROPORT PARIS. en_ligne : un lien de paiement est renvoye, la course est confirmee des le paiement."
    },
    "passagers": {
      "type": "integer",
      "default": 1,
      "maximum": 16,
      "minimum": 1
    },
    "date_heure": {
      "type": "string",
      "description": "Date et heure de prise en charge, heure de Paris, format ISO 8601 (ex. 2026-11-15T14:30:00)."
    },
    "vehicule_id": {
      "type": "integer",
      "description": "Identifiant du vehicule choisi, repris de la reponse de calculer_prix."
    },
    "accord_client": {
      "type": "boolean",
      "description": "Mettre true uniquement si le client a explicitement valide le recapitulatif (trajet, horaire, vehicule, prix)."
    }
  }
}
    arguments 113 lines
  • lire_reservation unknown 1h ago

    Donne l etat d une reservation deja faite. Demande le numero de reservation et l e-mail du client utilise pour la reservation.

    mcp-tool

    {
  "type": "object",
  "required": [
    "numero",
    "email"
  ],
  "properties": {
    "email": {
      "type": "string"
    },
    "numero": {
      "type": "integer"
    }
  }
}
    arguments 15 lines
  • calculer_prix unknown 1h ago

    Donne le prix fixe de chaque vehicule pour un trajet (ou une mise a disposition) a une date donnee. A appeler avant toute reservation. Les prix sont TTC, en euros.

    mcp-tool

    {
  "type": "object",
  "required": [
    "depart",
    "date_heure"
  ],
  "properties": {
    "type": {
      "enum": [
        "transfert",
        "mise_a_disposition"
      ],
      "type": "string",
      "default": "transfert",
      "description": "transfert = d un point A a un point B ; mise_a_disposition = chauffeur a l heure."
    },
    "arrets": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 3,
      "description": "Optionnel : jusqu a 3 arrets intermediaires."
    },
    "depart": {
      "type": "string",
      "description": "Adresse complete de prise en charge (ex. « Aeroport Paris-Orly, Terminal 4 » ou « 12 rue de Rivoli, 75001 Paris »)."
    },
    "heures": {
      "type": "number",
      "minimum": 1,
      "description": "Nombre d heures, obligatoire pour une mise a disposition."
    },
    "retour": {
      "type": "string",
      "description": "Optionnel : date et heure du trajet retour (meme format) pour un aller-retour. Le prix renvoye est alors aller + retour."
    },
    "arrivee": {
      "type": "string",
      "description": "Adresse complete de destination. Inutile pour une mise a disposition."
    },
    "bagages": {
      "type": "integer",
      "default": 0,
      "maximum": 20,
      "minimum": 0
    },
    "passagers": {
      "type": "integer",
      "default": 1,
      "maximum": 16,
      "minimum": 1
    },
    "date_heure": {
      "type": "string",
      "description": "Date et heure de prise en charge, heure de Paris, format ISO 8601 (ex. 2026-11-15T14:30:00)."
    }
  }
}
    arguments 59 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 238795d824ff0939.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/238795d824ff0939/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/238795d824ff0939/badge.svg)](https://brick.blue/agent/238795d824ff0939?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
90%

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.