# YeetIt (remote · yeetit.site)

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

- Trust score: 58/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `yeetit.site`: 58/100 (this document), [markdown](https://verifymcp.io/servers/snappyio-yeetit/yeetit.md), [page](https://verifymcp.io/servers/snappyio-yeetit/yeetit)

## Channel facts

- Endpoint: `https://yeetit.site/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1075 tokens (~268/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.snappyio-yeetit]
url = "https://yeetit.site/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "snappyio-yeetit": {
      "type": "remote",
      "url": "https://yeetit.site/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add snappyio-yeetit --url https://yeetit.site/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  snappyio-yeetit:
    url: "https://yeetit.site/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 58, +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.

### 2026-08-01 (score 57, +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.

### 2026-07-31 (score 56, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 57, +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.

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (4)

### `publish_website` (~511 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.

Input parameters:

- `assets` (object): 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 bin…
- `html` (string, required): 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 asse…
- `title` (string): Human-readable title for the published page. Used in social sharing previews and the claim page. Optional.

### `update_website` (~286 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.

Input parameters:

- `api_key` (string): 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.
- `assets` (object): Optional map of filename to content. If provided, replaces ALL existing assets. Omit to keep existing assets unchanged.
- `edit_key` (string): 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.
- `html` (string, required): Complete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content.
- `slug` (string, required): The slug of the site to update (e.g. "hello-world-k3m").
- `title` (string): Optional new title for the page.

### `delete_website` (~185 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.

Input parameters:

- `api_key` (string): The user's API key (e.g. "yt_abc123...").
- `confirm` (boolean, required): 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): The edit key for this site (e.g. "ek_9c4d2e7f...").
- `slug` (string, required): The slug of the site to delete (e.g. "hello-world-k3m").

### `get_website_status` (~93 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.

Input parameters:

- `slug` (string, required): The slug of the site to check (e.g. "hello-world-k3m").

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/snappyio-yeetit/yeetit#diagnostics

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 57
- 2026-07-31: 56
- 2026-07-30: 58
- 2026-07-29: 57
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://yeetit.site/mcp
- Repository: https://github.com/snappyio/yeetit
- Website: https://yeetit.site/
- Changelog RSS feed: https://verifymcp.io/servers/snappyio-yeetit/yeetit/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/snappyio-yeetit/yeetit/changelog.json
- HTML version of this page: https://verifymcp.io/servers/snappyio-yeetit/yeetit