io.github.snappyio/yeetit

Est-ce que io.github.snappyio/yeetit est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.snappyio/yeetit » 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

• delete_website≈ 247 tokens

  Permanently delete a published website. The site will be immediately inaccessible. Requires authentication via edit_key or api_key, and requires confirm: true as a safety mechanism to prevent accidental deletion. Use this when a user explicitly asks you to remove or delete a site. IMPORTANT: Always confirm with the user before calling this tool — deletion cannot be undone.

  Paramètres, retour & exemple (4)

  Paramètres

  • slug · string · requis
    The slug of the site to delete (e.g. "hello-world-k3m").
  • api_key · string · optionnel
    The user's API key (e.g. "yt_abc123...").
  • confirm · boolean · requis
    Must be set to true to confirm deletion. This is a safety mechanism — the tool will refuse to delete without explicit confirmation.
  • edit_key · string · optionnel
    The edit key for this site (e.g. "ek_9c4d2e7f...").

  Exemple d'appel

  {"name": "delete_website", "arguments": {"slug": "texte", "confirm": true}}

  Exemple de retour

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

• get_website_status≈ 128 tokens

  Get information about a published website including its title, view count, size, expiry date, and whether it has been claimed. No authentication required — this is public information. Use this to check if a site is still live, see how many views it has gotten, or check when it expires.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    The slug of the site to check (e.g. "hello-world-k3m").

  Exemple d'appel

  {"name": "get_website_status", "arguments": {"slug": "texte"}}

  Exemple de retour

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

• publish_website≈ 593 tokens

  Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.

  Paramètres, retour & exemple (3)

  Paramètres

  • html · string · requis
    Complete HTML document to publish. Must be a valid, self-contained page. Inline CSS and JS are supported. External resources (images, fonts, scripts) must use absolute URLs OR be included in the assets field with relative references (e.g. href="./style.css" or src="./logo.png"). Maximum total size including assets: 5.0MB (free tier) or 10 MB (Pro/Business).
  • title · string · optionnel
    Human-readable title for the published page. Used in social sharing previews and the claim page. Optional.
  • assets · object · optionnel
    Optional map of filename to content for bundled assets. Keys are filenames (e.g. "style.css", "logo.png", "app.js"). Values are either plain text strings (for CSS, JS, SVG, HTML) or data URIs for binary files (e.g. "data:image/png;base64,iVBOR..."). Reference these in your HTML with relative paths like ./style.css or ./logo.png. For multi-page sites, include additional .html files (e.g. "about.html") which become accessible at /{slug}/about. Limits: 10 assets (free) or 50 assets (Pro/Business), 5 MB max per individual asset, but total site size (HTML + all assets) must be under 5.0MB (free) or 10 MB (Pro/Business).

  Exemple d'appel

  {"name": "publish_website", "arguments": {"html": "texte"}}

  Exemple de retour

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

• update_website≈ 389 tokens

  Update an existing published website with new HTML content. Requires authentication via edit_key (from the original publish response) or api_key (from the user's dashboard after claiming the site). The html field replaces the entire page — this is a full replacement, not a patch. You can also update assets. Use this when a user asks you to modify, edit, or change a site you previously published. IMPORTANT: You must provide either edit_key or api_key for authentication.

  Paramètres, retour & exemple (6)

  Paramètres

  • html · string · requis
    Complete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content.
  • slug · string · requis
    The slug of the site to update (e.g. "hello-world-k3m").
  • title · string · optionnel
    Optional new title for the page.
  • assets · object · optionnel
    Optional map of filename to content. If provided, replaces ALL existing assets. Omit to keep existing assets unchanged.
  • api_key · string · optionnel
    The user's API key from their dashboard (e.g. "yt_abc123..."). Use this if the user has claimed the site and provided their API key.
  • edit_key · string · optionnel
    The edit key returned when the site was originally published (e.g. "ek_9c4d2e7f..."). Use this if you still have it from the publish response.

  Exemple d'appel

  {"name": "update_website", "arguments": {"html": "texte", "slug": "texte"}}

  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://yeetit.site/mcp