monappamoi
REMOTE · MONAPPAMOI.FR · SCANNED SEP 24
Host AI-generated single-file HTML apps with JSON persistence. No signup.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1353 tokens (~150/item across 9 items; 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_app" implies "publish" 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 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the monappamoi MCP server?
monappamoi is a hosted endpoint at https://monappamoi.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 · monappamoi.fr
claude mcp add --transport http fr-monappamoi-apps 'https://monappamoi.fr/mcp'
{
"mcpServers": {
"fr-monappamoi-apps": {
"url": "https://monappamoi.fr/mcp"
}
}
} {
"servers": {
"fr-monappamoi-apps": {
"type": "http",
"url": "https://monappamoi.fr/mcp"
}
}
} [mcp_servers.fr-monappamoi-apps] url = "https://monappamoi.fr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-monappamoi-apps": {
"type": "remote",
"url": "https://monappamoi.fr/mcp",
"enabled": true
}
}
} openclaw mcp add fr-monappamoi-apps --url 'https://monappamoi.fr/mcp' --transport streamable-http
mcp_servers:
fr-monappamoi-apps:
url: "https://monappamoi.fr/mcp" {
"McpServers": {
"fr-monappamoi-apps": {
"Transport": "http",
"Url": "https://monappamoi.fr/mcp"
}
}
} assistant mcp add fr-monappamoi-apps -t streamable-http -u 'https://monappamoi.fr/mcp'
{
"mcpServers": {
"fr-monappamoi-apps": {
"type": "http",
"url": "https://monappamoi.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.
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 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.
- 31 Aug 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.
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 24 Sept 2026 · Probed https://monappamoi.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=monappamoi.fr | CN=YE1,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 67da50dd6af1772c8ba20399c2fa1ba7822 |
| SANs: monappamoi.fr | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of monappamoi.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| monappamoi.fr. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://monappamoi.fr/mcp | Verified | 200 | |
| http (plaintext) | http://monappamoi.fr/mcp | HTTPS enforced | 308 | https://monappamoi.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 →
claim_app Rattacher une app au compte ~94
Rattache au compte de l'utilisateur une app publiée anonymement, à partir de son jeton secret. Elle apparaîtra ensuite dans list_my_apps et pourra être gérée sans jeton. Appelez cet outil quand l'utilisateur veut « récupérer » ou « rattacher » une app publiée sans compte.
| Name | Type | Req | Description |
|---|---|---|---|
| secret_token | string | yes | Le jeton secret (maam_app_…) de l'app à rattacher. |
No output schema declared.
No examples provided.
delete_app Supprimer une app ~90
Retire définitivement une app de la plateforme. Son URL cessera de fonctionner. Demandez confirmation à l'utilisateur avant d'appeler cet outil.
| Name | Type | Req | Description |
|---|---|---|---|
| secret_token | string | – | Le jeton secret (maam_app_…) renvoyé lors de la publication de cette app. Facultatif si l'app est rattachée au compte de la clé API configurée. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_app Informations sur une app ~87
Renvoie les métadonnées d'une app publiée (URL, titre, taille, dates de création et de mise à jour).
| Name | Type | Req | Description |
|---|---|---|---|
| secret_token | string | – | Le jeton secret (maam_app_…) renvoyé lors de la publication de cette app. Facultatif si l'app est rattachée au compte de la clé API configurée. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_app_data Lire les données d'une app ~133
Renvoie le document JSON enregistré par les utilisateurs de l'app. Appelez cet outil avant de faire évoluer une app qui enregistre des données, pour savoir quelle structure est réellement en place. Fonctionne aussi sur une app verrouillée : le jeton secret ou la clé API du propriétaire suffit, le verrou ne concerne que les visiteurs du sous-domaine.
| Name | Type | Req | Description |
|---|---|---|---|
| secret_token | string | – | Le jeton secret (maam_app_…) renvoyé lors de la publication de cette app. Facultatif si l'app est rattachée au compte de la clé API configurée. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_publishing_guide Guide de publication ~82
Explique comment écrire une app pour cette plateforme : où placer les données (HTML, localStorage ou API /api/data), le pattern de persistance recommandé, et comment faire évoluer une app sans casser les données de ses utilisateurs. À lire avant de publier une app qui enregistre quelque chose, et avant tout update_app qui change la structure des données.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_apps Lister mes apps ~61
Liste les apps publiées rattachées au compte de l'utilisateur. Appelez cet outil quand il demande « quelles sont mes apps », veut retrouver l'adresse d'une app publiée précédemment, ou souhaite en modifier une sans avoir son jeton sous la main.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_app Publier une app ~359
Met en ligne une app HTML mono-fichier et renvoie son URL publique. Appelez cet outil quand l'utilisateur veut héberger, publier, mettre en ligne ou partager une app HTML que vous venez de créer. Aucun compte n'est nécessaire. IMPORTANT : si l'app conserve des données que l'utilisateur s'attendra à retrouver plus tard (todo, notes, compteur, scores, favoris…), câblez-la sur GET/PUT /api/data AVANT de publier — localStorage seul ne survit pas au changement d'appareil. Voir get_publishing_guide. CONFIDENTIALITÉ : l'app publiée est accessible à quiconque a son adresse, mais elle PEUT être verrouillée (page et données réservées au compte de l'utilisateur, après lien envoyé par email). Cet outil renvoie le lien qui rattache et verrouille en un clic : proposez-le à l'utilisateur juste après la publication dès que l'app enregistre des données personnelles.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | Données initiales de l'app, en JSON sérialisé (ex. '{"todos":[]}'). N'écrase jamais des données existantes — utilisez set_app_data pour cela. |
| html | string | yes | Le fichier HTML complet de l'app (CSS et JS inclus dedans). Maximum 2 Mo. |
| slug | string | – | Base du sous-domaine souhaitée (3–40 caractères : minuscules, chiffres, tirets), sinon dérivée du titre. Un suffixe aléatoire lui est TOUJOURS ajouté : l'adresse finale diffère du slug demandé. Utili… |
| title | string | – | Titre lisible de l'app. |
No output schema declared.
No examples provided.
set_app_data Remplacer les données d'une app ~134
Écrase le document JSON de l'app. C'est la seule façon de remplacer des données existantes : utilisez-le pour migrer les données vers une nouvelle structure, ou pour repartir de zéro. Les données précédentes sont définitivement perdues — prévenez l'utilisateur.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Le nouveau document complet, en JSON sérialisé. |
| secret_token | string | – | Le jeton secret (maam_app_…) renvoyé lors de la publication de cette app. Facultatif si l'app est rattachée au compte de la clé API configurée. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
update_app Mettre à jour une app ~200
Remplace le HTML et/ou le titre d'une app déjà publiée. L'URL ne change pas. Les données déjà enregistrées par les utilisateurs ne sont jamais écrasées : si votre nouvelle version change la structure des données, lisez d'abord get_app_data puis migrez avec set_app_data.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | Données initiales, appliquées uniquement si l'app n'en a encore aucune. Pour remplacer des données existantes, utilisez set_app_data. |
| html | string | – | Le fichier HTML complet de l'app (CSS et JS inclus dedans). Maximum 2 Mo. |
| secret_token | string | – | Le jeton secret (maam_app_…) renvoyé lors de la publication de cette app. Facultatif si l'app est rattachée au compte de la clé API configurée. |
| slug | string | yes | Le sous-domaine de l'app à mettre à jour. |
| title | string | – | – |
No output schema declared.
No examples provided.
What is the monappamoi MCP server?
monappamoi is an MCP server listed in the public MCP registry as fr.monappamoi/apps. Host AI-generated single-file HTML apps with JSON persistence. No signup. This page covers its hosted endpoint (https://monappamoi.fr/mcp).
Is the monappamoi MCP server safe to use?
monappamoi scores 78 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 monappamoi MCP server expose?
monappamoi exposes 9 tools: get_publishing_guide, publish_app, update_app, get_app, delete_app, and 4 more. Their descriptions and schemas cost roughly 1,240 tokens of context every time the server is loaded.
Does the monappamoi MCP server require authentication?
No. We connected to monappamoi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the monappamoi MCP server still maintained?
monappamoi is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.