ai.yetty/yetty

Est-ce que ai.yetty/yetty est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.yetty/yetty » 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 10 outils

• yetty_authoring_guide≈ 163 tokens

  READ THIS BEFORE WRITING OR SENDING ANY HTML (no account needed, free, instant, no arguments). Returns yetty's exact structure rules — repeated items sharing one class, semantic class names for field labels, headings before sections, no JS-rendered content — that decide whether the site converts into a clean editable CMS with named fields and add/remove collections, or a wall of generic "Text" fields.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "yetty_authoring_guide", "arguments": {}}

  Exemple de retour

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

• yetty_batch_end≈ 107 tokens

  Close the parked batch. Nothing is processed yet — next call yetty_signup {email, park_ref} so the owner can approve by email.

  Paramètres, retour & exemple (1)

  Paramètres

  • batch_ref · string · requis

  Exemple d'appel

  {"name": "yetty_batch_end", "arguments": {"batch_ref": "texte"}}

  Exemple de retour

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

• yetty_batch_file≈ 173 tokens

  Add ONE file to the parked batch. Args: batch_ref (the pk_... park_ref); path (relative, folders allowed); content (text) OR content_base64 (binary). Returns {received_bytes, sha256} — verify against your local copy; mismatch = resend THIS file. Send EXACT bytes, never retype.

  Paramètres, retour & exemple (4)

  Paramètres

  • path · string · requis
  • content · string · optionnel
  • batch_ref · string · requis
  • content_base64 · string · optionnel

  Exemple d'appel

  {"name": "yetty_batch_file", "arguments": {"path": "texte", "batch_ref": "texte"}}

  Exemple de retour

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

• yetty_batch_start≈ 203 tokens

  No account needed: start a PARKED file batch — send the site now, authenticate after. Returns park_ref (use it as batch_ref). Files are stored safely but NOT processed until the owner approves by email. EXAMPLE: yetty_batch_start {} -> {park_ref:"pk_..."} -> yetty_batch_file {batch_ref:"pk_...", path:"index.html", content:"..."} per file -> yetty_batch_end {batch_ref:"pk_..."} -> yetty_signup {email:"owner@x.com", park_ref:"pk_..."} -> owner clicks the email -> yetty_claim_status {park_ref:"pk_..."} gives you an API key + the build status.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "yetty_batch_start", "arguments": {}}

  Exemple de retour

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

• yetty_claim_status≈ 140 tokens

  Check a parked upload. States: parked (send yetty_signup) -> awaiting-approval (owner must open the email and type the user_code) -> approved (returns your api_key ONCE + waiting_url — reconnect with Authorization: Bearer <api_key> for the full toolset).

  Paramètres, retour & exemple (1)

  Paramètres

  • park_ref · string · requis

  Exemple d'appel

  {"name": "yetty_claim_status", "arguments": {"park_ref": "texte"}}

  Exemple de retour

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

• yetty_login≈ 182 tokens

  Sign the OWNER in by email — no dashboard, no key copying. Works for existing accounts AND (when signups are open) new ones. FLOW: yetty_login {email:"owner@x.com"} -> {login_ref, user_code} -> SHOW the owner the user_code; they open the emailed link and type it -> poll yetty_login_status {login_ref} every ~20s -> it returns an api_key ONCE + the exact reconnect command. Use this whenever you are unauthenticated or your token expired.

  Paramètres, retour & exemple (1)

  Paramètres

  • email · string · requis

  Exemple d'appel

  {"name": "yetty_login", "arguments": {"email": "texte"}}

  Exemple de retour

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

• yetty_login_status≈ 152 tokens

  Check an email sign-in: pending (owner has not typed the code yet) -> approved (returns api_key ONCE + reconnect instructions). EXAMPLE reconnect for Claude Code: claude mcp remove yetty; claude mcp add --transport http yetty https://mcp.yetty.ai/ --header "Authorization: Bearer <api_key>" -s user

  Paramètres, retour & exemple (1)

  Paramètres

  • login_ref · string · requis

  Exemple d'appel

  {"name": "yetty_login_status", "arguments": {"login_ref": "texte"}}

  Exemple de retour

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

• yetty_pull_template≈ 383 tokens

  Pull a ready-made Yetty template file WITH its usage contract (no account needed, free, instant). Four boilerplates, one per store surface: template:"checkout-skeleton" (cart / checkout / thank-you markup with every data-yetty-component and data-yetty-slot mark), "account-skeleton" (the buyer's /account page in the site's own design), "order-status-skeleton" (the /order/{token} confirmation), "pay-skeleton" (the /pay/{token} frame - the payment element stays hosted and non-removable). Every file carries a commented CONDITIONAL REGIONS section showing the component logic grammar (data-yetty-when / data-yetty-each / data-yetty-state; full grammar in yetty_authoring_guide's logic_and_conditional_components chapter). Restyle freely to match the site; NEVER remove or rename data-yetty-* marks; write NO cart/checkout/account JavaScript of your own (Yetty provides the behavior); send the styled file back with the site files. (Connected Live-plan stores can additionally pull 24 gallery-<surface>-<layout> LAYOUT skeletons - different page structures over the same contract, auto-adjusted to the site's own colors and fonts.)

  Paramètres, retour & exemple (1)

  Paramètres

  • template · string · optionnel
    template key: checkout-skeleton (default) | account-skeleton | order-status-skeleton | pay-skeleton

  Exemple d'appel

  {"name": "yetty_pull_template", "arguments": {"template": "texte"}}

  Exemple de retour

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

• yetty_signup≈ 160 tokens

  Link a parked upload to the owner's email: sends them an approval email and returns a short user_code. The site is processed ONLY after the owner opens the email and types that code on the approval page. Args: email (the owner's), park_ref. SHOW THE OWNER THE CODE, then poll yetty_claim_status every ~30s.

  Paramètres, retour & exemple (2)

  Paramètres

  • email · string · requis
  • park_ref · string · requis

  Exemple d'appel

  {"name": "yetty_signup", "arguments": {"email": "texte", "park_ref": "texte"}}

  Exemple de retour

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

• yetty_status≈ 104 tokens

  Connection + authentication status. Call this FIRST. Unauthenticated sessions can still park a website (batch tools) and start email sign-up — the response tells you exactly how.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "yetty_status", "arguments": {}}

  Exemple de retour

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

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://mcp.yetty.ai/mcp