SesApp Access Sheets
REMOTE · SESAPP.FR · SCANNED SEP 23
Housing access sheets behind revocable guest links. x402 on Base.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · sesapp.fr
claude mcp add --transport http fr-sesapp-fiches 'https://sesapp.fr/mcp'
{
"mcpServers": {
"fr-sesapp-fiches": {
"url": "https://sesapp.fr/mcp"
}
}
} {
"servers": {
"fr-sesapp-fiches": {
"type": "http",
"url": "https://sesapp.fr/mcp"
}
}
} [mcp_servers.fr-sesapp-fiches] url = "https://sesapp.fr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-sesapp-fiches": {
"type": "remote",
"url": "https://sesapp.fr/mcp",
"enabled": true
}
}
} openclaw mcp add fr-sesapp-fiches --url 'https://sesapp.fr/mcp' --transport streamable-http
mcp_servers:
fr-sesapp-fiches:
url: "https://sesapp.fr/mcp" {
"McpServers": {
"fr-sesapp-fiches": {
"Transport": "http",
"Url": "https://sesapp.fr/mcp"
}
}
} assistant mcp add fr-sesapp-fiches -t streamable-http -u 'https://sesapp.fr/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 12 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “create_fiche” reworded the description of “instructions” cosmetic
- “update_fiche” reworded the description of “instructions” cosmetic
- 11 Sept 26 +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.
- 9 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Probed https://sesapp.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sesapp.fr | CN=YR1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 4096 | SHA256-RSA | 61d6923310f70f2a715813d24e6c4dd4548 |
| SANs: sesapp.fr, www.sesapp.fr | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sesapp.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| sesapp.fr. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://apis.google.com https://connect.facebook.net https://www.google.com https://www.gstatic.com https://t.contentsquare.net https://app.contentsquare.com https://www.googletagmanager.com https://consent.cookiebot.com https://consentcdn.cookiebot.com https://unpkg.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://www.youtube.com https://s.ytimg.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://unpkg.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https: blob:; connect-src 'self' https: wss:; frame-src 'self' https://accounts.google.com https://www.facebook.com https://docs.google.com https://consent.cookiebot.com https://consentcdn.cookiebot.com https://player.twitch.tv https://www.youtube.com https://www.youtube-nocookie.com https://www.openstreetmap.org; media-src 'self' blob: data:; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sesapp.fr/mcp | Verified | 200 | |
| http (plaintext) | http://sesapp.fr/mcp | HTTPS enforced | 301 | https://sesapp.fr/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_fiche ~597
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: . 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).
| Name | Type | Req | Description |
|---|---|---|---|
| accessCode | string | – | Shown on the generated cover. |
| formattedAddress | string | yes | – |
| 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 | yes | – |
| 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. |
No output schema declared.
No examples provided.
delete_fiche ~30
Delete an owned access sheet and its share links. Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_webhook ~29
Delete a webhook endpoint. Fleet/Platform. Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
geocode ~80
Resolve a postal address to formattedAddress + lat/lon for create_fiche (cover map and 150 m WiFi geofence). Optional country ISO2. Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO 3166-1 alpha-2, e.g. fr |
| query | string | yes | Address search, min 3 characters |
No output schema declared.
No examples provided.
get_fiche ~35
Get one owned access sheet by id (same fields as list_fiches). Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_fiches ~24
List access sheets owned by the authenticated agent. Requires Authorization: Bearer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_shares ~40
List guest links for a fiche (token, url, expiresAt, viewCount, createdAt). Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_webhooks ~26
List webhook endpoints (secret is never returned). Fleet/Platform. Requires Bearer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_webhook ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Subset of events. Default: all. |
| url | string | yes | HTTPS URL (http://127.0.0.1 allowed in DEV) |
No output schema declared.
No examples provided.
revoke_share ~65
Revoke a guest share token. Optional delayDays (1–365) keeps the link until then (soft revoke). Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| delayDays | number | – | If set, the link expires after N days instead of being deleted now. |
| token | string | yes | – |
No output schema declared.
No examples provided.
share_fiche ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | – | ISO datetime, optional. Omit for no expiry. |
| id | string | yes | – |
No output schema declared.
No examples provided.
status ~32
Current agent plan, expiry, fichesCount, maxFiches, overageUsdc. Requires Authorization: Bearer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
subscribe ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | – | SKU to purchase. Default agent. |
No output schema declared.
No examples provided.
update_fiche ~467
Update an owned access sheet. Same fields as create_fiche. Typical: update instructions with photos/links. Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| accessCode | string | – | Shown on the generated cover. |
| formattedAddress | string | – | – |
| id | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
update_webhook ~53
Update url, events, or active. Fleet/Platform. Requires Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | – |
| events | array | – | – |
| id | string | yes | – |
| url | string | – | – |
No output schema declared.
No examples provided.
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.