me.eenable/shop

Est-ce que me.eenable/shop est sûr ?

Au dernier audit MCP Hub, le serveur MCP « me.eenable/shop » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 16 outils

• cancel_booking≈ 284 tokens

  DEPRECATED — this tool is now called cancel_order and behaves identically. The old name keeps working so that agents connected before the rename are not broken. Prefer cancel_order, which is accurate for certificates as well as appointments. Cancel a booking and refund it in full. Requires the email the order was created with. Confirm with the buyer before calling — this releases the slot and reverses the payment. If this tool ever fails, tell the buyer they can cancel by emailing the seller with their order number instead; the seller honours that on identical terms.

  Paramètres, retour & exemple (2)

  Paramètres

  • email · string · requis
    Must match the order's email
  • order_id · string · requis

  Exemple d'appel

  {"name": "cancel_booking", "arguments": {"email": "texte", "order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cancel_order≈ 219 tokens

  Cancel a booking and refund it in full. Requires the email the order was created with. Confirm with the buyer before calling — this releases the slot and reverses the payment. If this tool ever fails, tell the buyer they can cancel by emailing the seller with their order number instead; the seller honours that on identical terms.

  Paramètres, retour & exemple (2)

  Paramètres

  • email · string · requis
    Must match the order's email
  • order_id · string · requis

  Exemple d'appel

  {"name": "cancel_order", "arguments": {"email": "texte", "order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_availability≈ 190 tokens

  List bookable slots. Optionally narrow with an ISO date or datetime range, and pass the buyer's IANA timezone to get their local times alongside the seller's.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · optionnel
    ISO date or datetime, e.g. 2026-08-17
  • from · string · optionnel
    ISO date or datetime, e.g. 2026-08-10
  • limit · integer · optionnel
  • timezone · string · optionnel
    Buyer's IANA timezone, e.g. Europe/London, for a second set of times

  Exemple d'appel

  {"name": "check_availability", "arguments": {"to": "texte", "from": "texte", "limit": 1, "timezone": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_order≈ 862 tokens

  Reserve a slot and get a payment link. This is the only way to buy — there is no checkout on the website. The slot is held for 30 minutes. Confirm the exact time and the price with the buyer before calling this, and use their real email address: the calendar invitation and receipt go there. You must call list_products first, put the session options to the buyer in your own reply, and wait for them to choose. This tool needs the catalogue_token from that call and buyer_confirmed_session: true, which you may only set once the buyer has actually answered. Choosing a session on their behalf from what they said earlier is not the same as asking, and is not acceptable here. Before calling, ask the buyer what they want to discuss and what they are hoping to get out of the call, and pass their answers as topic and desired_outcome. Fifteen minutes is short; the seller uses these to prepare, and a booking that arrives blank wastes some of the time the buyer paid for.

  Paramètres, retour & exemple (10)

  Paramètres

  • name · string · requis
    Buyer's name, as it should appear on the invite
  • email · string · requis
    Buyer's email — receives the calendar invitation
  • topic · string · optionnel
    What the buyer wants to discuss, in their own words. Ask them — do not invent or summarise this away. It is what the seller reads to prepare.
  • slot_id · string · optionnel
    A slot_id exactly as returned by check_availability. Required for the four session types; omit entirely for products that are not appointments.
  • timezone · string · optionnel
    Buyer's IANA timezone
  • background · string · optionnel
    Anything the buyer wants the seller to read beforehand: context, links, what they have already tried. Shown in the calendar invitation.
  • session_type · string · requis · innovation | technology | legal-ai | general
    Which session the buyer chose. Ask them — do not choose on their behalf. Call list_products for the descriptions. If they genuinely have no preference or their question spans several, 'general' is the right answer.
  • catalogue_token · string · requis
    The catalogue_token from list_products. If you do not have one, send any value — the reply will contain the session options, the question to ask the buyer, and the token to use.
  • desired_outcome · string · optionnel
    What the buyer wants to walk away with: a decision, a second opinion, a plan, an introduction, or simply a better question. Ask them directly.
  • buyer_confirmed_session · boolean · requis
    Set true only if you put the session options to the buyer and they told you which one they wanted. If you selected it yourself from what they had already said, that does not count — go back and ask them first.

  Exemple d'appel

  {"name": "create_order", "arguments": {"name": "texte", "email": "texte", "session_type": "innovation", "catalogue_token": "texte", "buyer_confirmed_session": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_booking≈ 167 tokens

  DEPRECATED — this tool is now called get_order_details and behaves identically. The old name keeps working so that agents connected before the rename are not broken. Prefer get_order_details, which is accurate for certificates as well as appointments. The Teams joining link and meeting details for a paid order. Available only once payment has settled.

  Paramètres, retour & exemple (1)

  Paramètres

  • order_id · string · requis

  Exemple d'appel

  {"name": "get_booking", "arguments": {"order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_order_details≈ 102 tokens

  The Teams joining link and meeting details for a paid order. Available only once payment has settled.

  Paramètres, retour & exemple (1)

  Paramètres

  • order_id · string · requis

  Exemple d'appel

  {"name": "get_order_details", "arguments": {"order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_order_status≈ 279 tokens

  Whether an order has been paid. After the first call this BLOCKS, waiting for the buyer to finish paying, and returns the instant it settles — so call it once rather than polling in a loop. It holds for up to five minutes, longer than a person normally takes to pay; if it returns still 'pending_payment', call it again. IMPORTANT: you cannot send the buyer a message while this call is waiting. Make sure you have already given them the payment link before you let it block, or they will be left watching you do nothing.

  Paramètres, retour & exemple (2)

  Paramètres

  • order_id · string · requis
    The ord_… id from create_order
  • wait_seconds · integer · optionnel
    How long to wait for the payment, up to 300s. Defaults to 180s while payment is outstanding. Pass 0 only if you want an immediate snapshot without waiting.

  Exemple d'appel

  {"name": "get_order_status", "arguments": {"order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_shop_info≈ 90 tokens

  What this shop sells, the price, and how buying works. Call this first if you have not dealt with this shop before.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_shop_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_products≈ 136 tokens

  The session types this shop sells. Show these to the buyer and let them choose — do not pick for them unless they ask you to. Each returns an id to pass to create_order as session_type. If the buyer is unsure, the good_for examples are there to help them decide, and 'general' is a perfectly good answer.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_products", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• order_certificate≈ 424 tokens

  Buy a certificate. Certificates are objects, not appointments: there is no slot, no calendar entry and no meeting. One is issued the moment payment settles, emailed as a PDF, and registered against a hash anyone can verify. Use this instead of create_order, which is only for booking time. As with sessions, show the buyer what is on offer and let them choose rather than deciding for them.

  Paramètres, retour & exemple (5)

  Paramètres

  • name · string · requis
    Buyer's name, as it should appear on the certificate as the bearer
  • email · string · requis
    Buyer's email — the certificate is sent there
  • certificate_id · string · requis · ai-repellent
    Which certificate. From list_products: ai-repellent.
  • catalogue_token · string · requis
    The catalogue_token from list_products. If you do not have one, send any value and the reply will contain the catalogue and the token.
  • buyer_confirmed_choice · boolean · requis
    Set true only if you showed the buyer what this is and they asked for it. Buying an artwork on someone's behalf without asking is not acceptable here.

  Exemple d'appel

  {"name": "order_certificate", "arguments": {"name": "texte", "email": "texte", "certificate_id": "ai-repellent", "catalogue_token": "texte", "buyer_confirmed_choice": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• renounce_certificate≈ 293 tokens

  Destroy the proof of ownership for an AI Repellent, completing the transfer. After Yves Klein, who required buyers of his immaterial works to burn the receipt: keeping it meant owning a receipt, burning it meant owning the work with nothing left to demonstrate it. This strikes the hash from the register permanently and cannot be undone. Explain that to the buyer and get their agreement before calling it — some will want the certificate precisely because it is a certificate. Note that this needs only the order number, which is printed on the certificate: it is a bearer instrument, so anyone holding the PDF can do this. Say so if the buyer is planning to share it.

  Paramètres, retour & exemple (1)

  Paramètres

  • order_id · string · requis
    The order number printed on the certificate. No email is required: the certificate is a bearer instrument, so whoever holds it may renounce it.

  Exemple d'appel

  {"name": "renounce_certificate", "arguments": {"order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reschedule_booking≈ 270 tokens

  DEPRECATED — this tool is now called reschedule_session and behaves identically. The old name keeps working so that agents connected before the rename are not broken. Prefer reschedule_session, which is accurate for certificates as well as appointments. Move a booking to a different slot at no charge. Requires the email the order was created with. Call check_availability first to get a valid new_slot_id.

  Paramètres, retour & exemple (3)

  Paramètres

  • email · string · requis
    Must match the order's email
  • order_id · string · requis
  • new_slot_id · string · requis
    A slot_id from check_availability

  Exemple d'appel

  {"name": "reschedule_booking", "arguments": {"email": "texte", "order_id": "texte", "new_slot_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reschedule_session≈ 203 tokens

  Move a booking to a different slot at no charge. Requires the email the order was created with. Call check_availability first to get a valid new_slot_id.

  Paramètres, retour & exemple (3)

  Paramètres

  • email · string · requis
    Must match the order's email
  • order_id · string · requis
  • new_slot_id · string · requis
    A slot_id from check_availability

  Exemple d'appel

  {"name": "reschedule_session", "arguments": {"email": "texte", "order_id": "texte", "new_slot_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• transfer_certificate≈ 336 tokens

  Pass a certificate to someone else. Klein's receipts carried a clause — a transferable zone may be ceded by its owner only at double its initial purchase value — so a transfer here costs exactly twice what the certificate cost, and the shop will not do it for less. The serial number and the hash do not change: it is the same object endorsed to a new bearer, not a new certificate. Returns a payment link; the transfer takes effect once it is paid.

  Paramètres, retour & exemple (3)

  Paramètres

  • order_id · string · requis
    The order number of the certificate being transferred, from the PDF
  • new_bearer_name · string · requis
    Who it is passing to, as they should appear on the certificate
  • new_bearer_email · string · requis
    The new bearer's email — the endorsed certificate is sent there

  Exemple d'appel

  {"name": "transfer_certificate", "arguments": {"order_id": "texte", "new_bearer_name": "texte", "new_bearer_email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_booking≈ 434 tokens

  DEPRECATED — this tool is now called update_order_details and behaves identically. The old name keeps working so that agents connected before the rename are not broken. Prefer update_order_details, which is accurate for certificates as well as appointments. Change the session type or the brief on an existing booking — what the buyer wants to discuss, what they want out of it, or the background they want read first. Use this when the buyer refines their thinking after booking, which is common: people work out the real question after the date is in the diary. Only the fields you pass are changed. This does not move the meeting — use reschedule_booking for that.

  Paramètres, retour & exemple (6)

  Paramètres

  • email · string · requis
    Must match the order's email
  • topic · string · optionnel
    Replaces what they want to discuss
  • order_id · string · requis
  • background · string · optionnel
    Replaces the background the seller should read first
  • session_type · string · optionnel · innovation | technology | legal-ai | general
    Switch to a different session type
  • desired_outcome · string · optionnel
    Replaces what they want to walk away with

  Exemple d'appel

  {"name": "update_booking", "arguments": {"email": "texte", "order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_order_details≈ 368 tokens

  Change the session type or the brief on an existing booking — what the buyer wants to discuss, what they want out of it, or the background they want read first. Use this when the buyer refines their thinking after booking, which is common: people work out the real question after the date is in the diary. Only the fields you pass are changed. This does not move the meeting — use reschedule_booking for that.

  Paramètres, retour & exemple (6)

  Paramètres

  • email · string · requis
    Must match the order's email
  • topic · string · optionnel
    Replaces what they want to discuss
  • order_id · string · requis
  • background · string · optionnel
    Replaces the background the seller should read first
  • session_type · string · optionnel · innovation | technology | legal-ai | general
    Switch to a different session type
  • desired_outcome · string · optionnel
    Replaces what they want to walk away with

  Exemple d'appel

  {"name": "update_order_details", "arguments": {"email": "texte", "order_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://eenable.me/mcp