mcp-registry/fr.sesapp/fiches · v1.0.0
As of 2026-10-27 02:43 UTC, the Sesapp Fiches MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 5 minutes.
Housing access sheets behind revocable guest links. x402 on Base.
Point your MCP client at this streamable-http endpoint: https://sesapp.fr/mcp
15 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
15 parameter(s) across 9 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
6 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Ffr.sesapp%2Ffiches/fixes
{
"name": "create_fiche",
"description": "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 ",
"inputSchema": {
"type": "object",
"required": [
"name",
"formattedAddress"
],
"properties": {
"lat": {
"type": "number",
"description": "Cover map + WiFi geofence (150 m)."
},
"lon": {
"type": "number",
"description": "Cover map + WiFi geofence (150 m)."
},
"name": {
"type": "string"
},
"locale": {
"enum": [
"fr",
"en"
],
"type": "string",
"description": "Guest chrome language. Markdown stays as written. Omit to follow Accept-Language / ?lang=."
},
"wifiName": {
"type": "string",
"description": "SSID for sesapp:wifi. Hidden until 150 m if wifiPassword is set."
},
"accessCode": {
"type": "string",
"description": "Shown on the generated cover."
},
"phoneNumber": {
"type": "string",
"description": "Required for sesapp:contact. E.164 preferred."
},
"instructions": {
"type": "string",
"description": "Markdown flip-book shown to the guest (this field).\nCover (map, name, formattedAddress, accessCode) is generated — do not repeat it here.\nSplit pages with a line containing only --- .\nSupported: # ## ### headings, paragraphs, **bold**, *italic*, - / 1. lists, [label](https://...), .\nPhotos: https URLs (GCS via the host app, or your own CDN). Agents send URLs, no file upload.\nNever put wifiPassword in Markdown; it is unlocked only within 150 m via GPS.\nIntent hrefs: sesapp:wifi (needs wifiName + wifiPassword) and sesapp:contact (needs phoneNumber). Guest-facing labels: [Ajouter le WiFi] / [Ajouter le contact].\nIf you omit those links but set the fields, SesApp appends WiFi/contact pages.\nExample:\n# Bienvenue\nParking au fond à gauche.\n\n\n\n---\n\n## Arrivée\nSonnette à gauche.\n\n[Itinéraire](https://maps.google.com/?q=48.8566,2.3522)\n\n---\n\n[Ajouter le WiFi](sesapp:wifi)\n\n---\n\n[Ajouter le contact](sesapp:contact)"
},
"wifiPassword": {
"type": "string",
"description": "Do not put in instructions. Unlocked within 150 m."
},
"formattedAddress": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "delete_fiche",
"description": "Delete an owned access sheet and its share links. Requires Bearer.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "delete_webhook",
"description": "Delete a webhook endpoint. Fleet/Platform. Requires Bearer.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/fr.sesapp/fiches"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/fr.sesapp/fiches"}) over MCP.
create_fiche ~674 tokensupdate_fiche ~570 tokensregister_webhook ~153 tokensgeocode ~114 tokensshare_fiche ~103 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Ffr.sesapp%2Ffiches?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Ffr.sesapp%2Ffiches?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ffr.sesapp%2Ffiches.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ffr.sesapp%2Ffiches.svg :target: https://glimind.com/server/mcp-registry%2Ffr.sesapp%2Ffiches?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:24b79e9cef6f37d8…, first seen 2026-10-17, included at leaf 1016 of 76,902. Version history · verify what your client received.
Compare: most reliable files servers · most reliable devops servers · most reliable data servers · most reliable web servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 02:43 UTC, the Sesapp Fiches MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 5 minutes.
Sesapp Fiches MCP server advertises 15 tools, including create_fiche, delete_fiche, delete_webhook, geocode, get_fiche.
Point your MCP client at this streamable-http endpoint: https://sesapp.fr/mcp
Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.