Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
eenable — a shop with no checkout is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Buy 15 minutes of Alex Finger's time, or an AI Repellent certificate. Agents only.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http eenable-a-shop-with-no-checkout-mcp https://eenable.me/mcp
# 2 — ask your agent for something these tools do
# get_shop_info, list_products, check_availability and 13 more
eenable — a shop with no checkout costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http eenable-a-shop-with-no-checkout-mcp https://eenable.me/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
What this shop sells, the price, and how buying works. Call this first if you have not dealt with this shop before.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | ISO date or datetime, e.g. 2026-08-10 |
| to | string | no | ISO date or datetime, e.g. 2026-08-17 |
| timezone | string | no | Buyer's IANA timezone, e.g. Europe/London, for a second set of times |
| limit | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Buyer's email — receives the calendar invitation | |
| name | string | yes | Buyer's name, as it should appear on the invite |
| slot_id | string | no | A slot_id exactly as returned by check_availability. Required for the four session types; omit entirely for products that are not appointments. |
| session_type | string | yes | 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 |
| catalogue_token | string | yes | 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. |
| buyer_confirmed_session | boolean | yes | 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 th |
| background | string | no | Anything the buyer wants the seller to read beforehand: context, links, what they have already tried. Shown in the calendar invitation. |
| topic | string | no | 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. |
| desired_outcome | string | no | 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. |
| timezone | string | no | Buyer's IANA timezone |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | The ord_… id from create_order |
| wait_seconds | integer | no | 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. |
The Teams joining link and meeting details for a paid order. Available only once payment has settled.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
| string | yes | Must match the order's email |
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 rev
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
| string | yes | Must match the order's email |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Buyer's email — the certificate is sent there | |
| name | string | yes | Buyer's name, as it should appear on the certificate as the bearer |
| certificate_id | string | yes | Which certificate. From list_products: ai-repellent. |
| catalogue_token | string | yes | 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 | yes | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | The order number of the certificate being transferred, from the PDF |
| new_bearer_name | string | yes | Who it is passing to, as they should appear on the certificate |
| new_bearer_email | string | yes | The new bearer's email — the endorsed certificate is sent there |
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 call
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | The order number printed on the certificate. No email is required: the certificate is a bearer instrument, so whoever holds it may renounce it. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
| string | yes | Must match the order's email | |
| session_type | string | no | Switch to a different session type |
| topic | string | no | Replaces what they want to discuss |
| desired_outcome | string | no | Replaces what they want to walk away with |
| background | string | no | Replaces the background the seller should read first |
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 th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
| string | yes | Must match the order's email | |
| session_type | string | no | Switch to a different session type |
| topic | string | no | Replaces what they want to discuss |
| desired_outcome | string | no | Replaces what they want to walk away with |
| background | string | no | Replaces the background the seller should read first |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
| string | yes | Must match the order's email | |
| new_slot_id | string | yes | A slot_id from check_availability |
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | — |
| string | yes | Must match the order's email | |
| new_slot_id | string | yes | A slot_id from check_availability |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install eenable — a shop with no checkout or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish eenable — a shop with no checkout can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.