Skip to content

sitectrl MCP server

ai.sitectrl/sitectrlsitectrl.aistreamable-httpv1.0.0Scanned

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

15 tools: 3 can delete or cancel things, 4 change things and 8 only read.

Tools: 3 delete, 0 irreversible, 4 write, 8 read.
  • Reads private data · 3
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the sitectrl MCP server can do

The sitectrl MCP server is published by sitectrl.ai, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (3 tools: write_site_files, publish_site and add_component) and create or change data (4 tools: create_site, edit_site, get_site_context and patch_site_file). 8 tools only read.

3 tools read private data (whoami, list_site_files and read_site_file); 2 tools bring in text other people can write (whoami and get_site); 1 tool can send data out of your system (publish_site). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 3Claude Code: deny
  • add_componentInsert 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 s…No findings

    Why it is in this group

    • The name "add_component" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
  • publish_sitePublish the site's draft to the LIVE site (hosted sites).Can send data outNo findings

    Why it is in this group

    • The name "publish_site" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "publish_site" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
  • write_site_filesCall get_site_context first.No findings

    Why it is in this group

    • The name "write_site_files" says "write": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
Changes things 4Claude Code: ask
  • create_siteBuild a brand-new hosted website from a plain-language description.No findings

    Why it is in this group

    • The name "create_site" says "create": a word for a change.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • edit_siteAsk sitectrl's AI editor to change an existing site ('add a contact page', 'make the hero darker').No findings

    Why it is in this group

    • The name "edit_site" says "edit": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • get_site_contextCALL THIS BEFORE ANY WRITE.1 finding

    Why it is in this group

    • The name "get_site_context" says "get": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_site_context" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "get_site_context" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
  • patch_site_fileCall get_site_context first.No findings

    Why it is in this group

    • The name "patch_site_file" says "patch": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
Only reads 8Show 8 read-only tools
  • get_analyticsThe site's private first-party traffic: pageviews/visitors/sessions/clicks totals, top pages, referrers, devices.No findings

    Why it is in this group

    • The name "get_analytics" says "get": a word for reading.
    Description, as the server wrote it
    The site's private first-party traffic: pageviews/visitors/sessions/clicks totals, top pages, referrers, devices. Windows: 24h, 7d, 30d.

    Annotations the server declares

    • readOnlyHint: true
  • get_build_statusCheck whether a site started by create_site has finished.No findings

    Why it is in this group

    • The name "get_build_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_siteDetails for one site: live URL, draft URL, status.Reads text others writeNo findings

    Why it is in this group

    • The name "get_site" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Details for one site: live URL, draft URL, status.

    Annotations the server declares

    • readOnlyHint: true
  • list_site_filesList the files in a site's draft tree (paths + sizes).Reads private dataNo findings

    Why it is in this group

    • The name "list_site_files" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_site_files" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    List the files in a site's draft tree (paths + sizes).

    Annotations the server declares

    • readOnlyHint: true
  • list_sitesList the user's sitectrl sites with their live URLs and hosting platform.No findings

    Why it is in this group

    • The name "list_sites" says "list": a word for reading.
    Description, as the server wrote it
    List the user's sitectrl sites with their live URLs and hosting platform.

    Annotations the server declares

    • readOnlyHint: true
  • read_site_fileRead one file from a site's draft tree (text, or base64 for binary; 512 KB cap).Reads private dataNo findings

    Why it is in this group

    • The name "read_site_file" says "read": a word for reading.

    What it can reach

    • private-dataThe name "read_site_file" says "read" and "file": it reads files.
    • private-dataThe description's first sentence says "read" and "file": it reads files.
    Description, as the server wrote it
    Read one file from a site's draft tree (text, or base64 for binary; 512 KB cap). Returns a 'hash' of the current bytes.

    Annotations the server declares

    • readOnlyHint: true
  • search_domainsSearch real domain availability + prices (com/net/org/co/io/site and more).No findings

    Why it is in this group

    • The name "search_domains" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • whoamiThe connected sitectrl account: email, plan status, free-site slot, and credit balance.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "whoami" says "whoami": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The connected sitectrl account: email, plan status, free-site slot, and credit balance.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__sitectrl__publish_site"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.sitectrl.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.sitectrl.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (3 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.sitectrl.ai/mcp: tools/list returned 15 tools to an anonymous client, including write_site_files (destructive), publish_site (destructive), add_component (destructive), create_site (write), edit_site (write) and 2 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 5 to 7

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_site_context" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "get_site_context" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 4 changed.+2 added~4 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 7.View diff
    • Tools that change things, listed without credentials: 5 to 7

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http sitectrl https://mcp.sitectrl.ai/mcp
claude mcp add --transport http sitectrl https://mcp.sitectrl.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__sitectrl__whoami",
      "mcp__sitectrl__list_sites",
      "mcp__sitectrl__get_site",
      "mcp__sitectrl__get_build_status",
      "mcp__sitectrl__list_site_files",
      "mcp__sitectrl__read_site_file",
      "mcp__sitectrl__search_domains",
      "mcp__sitectrl__get_analytics"
    ],
    "ask": [
      "mcp__sitectrl__create_site",
      "mcp__sitectrl__edit_site",
      "mcp__sitectrl__get_site_context",
      "mcp__sitectrl__patch_site_file"
    ],
    "deny": [
      "mcp__sitectrl__write_site_files",
      "mcp__sitectrl__publish_site",
      "mcp__sitectrl__add_component"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sitectrl. Review it before you use it.

Capability tags behind 5 rules
  • mcp__sitectrl__whoami private-data, untrusted-input
  • mcp__sitectrl__get_site untrusted-input
  • mcp__sitectrl__list_site_files private-data
  • mcp__sitectrl__read_site_file private-data
  • mcp__sitectrl__publish_site outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.sitectrl/sitectrl/verify?hash=8219c488561f85a762b3478aa06b85e1036bab030ca882dc31cdc384b5d5d62d" | jq -e '.changed == false'

Pinned hash 8219c488561f, from Nov 11, 2026, 22:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.sitectrl/sitectrl/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.sitectrl/sitectrl
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.sitectrl/sitectrl.svg)](https://radar.anlyon.com/servers/ai.sitectrl/sitectrl)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

sitectrl MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the sitectrl MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the sitectrl MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: write_site_files, publish_site and add_component.

Can the sitectrl MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the sitectrl MCP server have?

15 tools: 3 destructive, 4 write, 8 read. write_site_files, publish_site, add_component, create_site, edit_site, get_site_context, patch_site_file, whoami and 7 more.

Does the sitectrl MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the sitectrl MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_site.

Has the sitectrl MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.