# SesApp Access Sheets (remote · sesapp.fr)

Housing access sheets behind revocable guest links. x402 on Base.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-23

## Components

- remote · `sesapp.fr`: 80/100 (this document), [markdown](https://verifymcp.io/servers/fr-sesapp-fiches/sesapp.md), [page](https://verifymcp.io/servers/fr-sesapp-fiches/sesapp)

## Channel facts

- Endpoint: `https://sesapp.fr/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-09-23.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2097 tokens (~139/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_fiche" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SesApp Access Sheets MCP server?

SesApp Access Sheets is a hosted endpoint at https://sesapp.fr/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 fr-sesapp-fiches 'https://sesapp.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-sesapp-fiches": {
      "url": "https://sesapp.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-sesapp-fiches": {
      "type": "http",
      "url": "https://sesapp.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-sesapp-fiches]
url = "https://sesapp.fr/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add fr-sesapp-fiches --url 'https://sesapp.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-sesapp-fiches:
    url: "https://sesapp.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-sesapp-fiches": {
      "Transport": "http",
      "Url": "https://sesapp.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-sesapp-fiches -t streamable-http -u 'https://sesapp.fr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fr-sesapp-fiches": {
      "type": "http",
      "url": "https://sesapp.fr/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-09-22 (score 80, +1)

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

### 2026-09-20 (score 79, +1)

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

### 2026-09-18 (score 78, +1)

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

### 2026-09-15 (score 77, +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-09-13 (score 76, +1)

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

### 2026-09-12 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “create_fiche” reworded the description of “instructions”
- [cosmetic] “update_fiche” reworded the description of “instructions”

### 2026-09-11 (score 75, +1)

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

### 2026-09-09 (score 74, +1)

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

## MCP tools (15)

### `subscribe` (~71 tokens)

Subscribe or renew. plan=agent (15 USDC, 20 sheets), fleet (79 USDC, 200), platform (250 USDC, fair-use). Send PAYMENT-SIGNATURE (x402 v2). Returns a Bearer JWT.

Input parameters:

- `plan` (string): SKU to purchase. Default agent.

### `status` (~32 tokens)

Current agent plan, expiry, fichesCount, maxFiches, overageUsdc. Requires Authorization: Bearer.

### `geocode` (~80 tokens)

Resolve a postal address to formattedAddress + lat/lon for create_fiche (cover map and 150 m WiFi geofence). Optional country ISO2. Requires Bearer.

Input parameters:

- `country` (string): Optional ISO 3166-1 alpha-2, e.g. fr
- `query` (string, required): Address search, min 3 characters

### `list_fiches` (~24 tokens)

List access sheets owned by the authenticated agent. Requires Authorization: Bearer.

### `create_fiche` (~597 tokens)

Create an access sheet. Write the guest flip-book in `instructions` (Markdown; guest language, usually French). Cover (map/name/address/accessCode) is auto. Pages: --- . Photos: ![alt](https://...). Intents: [Add WiFi](sesapp:wifi) or [Ajouter le WiFi](sesapp:wifi) + wifiName/wifiPassword; [Add contact](sesapp:contact) or [Ajouter le contact](sesapp:contact) + phoneNumber. Never put wifiPassword in Markdown (150 m GPS). Optional `locale` fr|en for guest chrome. Playbook: GET /llms.txt. Requires Bearer. Beyond quota, retry with PAYMENT-SIGNATURE (0.50 USDC on Agent, 0.25 on Fleet).

Input parameters:

- `accessCode` (string): Shown on the generated cover.
- `formattedAddress` (string, required)
- `instructions` (string): Markdown flip-book shown to the guest (this field). Cover (map, name, formattedAddress, accessCode) is generated — do not repeat it here. Split pages with a line containing only --- . Supported: # ##…
- `lat` (number): Cover map + WiFi geofence (150 m).
- `locale` (string): Guest chrome language. Markdown stays as written. Omit to follow Accept-Language / ?lang=.
- `lon` (number): Cover map + WiFi geofence (150 m).
- `name` (string, required)
- `phoneNumber` (string): Required for sesapp:contact. E.164 preferred.
- `wifiName` (string): SSID for sesapp:wifi. Hidden until 150 m if wifiPassword is set.
- `wifiPassword` (string): Do not put in instructions. Unlocked within 150 m.

### `get_fiche` (~35 tokens)

Get one owned access sheet by id (same fields as list_fiches). Requires Bearer.

Input parameters:

- `id` (string, required)

### `update_fiche` (~467 tokens)

Update an owned access sheet. Same fields as create_fiche. Typical: update instructions with photos/links. Requires Bearer.

Input parameters:

- `accessCode` (string): Shown on the generated cover.
- `formattedAddress` (string)
- `id` (string, required)
- `instructions` (string): Markdown flip-book shown to the guest (this field). Cover (map, name, formattedAddress, accessCode) is generated — do not repeat it here. Split pages with a line containing only --- . Supported: # ##…
- `lat` (number): Cover map + WiFi geofence (150 m).
- `locale` (string): Guest chrome language. Markdown stays as written. Omit to follow Accept-Language / ?lang=.
- `lon` (number): Cover map + WiFi geofence (150 m).
- `name` (string)
- `phoneNumber` (string): Required for sesapp:contact. E.164 preferred.
- `wifiName` (string): SSID for sesapp:wifi. Hidden until 150 m if wifiPassword is set.
- `wifiPassword` (string): Do not put in instructions. Unlocked within 150 m.

### `delete_fiche` (~30 tokens)

Delete an owned access sheet and its share links. Requires Bearer.

Input parameters:

- `id` (string, required)

### `share_fiche` (~71 tokens)

Create a revocable guest link. Optional expiresAt (ISO). WiFi password is never in Markdown: guests unlock it within 150 m of lat/lon. Requires Bearer.

Input parameters:

- `expiresAt` (string): ISO datetime, optional. Omit for no expiry.
- `id` (string, required)

### `list_shares` (~40 tokens)

List guest links for a fiche (token, url, expiresAt, viewCount, createdAt). Requires Bearer.

Input parameters:

- `id` (string, required)

### `revoke_share` (~65 tokens)

Revoke a guest share token. Optional delayDays (1–365) keeps the link until then (soft revoke). Requires Bearer.

Input parameters:

- `delayDays` (number): If set, the link expires after N days instead of being deleted now.
- `token` (string, required)

### `register_webhook` (~114 tokens)

Fleet/Platform only. Register an HTTPS endpoint. Events: fiche.viewed, share.created, share.revoked, wifi.unlocked, quota.warning. HMAC SHA-256 in X-SesApp-Signature (t=unix,v1=hex of timestamp.body). Secret returned once. Max 5 endpoints. Requires Bearer.

Input parameters:

- `events` (array): Subset of events. Default: all.
- `url` (string, required): HTTPS URL (http://127.0.0.1 allowed in DEV)

### `list_webhooks` (~26 tokens)

List webhook endpoints (secret is never returned). Fleet/Platform. Requires Bearer.

### `update_webhook` (~53 tokens)

Update url, events, or active. Fleet/Platform. Requires Bearer.

Input parameters:

- `active` (boolean)
- `events` (array)
- `id` (string, required)
- `url` (string)

### `delete_webhook` (~29 tokens)

Delete a webhook endpoint. Fleet/Platform. Requires Bearer.

Input parameters:

- `id` (string, required)

## Diagnostics

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

## Score history

- 2026-09-23: 80
- 2026-09-22: 80
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72

## Common questions

### What is the SesApp Access Sheets MCP server?

SesApp Access Sheets is an MCP server listed in the public MCP registry as fr.sesapp/fiches. Housing access sheets behind revocable guest links. x402 on Base. This page covers its hosted endpoint (https://sesapp.fr/mcp).

### Is the SesApp Access Sheets MCP server safe to use?

SesApp Access Sheets scores 80 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 SesApp Access Sheets MCP server expose?

SesApp Access Sheets exposes 15 tools: subscribe, status, geocode, list_fiches, create_fiche, and 10 more. Their descriptions and schemas cost roughly 1,734 tokens of context every time the server is loaded.

### Does the SesApp Access Sheets MCP server require authentication?

Yes. SesApp Access Sheets asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the SesApp Access Sheets MCP server still maintained?

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

## Links

- Remote endpoint: https://sesapp.fr/mcp
- Website: https://sesapp.fr/
- Changelog RSS feed: https://verifymcp.io/servers/fr-sesapp-fiches/sesapp.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-sesapp-fiches/sesapp.json
- HTML version of this page: https://verifymcp.io/servers/fr-sesapp-fiches/sesapp