# eenable — a shop with no checkout (remote · eenable.me)

Buy 15 minutes of Alex Finger's time, or an AI Repellent certificate. Agents only.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `eenable.me`: 66/100 (this document), [markdown](https://verifymcp.io/servers/me-eenable-shop/eenable.md), [page](https://verifymcp.io/servers/me-eenable-shop/eenable)

## Channel facts

- Endpoint: `https://eenable.me/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_order).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2724 tokens (~170/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http me-eenable-shop https://eenable.me/mcp
```

### Codex

```toml
[mcp_servers.me-eenable-shop]
url = "https://eenable.me/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-eenable-shop": {
      "type": "remote",
      "url": "https://eenable.me/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-eenable-shop --url https://eenable.me/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-eenable-shop:
    url: "https://eenable.me/mcp"
```

### Other

```json
{
  "mcpServers": {
    "me-eenable-shop": {
      "type": "http",
      "url": "https://eenable.me/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-17 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-13 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-12 (score 62)

First indexed and scored.

## MCP tools (16)

### `get_shop_info` (~35 tokens)

Shop information

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

### `list_products` (~76 tokens)

Session types

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.

### `check_availability` (~120 tokens)

Check availability

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.

Input parameters:

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

### `create_order` (~554 tokens)

Create an order

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.

Input parameters:

- `background` (string): Anything the buyer wants the seller to read beforehand: context, links, what they have already tried. Shown in the calendar invitation.
- `buyer_confirmed_session` (boolean, required): 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 t…
- `catalogue_token` (string, required): 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): 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.
- `email` (string, required): Buyer's email — receives the calendar invitation
- `name` (string, required): Buyer's name, as it should appear on the invite
- `session_type` (string, required): 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 th…
- `slot_id` (string): 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): Buyer's IANA timezone
- `topic` (string): 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.

### `get_order_status` (~180 tokens)

Check order status

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.

Input parameters:

- `order_id` (string, required): The ord_… id from create_order
- `wait_seconds` (integer): 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.

### `get_order_details` (~36 tokens)

Get booking details

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

Input parameters:

- `order_id` (string, required)

### `get_booking` (~82 tokens)

Get booking details (old name)

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.

Input parameters:

- `order_id` (string, required)

### `cancel_order` (~94 tokens)

Cancel a booking

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.

Input parameters:

- `email` (string, required): Must match the order's email
- `order_id` (string, required)

### `cancel_booking` (~139 tokens)

Cancel a booking (old name)

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.

Input parameters:

- `email` (string, required): Must match the order's email
- `order_id` (string, required)

### `order_certificate` (~218 tokens)

Order a certificate

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.

Input parameters:

- `buyer_confirmed_choice` (boolean, required): 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.
- `catalogue_token` (string, required): 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.
- `certificate_id` (string, required): Which certificate. From list_products: ai-repellent.
- `email` (string, required): Buyer's email — the certificate is sent there
- `name` (string, required): Buyer's name, as it should appear on the certificate as the bearer

### `transfer_certificate` (~169 tokens)

Transfer a certificate to a new bearer

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.

Input parameters:

- `new_bearer_email` (string, required): The new bearer's email — the endorsed certificate is sent there
- `new_bearer_name` (string, required): Who it is passing to, as they should appear on the certificate
- `order_id` (string, required): The order number of the certificate being transferred, from the PDF

### `renounce_certificate` (~177 tokens)

Renounce a certificate

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.

Input parameters:

- `order_id` (string, required): The order number printed on the certificate. No email is required: the certificate is a bearer instrument, so whoever holds it may renounce it.

### `update_order_details` (~178 tokens)

Update what a booking is about

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.

Input parameters:

- `background` (string): Replaces the background the seller should read first
- `desired_outcome` (string): Replaces what they want to walk away with
- `email` (string, required): Must match the order's email
- `order_id` (string, required)
- `session_type` (string): Switch to a different session type
- `topic` (string): Replaces what they want to discuss

### `update_booking` (~224 tokens)

Update what a booking is about (old name)

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.

Input parameters:

- `background` (string): Replaces the background the seller should read first
- `desired_outcome` (string): Replaces what they want to walk away with
- `email` (string, required): Must match the order's email
- `order_id` (string, required)
- `session_type` (string): Switch to a different session type
- `topic` (string): Replaces what they want to discuss

### `reschedule_session` (~79 tokens)

Reschedule a booking

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.

Input parameters:

- `email` (string, required): Must match the order's email
- `new_slot_id` (string, required): A slot_id from check_availability
- `order_id` (string, required)

### `reschedule_booking` (~126 tokens)

Reschedule a booking (old name)

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.

Input parameters:

- `email` (string, required): Must match the order's email
- `new_slot_id` (string, required): A slot_id from check_availability
- `order_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-eenable-shop/eenable#diagnostics

## Score history

- 2026-08-20: 66
- 2026-08-19: 66
- 2026-08-18: 65
- 2026-08-17: 65
- 2026-08-16: 64
- 2026-08-15: 64
- 2026-08-14: 63
- 2026-08-13: 63
- 2026-08-12: 62

## Links

- Remote endpoint: https://eenable.me/mcp
- Website: https://eenable.me/
- Changelog RSS feed: https://verifymcp.io/servers/me-eenable-shop/eenable.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-eenable-shop/eenable.json
- HTML version of this page: https://verifymcp.io/servers/me-eenable-shop/eenable