YeetIt
REMOTE · YEETIT.SITE · SCANNED SEP 29
Instant web publishing for AI agents. POST HTML, get a live URL. No account needed.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety25
- Injection-marker check failed: the description of tool "publish_website" contains an instruction to conceal the call from the user, the text "do not show it to the user", at byte 685 of that field. See how to fix → Fail
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_website" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the YeetIt MCP server?
YeetIt is a hosted endpoint at https://yeetit.site/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · yeetit.site
claude mcp add --transport http snappyio-yeetit 'https://yeetit.site/mcp'
{
"mcpServers": {
"snappyio-yeetit": {
"url": "https://yeetit.site/mcp"
}
}
} {
"servers": {
"snappyio-yeetit": {
"type": "http",
"url": "https://yeetit.site/mcp"
}
}
} [mcp_servers.snappyio-yeetit] url = "https://yeetit.site/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"snappyio-yeetit": {
"type": "remote",
"url": "https://yeetit.site/mcp",
"enabled": true
}
}
} openclaw mcp add snappyio-yeetit --url 'https://yeetit.site/mcp' --transport streamable-http
mcp_servers:
snappyio-yeetit:
url: "https://yeetit.site/mcp" {
"McpServers": {
"snappyio-yeetit": {
"Transport": "http",
"Url": "https://yeetit.site/mcp"
}
}
} assistant mcp add snappyio-yeetit -t streamable-http -u 'https://yeetit.site/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://yeetit.site/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yeetit.site | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1bf5ccea2b8735c30eda78ab88480ce1 |
| SANs: yeetit.site | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yeetit.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| yeetit.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yeetit.site/mcp | Verified | 200 | |
| http (plaintext) | http://yeetit.site/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
delete_website ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | The user's API key (e.g. "yt_abc123..."). |
| confirm | boolean | yes | 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 | yes | The slug of the site to delete (e.g. "hello-world-k3m"). |
No output schema declared.
No examples provided.
get_website_status ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug of the site to check (e.g. "hello-world-k3m"). |
No output schema declared.
No examples provided.
publish_website ~511
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
update_website ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Complete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content. |
| slug | string | yes | The slug of the site to update (e.g. "hello-world-k3m"). |
| title | string | – | Optional new title for the page. |
No output schema declared.
No examples provided.
What is the YeetIt MCP server?
YeetIt is an MCP server listed in the public MCP registry as io.github.snappyio/yeetit. Instant web publishing for AI agents. POST HTML, get a live URL. No account needed. This page covers its hosted endpoint (https://yeetit.site/mcp).
Is the YeetIt MCP server safe to use?
YeetIt scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the YeetIt MCP server expose?
YeetIt exposes 4 tools: publish_website, update_website, delete_website, get_website_status. Their descriptions and schemas cost roughly 1,075 tokens of context every time the server is loaded.
Does the YeetIt MCP server require authentication?
No. We connected to YeetIt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the YeetIt MCP server still maintained?
YeetIt is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.