Skip to content

SesApp Access Sheets MCP server

fr.sesapp/fichessesapp.frstreamable-httpv1.1.0Scanned

Housing access sheets via guest links. REST+MCP+x402 on Base.

15 tools: 3 can delete or cancel things, 6 change things and 6 only read.

Tools: 3 delete, 0 irreversible, 6 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 4
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SesApp Access Sheets MCP server can do

The SesApp Access Sheets MCP server is published by sesapp.fr, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (3 tools: delete_fiche, revoke_share and delete_webhook) and create or change data (6 tools: subscribe, create_fiche, update_fiche, share_fiche and 2 more). 6 tools only read.

1 tool reads private data (list_webhooks); 1 tool brings in text other people can write (list_shares); 4 tools can send data out of your system (create_fiche, update_fiche, register_webhook and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 3Claude Code: deny
  • delete_ficheDelete an owned access sheet and its share links.No findings

    Why it is in this group

    • The name "delete_fiche" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete an owned access sheet and its share links. Requires Bearer.
  • delete_webhookDelete a webhook endpoint.No findings

    Why it is in this group

    • The name "delete_webhook" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete a webhook endpoint. Fleet/Platform. Requires Bearer.
  • revoke_shareRevoke a guest share token.No findings

    Why it is in this group

    • The name "revoke_share" says "revoke": a word for removing or ending something.
    Description, as the server wrote it
    Revoke a guest share token. Optional delayDays (1–365) keeps the link until then (soft revoke). Requires Bearer.
Changes things 6Claude Code: ask
  • create_ficheCreate an access sheet.Can send data outNo findings

    Why it is in this group

    • The name "create_fiche" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phoneNumber): what the tool writes goes there.
    Description, as the server wrote it
    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).
  • register_webhookFleet/Platform only.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • share_ficheCreate a revocable guest link.No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    Description, as the server wrote it
    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.
  • subscribeSubscribe or renew.No findings

    Why it is in this group

    • The name "subscribe" says "subscribe": a word for a change.
    Description, as the server wrote it
    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.
  • update_ficheUpdate an owned access sheet.Can send data outNo findings

    Why it is in this group

    • The name "update_fiche" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phoneNumber): what the tool writes goes there.
    Description, as the server wrote it
    Update an owned access sheet. Same fields as create_fiche. Typical: update instructions with photos/links. Requires Bearer.
  • update_webhookUpdate url, events, or active.Can send data outNo findings

    Why it is in this group

    • The name "update_webhook" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Update url, events, or active. Fleet/Platform. Requires Bearer.
Only reads 6Show 6 read-only tools
  • geocodeResolve a postal address to formattedAddress + lat/lon for create_fiche (cover map and 150 m WiFi geofence).No findings

    Why it is in this group

    • The description's first verb is "resolve": a word for reading.
    Description, as the server wrote it
    Resolve a postal address to formattedAddress + lat/lon for create_fiche (cover map and 150 m WiFi geofence). Optional country ISO2. Requires Bearer.
  • get_ficheGet one owned access sheet by id (same fields as list_fiches).No findings

    Why it is in this group

    • The name "get_fiche" says "get": a word for reading.
    Description, as the server wrote it
    Get one owned access sheet by id (same fields as list_fiches). Requires Bearer.
  • list_fichesList access sheets owned by the authenticated agent.No findings

    Why it is in this group

    • The name "list_fiches" says "list": a word for reading.
    Description, as the server wrote it
    List access sheets owned by the authenticated agent. Requires Authorization: Bearer.
  • list_sharesList guest links for a fiche (token, url, expiresAt, viewCount, createdAt).Reads text others writeNo findings

    Why it is in this group

    • The name "list_shares" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List guest links for a fiche (token, url, expiresAt, viewCount, createdAt). Requires Bearer.
  • list_webhooksList webhook endpoints (secret is never returned).Reads private dataNo findings

    Why it is in this group

    • The name "list_webhooks" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "secret": it reads secrets.
    Description, as the server wrote it
    List webhook endpoints (secret is never returned). Fleet/Platform. Requires Bearer.
  • statusCurrent agent plan, expiry, fichesCount, maxFiches, overageUsdc.No findings

    Why it is in this group

    • The name "status" says "status": a word for reading.
    Description, as the server wrote it
    Current agent plan, expiry, fichesCount, maxFiches, overageUsdc. Requires Authorization: Bearer.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__fiches__list_shares"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (3 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://sesapp.fr/mcp: tools/list returned 15 tools to an anonymous client, including delete_fiche (destructive), revoke_share (destructive), delete_webhook (destructive), subscribe (write), create_fiche (write) and 4 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http fiches https://sesapp.fr/mcp
claude mcp add --transport http fiches https://sesapp.fr/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fiches__status",
      "mcp__fiches__geocode",
      "mcp__fiches__list_fiches",
      "mcp__fiches__get_fiche",
      "mcp__fiches__list_shares",
      "mcp__fiches__list_webhooks"
    ],
    "ask": [
      "mcp__fiches__subscribe",
      "mcp__fiches__create_fiche",
      "mcp__fiches__update_fiche",
      "mcp__fiches__share_fiche",
      "mcp__fiches__register_webhook",
      "mcp__fiches__update_webhook"
    ],
    "deny": [
      "mcp__fiches__delete_fiche",
      "mcp__fiches__revoke_share",
      "mcp__fiches__delete_webhook"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fiches. Review it before you use it.

Capability tags behind 6 rules
  • mcp__fiches__create_fiche outbound
  • mcp__fiches__update_fiche outbound
  • mcp__fiches__list_shares untrusted-input
  • mcp__fiches__register_webhook outbound
  • mcp__fiches__list_webhooks private-data
  • mcp__fiches__update_webhook outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/fr.sesapp/fiches/verify?hash=d226f19e2dedfa27fedcc37a6eeb8ed1048b5dcf6f9eccac9c1b5e6659d64185" | jq -e '.changed == false'

Pinned hash d226f19e2ded, from Nov 20, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/fr.sesapp/fiches/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for fr.sesapp/fiches
[![Anlyon Radar](https://radar.anlyon.com/badge/fr.sesapp/fiches.svg)](https://radar.anlyon.com/servers/fr.sesapp/fiches)

Source: MCP Registry. Synced Nov 6, 2026, 02:17 UTC.

SesApp Access Sheets MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SesApp Access Sheets MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SesApp Access Sheets MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: delete_fiche, revoke_share and delete_webhook.

Can the SesApp Access Sheets MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SesApp Access Sheets MCP server have?

15 tools: 3 destructive, 6 write, 6 read. delete_fiche, revoke_share, delete_webhook, subscribe, create_fiche, update_fiche, share_fiche, register_webhook and 7 more.

Does the SesApp Access Sheets MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SesApp Access Sheets MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_fiche, update_fiche, register_webhook and update_webhook.

Has the SesApp Access Sheets MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.