ai.sitectrl/sitectrl
REMOTE · MCP.SITECTRL.AI · SCANNED SEP 21
Your AI builds real hosted websites: describe it, get a live site with SSL, forms, analytics. Free.
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% 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 14 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
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
claude mcp add --transport http ai-sitectrl-sitectrl 'https://mcp.sitectrl.ai/mcp'
{
"mcpServers": {
"ai-sitectrl-sitectrl": {
"url": "https://mcp.sitectrl.ai/mcp"
}
}
} {
"servers": {
"ai-sitectrl-sitectrl": {
"type": "http",
"url": "https://mcp.sitectrl.ai/mcp"
}
}
} [mcp_servers.ai-sitectrl-sitectrl] url = "https://mcp.sitectrl.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-sitectrl-sitectrl": {
"type": "remote",
"url": "https://mcp.sitectrl.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-sitectrl-sitectrl --url 'https://mcp.sitectrl.ai/mcp' --transport streamable-http
mcp_servers:
ai-sitectrl-sitectrl:
url: "https://mcp.sitectrl.ai/mcp" {
"McpServers": {
"ai-sitectrl-sitectrl": {
"Transport": "http",
"Url": "https://mcp.sitectrl.ai/mcp"
}
}
} assistant mcp add ai-sitectrl-sitectrl -t streamable-http -u 'https://mcp.sitectrl.ai/mcp'
{
"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.
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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +5
- HTTPS: unverified → pass ▲ security
- 15 Sept 26 +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.
- 14 Sept 26 −1
- 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
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 8 Sept 26 +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.
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 21 Sept 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 | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 53f40a8062c90af0abe28cc57c02e9476f4 |
| 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 | 3799 | 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 |
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 →
add_component Add a library 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.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | object | yes | – |
| fields | object | yes | 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 | yes | – |
| pages | – | – | "all", or an array of page paths, e.g. ["index.html", "about.html"] |
| slug | string | yes | – |
No output schema declared.
No examples provided.
create_site Create a new site ~343
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Short human name for the site, e.g. 'Whitney Apparel'. |
| template | string | – | Starting template (guest builds; default local-services). |
No output schema declared.
No examples provided.
edit_site Edit site (AI developer) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| instruction | string | yes | The change to make, in plain language. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_analytics Get site analytics ~65
The site's private first-party traffic: pageviews/visitors/sessions/clicks totals, top pages, referrers, devices. Windows: 24h, 7d, 30d.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| window | string | – | – |
No output schema declared.
No examples provided.
get_build_status Check a site build ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | yes | The claim_token from create_site. |
No output schema declared.
No examples provided.
get_site Get site details ~34
Details for one site: live URL, draft URL, status.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The site's slug from list_sites. |
No output schema declared.
No examples provided.
list_site_files List site files ~29
List the files in a site's draft tree (paths + sizes).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_sites List my 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.
publish_site Publish to live 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
read_site_file Read a site file ~45
Read one file from a site's draft tree (text, or base64 for binary; 512 KB cap).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
search_domains 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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Domain or name to check, e.g. 'sierratrailcoffee.com'. |
No output schema declared.
No examples provided.
whoami Who am I ~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 Write site files ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
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.