# ai.yetty/yetty (remote · mcp.yetty.ai)

Build, edit and run real hosted websites from your AI - content, SEO, menus, store, rollback.

- Trust score: 86/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.yetty.ai`: 86/100 (this document), [markdown](https://verifymcp.io/servers/ai-yetty-yetty/mcp.md), [page](https://verifymcp.io/servers/ai-yetty-yetty/mcp)

## Channel facts

- Endpoint: `https://mcp.yetty.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-09-20.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2701 tokens (~270/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 70/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 9% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ai.yetty/yetty MCP server?

ai.yetty/yetty is a hosted endpoint at https://mcp.yetty.ai/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.

### Claude

```bash
claude mcp add --transport http ai-yetty-yetty 'https://mcp.yetty.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-yetty-yetty": {
      "url": "https://mcp.yetty.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-yetty-yetty": {
      "type": "http",
      "url": "https://mcp.yetty.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-yetty-yetty]
url = "https://mcp.yetty.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-yetty-yetty --url 'https://mcp.yetty.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-yetty-yetty:
    url: "https://mcp.yetty.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-yetty-yetty": {
      "Transport": "http",
      "Url": "https://mcp.yetty.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-yetty-yetty -t streamable-http -u 'https://mcp.yetty.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-yetty-yetty": {
      "type": "http",
      "url": "https://mcp.yetty.ai/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-09-20 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 84, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 241 → 270
- [functional] Schema quality: excellent → good

### 2026-09-13 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `yetty_status` (~43 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.

### `yetty_authoring_guide` (~94 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.

### `yetty_pull_template` (~291 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.)

Input parameters:

- `template` (string): template key: checkout-skeleton (default) | account-skeleton | order-status-skeleton | pay-skeleton

### `yetty_batch_start` (~153 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.

### `yetty_batch_file` (~108 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.

Input parameters:

- `batch_ref` (string, required)
- `content` (string)
- `content_base64` (string)
- `path` (string, required)

### `yetty_batch_end` (~47 tokens)

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

Input parameters:

- `batch_ref` (string, required)

### `yetty_signup` (~92 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.

Input parameters:

- `email` (string, required)
- `park_ref` (string, required)

### `yetty_claim_status` (~77 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).

Input parameters:

- `park_ref` (string, required)

### `yetty_login` (~123 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.

Input parameters:

- `email` (string, required)

### `yetty_login_status` (~94 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

Input parameters:

- `login_ref` (string, required)

## Diagnostics

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

## Score history

- 2026-09-20: 86
- 2026-09-19: 86
- 2026-09-18: 85
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 84
- 2026-09-12: 83
- 2026-09-11: 83
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 80
- 2026-09-03: 79
- 2026-09-02: 79
- 2026-09-01: 78
- 2026-08-31: 78
- 2026-08-30: 77
- 2026-08-29: 77
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 65
- 2026-08-25: 62
- 2026-08-24: 73
- 2026-08-23: 72
- 2026-08-22: 71

## Common questions

### What is the ai.yetty/yetty MCP server?

ai.yetty/yetty is an MCP server listed in the public MCP registry as ai.yetty/yetty. Build, edit and run real hosted websites from your AI - content, SEO, menus, store, rollback. This page covers its hosted endpoint (https://mcp.yetty.ai/mcp).

### Is the ai.yetty/yetty MCP server safe to use?

ai.yetty/yetty scores 86 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 ai.yetty/yetty MCP server expose?

ai.yetty/yetty exposes 10 tools: yetty_status, yetty_authoring_guide, yetty_pull_template, yetty_batch_start, yetty_batch_file, and 5 more. Their descriptions and schemas cost roughly 1,122 tokens of context every time the server is loaded.

### Does the ai.yetty/yetty MCP server require authentication?

Yes. ai.yetty/yetty asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the ai.yetty/yetty MCP server still maintained?

ai.yetty/yetty is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.yetty.ai/mcp
- Repository: https://github.com/avniy/yetty-mcp
- Website: https://yetty.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-yetty-yetty/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-yetty-yetty/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-yetty-yetty/mcp