Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.sitectrl/sitectrl

REMOTE · MCP.SITECTRL.AI

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

Available components

0 this week 88 Trust /100

Last scanned (2 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security92
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2234 tokens (~148/item across 15 items; 15 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 Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 39% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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 Oct 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “read_site_file” rewrote its description, which is the text the model reads security
    • Tool “write_site_files” rewrote its description, which is the text the model reads security
    • Schema quality: 1806 → 2234 ▼ functional
    • Tool coverage: 48% → 39% ▼ functional
    • Schema quality: excellent → good functional
    • New tool “get_site_context” functional
    • New tool “patch_site_file” functional
  • 27 Oct 26 0
    • Tool “create_site” rewrote its description, which is the text the model reads security
    • Tool “get_build_status” rewrote its description, which is the text the model reads security
    • “get_build_status” added an optional parameter “slug” cosmetic
    • “get_build_status” reworded the description of “claim_token” cosmetic
    • “get_build_status” made “claim_token” optional cosmetic
  • 4 Oct 26 0
    • “create_site” reworded the description of “template” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 30 Sept 26 0
    • Stability: 0.97 → pass security
  • 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
  • 17 Sept 26 0
    • HTTPS: unverified → pass ▲ security
  • 14 Sept 26 0
    • New tool “add_component”, which the server declares destructive security
    • Tool “write_site_files” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
Diagnostics

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 5 Nov 2026 · Probed https://mcp.sitectrl.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.sitectrl.ai CN=YE2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA384 6edbbee5e8eec30ea1786aa5601a2e255ae
SANs: mcp.sitectrl.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.sitectrl.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
sitectrl.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.sitectrl.ai/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://mcp.sitectrl.ai/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.sitectrl.ai/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.sitectrl.ai/mcp
Authorisation server https://mcp.sitectrl.ai

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.sitectrl.ai/mcp Verified 200
http (plaintext) http://mcp.sitectrl.ai/mcp HTTPS enforced 301 https://mcp.sitectrl.ai/mcp
MCP tools · 15 exposed · ~2,008 tokens

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 →

Tool Tokens
add_component ~477

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.

NameTypeReqDescription
anchorobjectyes–
fieldsobjectyesComponent-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?…
namestringyes–
pages––"all", or an array of page paths, e.g. ["index.html", "about.html"]
slugstringyes–

No output schema declared.

No examples provided.

create_site ~368

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 / live_url) and poll get_build_status — with the returned slug when signed in, with the returned claim_token for a guest build. 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).

NameTypeReqDescription
contact_emailstring–Optional, guest builds only: the user's email — we send the site link and a reminder before the unclaimed site expires.
descriptionstringyesWhat 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_namestringyesShort human name for the site, e.g. 'Whitney Apparel'.
templatestring–Optional override of the starting template. Omit it and the template is chosen from the description.

No output schema declared.

No examples provided.

edit_site ~82

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.

NameTypeReqDescription
instructionstringyesThe change to make, in plain language.
slugstringyes–

No output schema declared.

No examples provided.

get_analytics ~65

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

NameTypeReqDescription
slugstringyes–
windowstring––

No output schema declared.

No examples provided.

get_build_status ~107

Check whether a site started by create_site has finished. Signed in: pass the slug create_site returned (status building / built / failed). Guest build: pass the claim_token — 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.

NameTypeReqDescription
claim_tokenstring–Guest builds: the claim_token from create_site.
slugstring–Signed in: the slug from create_site.

No output schema declared.

No examples provided.

get_site ~34

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

NameTypeReqDescription
slugstringyesThe site's slug from list_sites.

No output schema declared.

No examples provided.

get_site_context ~96

CALL THIS BEFORE ANY WRITE. Returns what sitectrl's own editing agent knows about the site: its notes, brand tokens, page inventory, declared invariants, the platform-owned parts every page must keep (with the exact snippet and why), each HTML file's base_hash, and the edit rules (patch, never regenerate a whole file; writes land in the draft; publish_site goes live).

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_site_files ~29

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

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_sites ~23

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

patch_site_file ~194

Call get_site_context first. Change an existing draft file IN PLACE — the way to modify a page. Each edit is {find, replace} (swap exact text) or {after, insert} (add text right after an anchor); the anchor must appear exactly once in the current file, else nothing is written and you are told why. Edits apply in order. Prefer this to rewriting the page with write_site_files: whole-file rewrites from memory drop or duplicate things. Same checks as write_site_files (keep sc-track.js, data-sc-carry tags and the sc-badge block; no noindex / 'Disallow: /' on a site with its own domain). Optional base_hash (from read_site_file) refuses the edit if the file changed.

NameTypeReqDescription
base_hashstring––
editsarrayyes–
pathstringyes–
slugstringyes–

No output schema declared.

No examples provided.

publish_site ~44

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.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

read_site_file ~55

Read one file from a site's draft tree (text, or base64 for binary; 512 KB cap). Returns a 'hash' of the current bytes.

NameTypeReqDescription
pathstringyes–
slugstringyes–

No output schema declared.

No examples provided.

search_domains ~79

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.

NameTypeReqDescription
querystringyesDomain or name to check, e.g. 'sierratrailcoffee.com'.

No output schema declared.

No examples provided.

whoami ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

write_site_files ~327

Call get_site_context first. Push NEW files (HTML/CSS/JS/images) into a site's DRAFT. To CHANGE an existing page use patch_site_file instead (find/replace on the current file) — rewriting a whole page from memory drops or duplicates things; overwriting an existing .html needs base_hash from read_site_file. 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. Site rules: keep sc-track.js, the data-sc-carry canonical/og:url tags and the sc-badge block; never add noindex or 'Disallow: /' on a site with its own domain. Follow with publish_site to go live.

NameTypeReqDescription
filesarrayyes–
slugstringyes–

No output schema declared.

No examples provided.

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.

remote · mcp.sitectrl.ai

# add to Claude Code
claude mcp add --transport http ai-sitectrl-sitectrl 'https://mcp.sitectrl.ai/mcp'
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 88 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 15 tools: whoami, list_sites, get_site, create_site, get_build_status, and 10 more. Their descriptions and schemas cost roughly 2,008 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.