design.zaps/zaps

Est-ce que design.zaps/zaps est sûr ?

Au dernier audit MCP Hub, le serveur MCP « design.zaps/zaps » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• create_designs≈ 783 tokens

  The whole job in one call: give it a SEARCH QUERY you have written, your photo URLs and the words you want on the design, and it finds templates that fit, renders each with your photos and your copy, and returns several finished designs to choose between. Use this when someone wants options — it is search and render together, so there is no need to call search_templates and fill_template yourself. Templates that hold every photo you supplied are preferred, so pass all of them. Photos attached in the conversation go in `photos`; photos already on the web go in `images`. Each returned design spends one agentic token.

  Paramètres, retour & exemple (6)

  Paramètres

  • text · array · optionnel
    The words to put ON the designs — headline first, then any supporting lines. WRITE THESE YOURSELF from the brief: a template ships with the designer's placeholder copy, and leaving it means a coffee shop opening goes out reading whatever they typed. Keep a headline to a few words; templates lay out short lines.
  • brief · string · requis
    The SEARCH QUERY for the template catalogue — you write it, we do not build it from anything else. Title Case phrases separated by commas, the way the catalogue describes itself: "Birthday Party, Friends, Celebration, Confetti, Party Invite". Five or six covering occasion, subject and mood. Written this way it scores about 0.11 higher than the same intent as a sentence, and a single word is worst of all. If you were given photos, look at them and let what you see inform the phrases.
  • count · integer · optionnel
    How many finished designs to return. Default 5, at most 10.
  • images · array · optionnel
    Publicly reachable image URLs, in placement order.
  • photos · array · optionnel
    Photos the person attached in this conversation, in placement order. Use this OR images, not both.
  • segment · string · optionnel
    Optional shape filter, e.g. story or carousel.

  Exemple d'appel

  {"name": "create_designs", "arguments": {"brief": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "upsell": "texte", "options": [], "matchedBy": "texte", "remaining": 1, "requested": 1, "entitlement": "texte"}}

• fill_template≈ 458 tokens

  Render a finished image: give it a template id from search_templates and the photo URLs to place, and it returns the rendered design. Photos are placed into the template's image slots in the order given, so pass them in the order you want them to appear. Photos attached in the conversation go in `photos`; photos already on the web go in `images`. Each render spends one agentic token.

  Paramètres, retour & exemple (3)

  Paramètres

  • images · array · optionnel
    Publicly reachable image URLs, in placement order.
  • photos · array · optionnel
    Photos the person attached in this conversation, in placement order. Use this OR images, not both.
  • coverId · string · requis
    Template id, from a search_templates result.

  Exemple d'appel

  {"name": "fill_template", "arguments": {"coverId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "upsell": "texte", "options": [], "matchedBy": "texte", "remaining": 1, "requested": 1, "entitlement": "texte"}}

• search_templates≈ 432 tokens

  Find design templates. YOU write the query, and its wording decides the match: the catalogue describes each template as Title Case phrases separated by commas, and a query in that same register scores about 0.11 higher than the same intent written as a sentence. Write five or six phrases covering the occasion, the subject and the mood — "Coffee Shop, Cafe Vibes, Grand Opening, Latte Art, Cafe Aesthetic" rather than "grand opening of a neighbourhood coffee shop". A single word is worst of all. Returns templates with an id to fill and a link a person can open to keep editing.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    How many templates to return. Default 5.
  • query · string · requis
    Title Case phrases separated by commas, the way the catalogue describes itself. Five or six covering occasion, subject and mood.
  • segment · string · optionnel
    Optional shape filter, e.g. story or carousel.

  Exemple d'appel

  {"name": "search_templates", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"templates": []}}

• upload_images≈ 410 tokens

  Call this FIRST when the photos are on the caller's machine rather than already on the web — our renderer fetches over the network and cannot read a local path. Simplest way: read each file and pass it in `files` as base64; the reply gives you a publicUrl per photo to hand straight to create_designs, with nothing else to run. If you would rather upload the bytes yourself, pass `count` instead and you get presigned links to PUT to. Costs nothing either way.

  Paramètres, retour & exemple (3)

  Paramètres

  • count · integer · optionnel
    Only when uploading the bytes yourself: how many links to mint.
  • files · array · optionnel
    The photos themselves, base64 encoded. We store them and hand back a url each. Use this unless you have a reason not to.
  • mimeType · string · optionnel
    The images' media type, e.g. image/png or image/jpeg.

  Exemple d'appel

  {"name": "upload_images", "arguments": {"count": 1, "files": [], "mimeType": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"howTo": "texte", "slots": [], "imageUrls": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.zaps.design/mcp