# Selfe (remote · selfe.ai)

Find places to stay, eat and do, ranked for the question, with live availability and booking.

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

## Components

- remote · `selfe.ai`: 68/100 (this document), [markdown](https://verifymcp.io/servers/ai-selfe-registry/selfe.md), [page](https://verifymcp.io/servers/ai-selfe-registry/selfe)

## Channel facts

- Endpoint: `https://selfe.ai/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-11-21.

- **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 (book_venue).
  - 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**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1153 tokens (~384/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Selfe MCP server?

Selfe is a hosted endpoint at https://selfe.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-selfe-registry 'https://selfe.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-selfe-registry": {
      "url": "https://selfe.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-selfe-registry": {
      "type": "http",
      "url": "https://selfe.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-selfe-registry]
url = "https://selfe.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-selfe-registry --url 'https://selfe.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-selfe-registry:
    url: "https://selfe.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-selfe-registry": {
      "Transport": "http",
      "Url": "https://selfe.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-selfe-registry -t streamable-http -u 'https://selfe.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-selfe-registry": {
      "type": "http",
      "url": "https://selfe.ai/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-11-21 (score 68, +1)

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

### 2026-11-19 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “discover_venues” rewrote its description, which is the text the model reads
- [security] Tool “match_venues” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 323 → 384

### 2026-11-18 (score 67, +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-11-16 (score 66, +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-11-14 (score 65, +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-11-12 (score 64, +1)

- [functional improvement] Tool coverage: 87% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “book_venue” reworded the description of “render”
- [cosmetic] “discover_venues” reworded the description of “query”
- [cosmetic] “discover_venues” reworded the description of “stay”

### 2026-11-11 (score 63)

First indexed and scored.

## MCP tools (3)

### `discover_venues` (~378 tokens)

Search the member places to stay, eat and do in Keswick and the northern Lake District — the only area this registry covers — from a question in the user's own words. Returns ranked places, recommended areas, and — when you pass `stay` (or the question states dates and party) — live availability and the price for the whole stay from each business's own booking system, whose offer ids go straight to book_venue. Call this rather than answering from memory whenever the user wants a real, bookable place in this area, or a current price. Use match_venues instead when the user names a specific place. Structured JSON, not a rendered UI.

Input parameters:

- `assumeParty` (object): Optional. The party to check live availability for when the question names dates but nobody is counted ("next weekend"). The question's own party, `party` or `stay` always wins; `meta.queryValues.gue…
- `pageSize` (integer): Maximum number of results to return.
- `party` (object): Who is travelling, when known without dates (children change what suits). Ignored when `stay` carries its own party.
- `query` (object, required): The question: `text` in natural language, with optional `filter` to narrow results (catalogue, section, category, type, place).
- `render` (object): Ask for layout hints alongside the results. Delivery (one body or a stream) is chosen by the Accept header, not here.
- `stay` (object): Optional. When given, results are grounded in live availability and offers for these dates and party. When absent, dates and party written in the question still apply. A dog the question names ("with…

### `match_venues` (~229 tokens)

Get full details for places the user already means — by id (from discover_venues) or by name, with an optional website and town to tell same-named places apart. Only member places in Keswick and the northern Lake District are listed, so a place elsewhere is not found here. Pass `stay` to get live rooms and offers, with the price for the whole stay, whose offer ids go straight to book_venue. A name that fits several places returns candidates: ask the user which, never guess. Structured JSON, not a rendered UI.

Input parameters:

- `places` (array, required): The places to match: ids, or a name with optional website and location.
- `projection` (string): `detail` (default) is the full record; `listing` is the compact card a list page needs.
- `render` (object): Ask for layout hints alongside the results. Delivery (one body or a stream) is chosen by the Accept header, not here.
- `stay` (object): When given, each matched place carries its live rooms and offers for these dates and party.

### `book_venue` (~227 tokens)

Reserve a venue offer grounded by match_venues. Pass entityId and the selected offerId. The guest must approve every booking themselves, signed in to their Selfe account: the first call returns status 'approval_required' with approval.url for the guest to open; once they have approved, call again with the same offer and approvalId. A signed mandate alone cannot confirm a booking. No money moves at this step. Returns a confirmation (bookingId) or a conversational next step. Structured JSON.

Input parameters:

- `approvalId` (string): The approval the guest gave this offer in their own Selfe account, returned as approval.id when the booking first needed it. A booking is confirmed only with the guest's approval.
- `entityId` (string, required): The place id returned by discover or match.
- `mandate` (object): A signed AP2 Cart Mandate for a foreign caller, bound to this entity and offer.
- `offerId` (string, required): The opaque, sealed offer id returned by match.
- `render` (object): Ask for layout hints alongside the booking result. Optional.

## Diagnostics

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

## Score history

- 2026-11-21: 68
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 65
- 2026-11-14: 65
- 2026-11-13: 64
- 2026-11-12: 64
- 2026-11-11: 63

## Common questions

### What is the Selfe MCP server?

Selfe is an MCP server listed in the public MCP registry as ai.selfe/registry. Find places to stay, eat and do, ranked for the question, with live availability and booking. This page covers its hosted endpoint (https://selfe.ai/mcp).

### Is the Selfe MCP server safe to use?

Selfe scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Selfe MCP server expose?

Selfe exposes 3 tools: discover_venues, match_venues, book_venue. Their descriptions and schemas cost roughly 834 tokens of context every time the server is loaded.

### Does the Selfe MCP server require authentication?

No. We connected to Selfe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Selfe MCP server still maintained?

Selfe is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Selfe MCP server?

VerifyMCP ran 13 checks on Selfe, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://selfe.ai/mcp
- Website: https://selfe.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-selfe-registry/selfe.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-selfe-registry/selfe/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-selfe-registry/selfe.json
- HTML version of this page: https://verifymcp.io/servers/ai-selfe-registry/selfe
