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

Your AI builds real hosted websites: describe it, get a live site with SSL, forms, analytics. Free.

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.sitectrl.ai/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-09-21.

- **Endpoint Security**: 92/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1746 tokens (~134/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 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.sitectrl/sitectrl MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "ai-sitectrl-sitectrl": {
      "type": "http",
      "url": "https://mcp.sitectrl.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-21 (score 85, +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-19 (score 84, +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-17 (score 83, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-09-15 (score 78, +1)

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

### 2026-09-14 (score 77, −1)

- [security] New tool “add_component”, which the server declares destructive
- [security] Tool “write_site_files” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

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

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

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

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

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

## MCP tools (13)

### `whoami` (~28 tokens)

Who am I

The connected sitectrl account: email, plan status, free-site slot, and credit balance.

### `list_sites` (~23 tokens)

List my sites

List the user's sitectrl sites with their live URLs and hosting platform.

### `get_site` (~34 tokens)

Get site details

Details for one site: live URL, draft URL, status.

Input parameters:

- `slug` (string, required): The site's slug from list_sites.

### `create_site` (~343 tokens)

Create a new site

Build a brand-new hosted website from a plain-language description. RETURNS IMMEDIATELY with status 'building' — the site takes about 2-3 minutes and is NOT ready when this returns. Tell the user where it will be (expected_url) and poll get_build_status with the returned claim_token. NEVER call create_site a second time for the same site: each call builds another one. Works WITHOUT signing in: an unauthenticated call builds a guest site and returns a claim_url — the user signs up free (no card) at that link to keep it; unclaimed guest sites are deleted after 72 hours. Signed in, the site lands directly on the connected account (free tier: one site, no card).

Input parameters:

- `contact_email` (string): Optional, guest builds only: the user's email — we send the site link and a reminder before the unclaimed site expires.
- `description` (string, required): What the site is for. MINIMUM 12 CHARACTERS — a bare 'bike shop' is rejected. Say what the business is, where it is, and what the site should include; the AI builds directly from this, so more detail…
- `site_name` (string, required): Short human name for the site, e.g. 'Whitney Apparel'.
- `template` (string): Starting template (guest builds; default local-services).

### `get_build_status` (~72 tokens)

Check a site build

Check whether a site started by create_site has finished. Pass the claim_token create_site returned. Works WITHOUT signing in. Poll this every 30-60 seconds rather than calling create_site again — a second create_site call builds a SECOND site.

Input parameters:

- `claim_token` (string, required): The claim_token from create_site.

### `edit_site` (~82 tokens)

Edit site (AI developer)

Ask sitectrl's AI editor to change an existing site ('add a contact page', 'make the hero darker'). Edits land in the site's draft; the first build of a brand-new site goes straight live. Returns what changed plus the draft URL.

Input parameters:

- `instruction` (string, required): The change to make, in plain language.
- `slug` (string, required)

### `write_site_files` (~231 tokens)

Write site files

Push files (HTML/CSS/JS/images) into a site's DRAFT — use this when YOU are writing the code yourself instead of asking sitectrl's AI. Text files go in 'content'; binary files (images/fonts) in 'content_base64'. Max 40 files/call, 2 MB/file. Keep the <script defer src="sc-track.js"></script> include on every HTML page (the site's built-in private analytics — publish re-adds it if missing). Use clearly-marked placeholder contact info unless the user provided real details. For working forms, POST to /_sc/form/submit with a hidden _form name field — submissions reach the owner's dashboard + email (never use mailto:). Every HTML file is checked before it's written (DOCTYPE, charset, and any invariant this site has declared) — a file that fails is refused and comes back in 'refused' with what's wrong and the exact fix; other files in the same call still write. Follow with publish_site to go live.

Input parameters:

- `files` (array, required)
- `slug` (string, required)

### `list_site_files` (~29 tokens)

List site files

List the files in a site's draft tree (paths + sizes).

Input parameters:

- `slug` (string, required)

### `read_site_file` (~45 tokens)

Read a site file

Read one file from a site's draft tree (text, or base64 for binary; 512 KB cap).

Input parameters:

- `path` (string, required)
- `slug` (string, required)

### `publish_site` (~44 tokens)

Publish to live site

Publish the site's draft to the LIVE site (hosted sites). A snapshot of the previous live version is taken first, so it's undoable.

Input parameters:

- `slug` (string, required)

### `add_component` (~477 tokens)

Add a library component

Insert a component from the site's shared library into one or more existing pages, INSTEAD of hand-writing the markup yourself — the classes are already styled and themed to this site's colours. Choices: sc-page-title (the page's one <h1>), sc-gallery (cross-fading photo reel — needs 'images'), sc-info-tiles (title + picture + text sections — needs 'tiles'), sc-instructions (numbered/titled steps, optionally with a button each — needs 'tiles'), sc-event (one dated thing: a class, a session, an opening — needs 'title'), sc-btn (a link styled as a button — needs 'label'). NOT offered: sc-header/sc-footer (the site's own shell already emits those) or sc-hero (placed once, on the home page, by the site's own build). 'anchor' says where it goes: {"type": "heading", "value": "<text on the page>", "position": "after"} (default), {"type": "id", "value": "<element id>", "position": "after"}, {"type": "main_end"} (append at the end of the page), or {"type": "replace", "value": "<class of an existing sc-* block>"}. 'pages' is "all" or a list of paths from list_site_files. A page whose anchor doesn't match comes back in 'findings' with what's wrong and the fix — other pages in the same call still get the component. Follow with publish_site.

Input parameters:

- `anchor` (object, required)
- `fields` (object, required): Component-specific content. sc-page-title: {text, eyebrow?}. sc-gallery: {images: [{src, alt}]}. sc-info-tiles: {tiles: [{title, img?, alt?, text}]}. sc-instructions: {title?, intro?, tiles: [{title?…
- `name` (string, required)
- `pages`: "all", or an array of page paths, e.g. ["index.html", "about.html"]
- `slug` (string, required)

### `search_domains` (~79 tokens)

Search domains

Search real domain availability + prices (com/net/org/co/io/site and more). Available results include a purchase_url — hand it to the USER to complete checkout; the connector never spends money. Purchased domains connect to their sites in one click.

Input parameters:

- `query` (string, required): Domain or name to check, e.g. 'sierratrailcoffee.com'.

### `get_analytics` (~65 tokens)

Get site analytics

The site's private first-party traffic: pageviews/visitors/sessions/clicks totals, top pages, referrers, devices. Windows: 24h, 7d, 30d.

Input parameters:

- `slug` (string, required)
- `window` (string)

## Diagnostics

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

## Score history

- 2026-09-21: 85
- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 83
- 2026-09-17: 83
- 2026-09-16: 78
- 2026-09-15: 78
- 2026-09-14: 77
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 75
- 2026-09-06: 75
- 2026-09-05: 74
- 2026-09-04: 74
- 2026-09-03: 73
- 2026-09-02: 73
- 2026-09-01: 72
- 2026-08-31: 71

## Common questions

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

ai.sitectrl/sitectrl is an MCP server listed in the public MCP registry as ai.sitectrl/sitectrl. Your AI builds real hosted websites: describe it, get a live site with SSL, forms, analytics. Free. This page covers its hosted endpoint (https://mcp.sitectrl.ai/mcp).

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

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

ai.sitectrl/sitectrl exposes 13 tools: whoami, list_sites, get_site, create_site, get_build_status, and 8 more. Their descriptions and schemas cost roughly 1,552 tokens of context every time the server is loaded.

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

Yes. ai.sitectrl/sitectrl 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.sitectrl/sitectrl MCP server still maintained?

ai.sitectrl/sitectrl is still listed as active in the MCP registry. We last reached this channel on 21 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.sitectrl.ai/mcp
- Website: https://sitectrl.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-sitectrl-sitectrl/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-sitectrl-sitectrl/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-sitectrl-sitectrl/mcp