Motif & Moi
REMOTE · MOTIFETMOI.COM
Custom clothing printed in Rennes, France: catalog, quotes, delivery dates, prefilled order links.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1762 tokens (~251/item across 7 items; 7 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- “create_design” reworded the description of “logo_url” cosmetic
- “create_group_order” reworded the description of “logo_url” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 4 Nov 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.
- 2 Nov 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.
- 31 Oct 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.
- 29 Oct 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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 69
First indexed and scored.
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 5 Nov 2026 · Probed https://motifetmoi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=motifetmoi.com | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5ebd73951c339d3009febde956da5a49a3a |
| SANs: motifetmoi.com | ||||||
| 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 motifetmoi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| motifetmoi.com. | No DS | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://motifetmoi.com/mcp | Verified | 200 | |
| http (plaintext) | http://motifetmoi.com/mcp | HTTPS enforced | 308 | https://motifetmoi.com/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_design Préparer le vêtement et son lien de commande ~421
Enregistre la personnalisation (logo par URL https publique ou en base64, textes, prénoms et numéros par pièce, quantités) et renvoie un lien vers le configurateur prérempli, un aperçu et le devis. Rien n’est commandé : le client ouvre le lien, vérifie le visuel (bon à tirer), puis commande et paie lui-même. Le lien reste valable 90 jours.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Catégorie (identifiant de list_products), ex. t-shirt, sweat, hoodie, polo, tote-bag. |
| color | string | – | Couleur du vêtement (nom de list_products, ex. Noir). |
| front_format | string | – | Devant : petit logo sur le cœur (compris dans le prix) ou grand format (supplément). |
| logo_base64 | string | – | Logo encodé en base64 (à la place de logo_url). |
| logo_filename | string | – | – |
| logo_sides | array | – | Faces qui portent le logo (défaut : front). |
| logo_size | string | – | Taille dans la zone : s (petit), m (moyen, défaut), l (grand). |
| logo_url | string | – | Adresse https publique du logo (PNG, JPG, WebP ou SVG, 10 Mo max). |
| pieces | array | – | Une entrée par pièce quand un texte est « par pièce » : taille, prénom, numéro. |
| postal_code | string | – | Code postal français de livraison : donne la date de réception. |
| quality | string | – | Qualité : eco, standard (défaut) ou premium, selon la catégorie. |
| shipping | string | – | – |
| sizes | object | – | Quantités par taille, ex. {"M": 10, "L": 5}. Inutile avec pieces. |
| texts | array | – | Textes imprimés. Pour un prénom ou un numéro différent sur chaque pièce : per_piece, sans text, et la liste pieces. |
No output schema declared.
No examples provided.
create_group_order Lancer une commande de groupe ~508
Pour un club, une classe, une association : crée le modèle et deux liens. Le lien membres est à partager (WhatsApp, e-mail) : chacun y choisit sa taille, saisit son prénom et son numéro si le modèle en a (texte per_piece), et paie sa part en ligne si pay_mode vaut members. Le lien responsable est privé : il suit les inscriptions et passe la commande pour tous à la date limite (il vérifie alors le visuel et paie le solde). Plus le groupe est nombreux, moins c’est cher : la remise porte sur tout le groupe et le trop-perçu des premiers inscrits leur est remboursé.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Catégorie (identifiant de list_products), ex. t-shirt, sweat, hoodie, polo, tote-bag. |
| club_margin_pct | integer | – | Avec pay_mode members : marge en % ajoutée au prix de chaque membre pour la caisse du club, reversée au club par virement après la commande (IBAN à saisir sur owner_url). |
| color | string | – | Couleur du vêtement (nom de list_products, ex. Noir). |
| deadline | string | – | Date limite des inscriptions (AAAA-MM-JJ), à venir. |
| front_format | string | – | Devant : petit logo sur le cœur (compris dans le prix) ou grand format (supplément). |
| logo_base64 | string | – | Logo encodé en base64 (à la place de logo_url). |
| logo_filename | string | – | – |
| logo_sides | array | – | Faces qui portent le logo (défaut : front). |
| logo_size | string | – | Taille dans la zone : s (petit), m (moyen, défaut), l (grand). |
| logo_url | string | – | Adresse https publique du logo (PNG, JPG, WebP ou SVG, 10 Mo max). |
| pay_mode | string | – | members (défaut) : chacun paie sa part en ligne ; owner : le responsable règle tout. |
| quality | string | – | Qualité : eco, standard (défaut) ou premium, selon la catégorie. |
| texts | array | – | Textes imprimés. Pour un prénom ou un numéro différent sur chaque pièce : per_piece, sans text, et la liste pieces. |
| title | string | yes | Nom de la commande, ex. « Sweats du FC Rennes Sud ». |
No output schema declared.
No examples provided.
get_design_preview Aperçu d’un design ~46
Image PNG du vêtement personnalisé (chaque face marquée et gros plans), pour montrer le rendu au client avant qu’il ouvre le lien.
| Name | Type | Req | Description |
|---|---|---|---|
| design_id | string | yes | – |
No output schema declared.
No examples provided.
get_group_status Suivi d’une commande de groupe ~63
Inscriptions d’une commande de groupe (tailles, prénoms, numéros, paiements) pour son responsable : group_id et owner_key renvoyés par create_group_order.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
| owner_key | string | yes | – |
No output schema declared.
No examples provided.
get_order_status Suivi d’une commande ~55
Étape de fabrication et de livraison d’une commande payée, avec son numéro (MM-XXXXXX) et l’e-mail utilisé pour la payer.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| order_number | string | yes | – |
No output schema declared.
No examples provided.
get_quote Devis et date de livraison ~312
Prix TTC exact (remise de quantité comprise), frais de livraison et date de réception estimée pour une personnalisation, sans rien enregistrer. Donner postal_code pour la date.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Catégorie (identifiant de list_products), ex. t-shirt, sweat, hoodie, polo, tote-bag. |
| color | string | – | Couleur du vêtement (nom de list_products, ex. Noir). |
| front_format | string | – | Devant : petit logo sur le cœur (compris dans le prix) ou grand format (supplément). |
| logo_sides | array | – | Faces qui portent le logo (défaut : front). |
| logo_size | string | – | Taille dans la zone : s (petit), m (moyen, défaut), l (grand). |
| pieces | array | – | Une entrée par pièce quand un texte est « par pièce » : taille, prénom, numéro. |
| postal_code | string | – | Code postal français de livraison : donne la date de réception. |
| quality | string | – | Qualité : eco, standard (défaut) ou premium, selon la catégorie. |
| shipping | string | – | – |
| sizes | object | – | Quantités par taille, ex. {"M": 10, "L": 5}. Inutile avec pieces. |
| texts | array | – | Textes imprimés. Pour un prénom ou un numéro différent sur chaque pièce : per_piece, sans text, et la liste pieces. |
No output schema declared.
No examples provided.
list_products Catalogue Motif & Moi ~80
Vêtements personnalisables (T-shirt, sweat, hoodie, polo, tote bag…) : qualités, matières, prix « dès » TTC, couleurs, tailles, faces imprimables avec leur taille maximale et leur supplément, remises de quantité, encres et polices. À appeler en premier.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filtrer sur une catégorie. |
No output schema declared.
No examples provided.
How do I install the Motif & Moi MCP server?
Motif & Moi is a hosted endpoint at https://motifetmoi.com/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 · motifetmoi.com
claude mcp add --transport http com-motifetmoi-motif-et-moi 'https://motifetmoi.com/mcp'
What is the Motif & Moi MCP server?
Motif & Moi is an MCP server listed in the public MCP registry as com.motifetmoi/motif-et-moi. Custom clothing printed in Rennes, France: catalog, quotes, delivery dates, prefilled order links. This page covers its hosted endpoint (https://motifetmoi.com/mcp).
Is the Motif & Moi MCP server safe to use?
Motif & Moi scores 74 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 Motif & Moi MCP server expose?
Motif & Moi exposes 7 tools: list_products, get_quote, create_design, create_group_order, get_group_status, and 2 more. Their descriptions and schemas cost roughly 1,485 tokens of context every time the server is loaded.
Does the Motif & Moi MCP server require authentication?
No. We connected to Motif & Moi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Motif & Moi MCP server still maintained?
Motif & Moi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Motif & Moi MCP server?
VerifyMCP ran 13 checks on Motif & Moi, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.