Is the Snappyio Yeetit MCP server down?

mcp-registry/io.github.snappyio/yeetit · v1.0.0

healthy
Last checked 2026-10-22 02:03 UTC · handshake 191ms

As of 2026-10-22 02:03 UTC, the Snappyio Yeetit MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,161
outages (90d)
0
tools
4

Instant web publishing for AI agents. POST HTML, get a live URL. No account needed.

Install Snappyio Yeetit MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http snappyio-yeetit-mcp-server https://yeetit.site/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "snappyio-yeetit-mcp-server": {
      "type": "http",
      "url": "https://yeetit.site/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 4 tool(s); ~1,350 tokens of tool definitions.
Scores higher than 30% of 15,507 MCP servers Glimind has audited.
Its tool list costs an agent ~1,350 tokens per session — lighter than 65% of servers.
76 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (4)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: delete_website, get_website_status, publish_website, update_website

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: delete_website, publish_website, update_website

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.snappyio%2Fyeetit/fixes

delete_website 1 change
{
  "name": "delete_website",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug",
      "confirm"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "The slug of the site to delete (e.g. \"hello-world-k3m\")."
      },
      "api_key": {
        "type": "string",
        "description": "The user's API key (e.g. \"yt_abc123...\")."
      },
      "confirm": {
        "type": "boolean",
        "description": "Must be set to true to confirm deletion. This is a safety mechanism — the tool will refuse to delete without explicit confirmation."
      },
      "edit_key": {
        "type": "string",
        "description": "The edit key for this site (e.g. \"ek_9c4d2e7f...\")."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
get_website_status 1 change
{
  "name": "get_website_status",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "The slug of the site to check (e.g. \"hello-world-k3m\")."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
publish_website 1 change
{
  "name": "publish_website",
  "description": "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: Afte",
  "inputSchema": {
    "type": "object",
    "required": [
      "html"
    ],
    "properties": {
      "html": {
        "type": "string",
        "description": "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": {
        "type": "string",
        "description": "Human-readable title for the published page. Used in social sharing previews and the claim page. Optional."
      },
      "assets": {
        "type": "object",
        "description": "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).",
        "additionalProperties": {
          "type": "string"
        }
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.snappyio/yeetit"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.snappyio/yeetit"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.snappyio%2Fyeetit.svg)](https://glimind.com/server/mcp-registry%2Fio.github.snappyio%2Fyeetit?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.snappyio%2Fyeetit?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.snappyio%2Fyeetit.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.snappyio%2Fyeetit.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.snappyio%2Fyeetit?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9627df2ac2e584dc…, first seen 2026-10-17, included at leaf 6070 of 42,833. Version history · verify what your client received.

Tools (4)

Compare: most reliable web servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Snappyio Yeetit MCP server down right now?

As of 2026-10-22 02:03 UTC, the Snappyio Yeetit MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Snappyio Yeetit MCP server provide?

Snappyio Yeetit MCP server advertises 4 tools, including delete_website, get_website_status, publish_website, update_website.

How do I install Snappyio Yeetit MCP server?

Point your MCP client at this streamable-http endpoint: https://yeetit.site/mcp

Is the Snappyio Yeetit MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Snappyio Yeetit MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve