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.

Cactal

REMOTE · API.CACTAL.AI

The website platform for AI agents. One API to build, host, and operate real websites.

Available components

+3 this week 69 Trust /100

Last scanned (21 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Recent critical change

Authorization (1 Nov 2026). See the changelog before you install this server.

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 Security57
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 13572 tokens (~161/item across 84 items; 84 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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 37% 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 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 85 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • Tool “skills_read” rewrote its description, which is the text the model reads security
    • “webResearch_probe” reworded the description of “presets” cosmetic
  • 18 Nov 26 +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.

  • 16 Nov 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 Nov 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.

  • 12 Nov 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.

  • 10 Nov 26 +1

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

  • 8 Nov 26 +1

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

  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ 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 21 Nov 2026 · Probed https://api.cactal.ai/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.cactal.ai CN=YR1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 RSA 2048 SHA256-RSA 6b91555c30c17ee82a727954e077b20fc62
SANs: api.cactal.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.cactal.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
cactal.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.cactal.ai/v1/mcp Verified 200
http (plaintext) http://api.cactal.ai/v1/mcp HTTPS enforced 301 https://api.cactal.ai/v1/mcp
MCP tools · 84 exposed · ~13,169 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
cms_collections_create ~159

Creates a collection in the website’s CMS. `slug` uses lowercase letters, digits, and hyphens (max 64 characters, starting with a letter) and must be unique among the website’s active collections; `displayName` is 1–200 characters and `description` up to 2,000. Optionally pass `fields` (up to 100, same shape as the create-field body) to define the schema in the same call. A website can hold at most 100 active collections; the limit is enforced with a conflict error.

NameTypeReqDescription
description–––
displayNamestringyes–
fieldsarray––
slugstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

cms_collections_delete ~92

Soft-deletes the collection, making it and all of its items unreachable through the API; the slug becomes reusable. Refused with a conflict while any reference field in another collection targets this collection — delete those fields first. If the website has a published version, the deletion is validated against the published site’s content queries and rejected when the site still depends on the collection.

NameTypeReqDescription
collectionIdstringyes–

No output schema declared.

No examples provided.

cms_collections_update ~167

Updates `displayName` (1–200 characters), `description` (up to 2,000 characters; pass `null` to clear), and/or `slug` (a rename). A slug change fails with a conflict when another active collection in the website already uses it, and when the website has a published version the rename is validated against the published site’s content queries and rejected when it would break them.

NameTypeReqDescription
collectionIdstringyes–
description–––
displayNamestring––
slugstring–New slug for the collection — a rename. Omit to keep the current slug. Must be unique among the website’s active collections; when the website has a published version the rename is validated against…

No output schema declared.

No examples provided.

cms_fields_create ~236

Adds a typed field at the end of the collection’s field order. `key` is lowercase snake_case (max 64 characters), must be unique in the collection, and cannot use the reserved metadata names `id`, `slug`, `publishedAt`, `publishAt`, `createdAt`, `updatedAt`, or `position`; `type` is immutable after creation. `reference` and `multi_reference` fields require a `targetCollectionId` in the same website, and `option` fields require `config.choices` (1–1,000 choices). A collection can hold at most 100 fields, and `required: true` is rejected while the collection has active items — add the field as optional, backfill every item, then mark it required.

NameTypeReqDescription
collectionIdstringyes–
configobject––
description–––
displayNamestringyes–
example–––
isUniqueboolean––
keystringyes–
requiredboolean––
targetCollectionIdstring––
typestringyes–

No output schema declared.

No examples provided.

cms_fields_delete ~85

Permanently deletes the field and its stored values: the key is stripped from every item’s `data`, and reference or asset attachments made through the field are removed. This cannot be undone. If the website has a published version, the deletion is validated against the published site’s content queries and rejected when the site still depends on the field.

NameTypeReqDescription
fieldIdstringyes–

No output schema declared.

No examples provided.

cms_fields_update ~387

Updates `displayName`, `description`, `required`, `isUnique`, `example`, and (for `option` fields only) `config`; `type` and `targetCollectionId` are immutable. Setting `required: true` is rejected until every active item has a valid value for the field. Setting `isUnique: true` enforces uniqueness on all future writes and fails with a conflict when existing values already collide; unique is not supported for `plain_text`, `markdown`, `multi_reference`, `image`, `gallery`, or `file` fields. Pass `key` to rename the field’s key: the key is atomically migrated in every stored item’s `data` in the same transaction (no values are lost), a conflict is returned when the new key is already used in the collection, and when the website has a published version the rename is validated against the published site’s content queries. Pass `position: "first"` or `"last"`, or `"before"` / `"after"` together with `anchorFieldId`, to move the field within the collection’s display order.

NameTypeReqDescription
anchorFieldIdstring–Sibling field to move against when `position` is `"before"` or `"after"`.
configobject––
description–––
displayNamestring––
example–––
fieldIdstringyes–
isUniqueboolean––
keystring–New key for the field — a rename. Omit to keep the current key. Atomically migrates the key in every stored item’s `data`, so no values are lost.
positionstring–Moves the field within the collection’s display order. Omit to leave the order unchanged. `"before"` / `"after"` require `anchorFieldId`.
requiredboolean––

No output schema declared.

No examples provided.

cms_items_backreferences_list ~112

Lists active items that reference the target item through a `reference` or `multi_reference` field, newest first, with cursor pagination (default 20 per page, maximum 100). Each source item appears once even when multiple fields point to the target. `depth` (0–3, default 0) controls reference hydration in the returned source items.

NameTypeReqDescription
cursorstring––
depthinteger––
itemIdstringyes–
limitinteger––

No output schema declared.

No examples provided.

cms_items_create ~336

Creates an item at the end of the collection’s manual order. Scalar values go in `data` keyed by field key and are validated against the field types — unknown keys are rejected, required fields must be present, `plain_text` and `markdown` are capped at 1,048,576 bytes (markdown must not contain raw HTML), `date` values are ISO 8601 with timezone, and `color` values are normalized to hex. Relationship and asset values go in the side maps: `references` (`reference`: an item id; `multi_reference`: an ordered array of up to 1,000 ids), `images` (`image`: an asset id or `{ assetId, altText }`; `gallery`: an ordered array of up to 25 of those), and `files` (`file`: an asset id or `{ assetId }`). `slug` is optional — it is derived from `data.title` or `data.name` when omitted. Set a non-future `publishedAt` to create an already-published item, or a future `publishAt` to schedule it; the two fields are mutually exclusive.

NameTypeReqDescription
collectionIdstringyes–
dataobject––
filesobject––
imagesobject––
publishAt––Future absolute timestamp for scheduled publication. Cannot be combined with `publishedAt`.
publishedAt––Initial publication timestamp. Must not be in the future. Omit for a draft, or use `publishAt` to schedule publication.
referencesobject––
slugstring––

No output schema declared.

No examples provided.

cms_items_delete ~70

Soft-deletes the item: it disappears from reads, list results, and backreferences, and fields referencing it read `null` (single reference) or shrink (multi-reference). Its slug becomes reusable, and incoming references are preserved so the item can be restored.

NameTypeReqDescription
itemIdstringyes–

No output schema declared.

No examples provided.

cms_items_get ~265

Returns one item, looked up by `itemId` or by the `collectionId` + `slug` pair (provide exactly one of the two). The `data` object is complete and schema-shaped: every currently-defined field is present and missing optional values read as `null`. `depth` (0–3, default 0) embeds referenced items in place of their ids, one level per unit; referenced items that were deleted read as `null` (single reference) or are omitted from arrays (multi-reference). Set `published` to `"true"` or `"false"` to match only a published or only a draft item (a mismatch reads as not found). List items that reference it with `cms.items.backreferences.list`.

NameTypeReqDescription
collectionIdstring–Collection to look the item up in by slug. Pair with `slug`.
depthinteger––
itemIdstring–Item id. Provide either this or the `collectionId` + `slug` pair.
published––Only match a published (`"true"`) or draft (`"false"`) item; a mismatch reads as not found. Omit to match either.
slugstring–Item slug within the collection. Pair with `collectionId`.

No output schema declared.

No examples provided.

cms_items_list ~367

Returns the collection’s active items in manual (drag) order by default, 20 per page (max 100); paginate with `cursor` or with 1-based `page` offsets, not both. Filter with `published` (`true` / `false`) and a JSON-encoded `filter` map of `{ fieldKey: { operator: value } }` — operators `eq`, `neq`, `in`, `nin`, `gt`, `gte`, `lt`, `lte`, `contains`, `startsWith`, `endsWith`, and `exists`, plus `slug` equality on reference fields; metadata keys are `id`, `slug`, `publishedAt`, `publishAt`, `createdAt`, and `updatedAt`. Combine clauses with `filterLogic` (`and` by default, or `or`). `search` accepts a query string (1–200 characters) or JSON `{ "query", "fields" }` to restrict which text fields are searched; `sort` accepts JSON `{ "kind": "field" | "meta", "field", "direction": "asc" | "desc" }`, where sortable metadata fields are `id`, `slug`, `publishedAt`, `publishAt`, `createdAt`, `updatedAt`, and `position`. `depth` (0–3, default 0) embeds referenced items in place of their ids, one level per unit.

NameTypeReqDescription
collectionIdstringyes–
cursorstring––
depthinteger––
filterstring––
filterLogicstring––
limitinteger––
pageinteger––
published–––
searchstring––
sortstring––

No output schema declared.

No examples provided.

cms_items_restore ~50

Restores a soft-deleted item, making it readable again and re-exposing references to and from it. Returns 404 when the item is not currently deleted.

NameTypeReqDescription
itemIdstringyes–

No output schema declared.

No examples provided.

cms_items_setPublished ~186

Use exactly one publication action: `published: true` publishes immediately and sets `publishedAt` to now; a future `publishAt` schedules a draft for automatic publication; `published: false` unpublishes an item or cancels its schedule. A published item must be unpublished before it can be scheduled because CMS items do not have revision snapshots. Published websites read only items with an actual `publishedAt`, so immediate and scheduled promotion become visible without a site republish. Repeating the same action is idempotent.

NameTypeReqDescription
itemIdstringyes–
publishAtstring–Future absolute timestamp for scheduling. Omit `published`; scheduled items remain hidden until the promotion job runs.
publishedboolean–`true` publishes immediately; `false` unpublishes or cancels a schedule. Use `publishAt` instead to schedule publication.

No output schema declared.

No examples provided.

cms_items_update ~288

Patches an item; omitted fields are left untouched. Keys in `data` are merged into the existing values and validated the same way as on create, while each key provided in `references`, `images`, or `files` replaces that field’s value wholesale — pass `null` (or `[]` for multi-valued fields) to clear an optional field. `slug` renames the item’s slug; slug and unique-field collisions fail with a conflict. Pass `position: "first"` or `"last"`, or `"before"` / `"after"` together with `anchorItemId`, to move the item within the collection’s manual order — the default sort for item lists.

NameTypeReqDescription
anchorItemIdstring–Sibling item to move against when `position` is `"before"` or `"after"`.
dataobject––
filesobject––
imagesobject––
itemIdstringyes–
positionstring–Moves the item within the collection’s manual order — the default sort for item lists. Omit to leave the order unchanged. `"before"` / `"after"` require `anchorItemId`.
referencesobject––
slugstring–New slug for the item — a rename. Omit to keep the current slug. Must be unique among the collection’s active items.

No output schema declared.

No examples provided.

cms_schema_snapshot ~62

Returns every active collection and field of a website in one call — the full content model. Collections are ordered newest first; fields are grouped by collection in display order. Use this to discover the schema before reading or writing items.

NameTypeReqDescription
websiteIdstringyes–

No output schema declared.

No examples provided.

docs_read ~91

Read one Cactal documentation page as Markdown. Pass a page path from docs search results, for example "concepts/publishing" or "agents/agent-safe-publishing". Pass "llms.txt" for an index of every page with titles and descriptions.

NameTypeReqDescription
pathstringyesDocs page path, for example "concepts/publishing". Pass "llms.txt" for the index of every page.

No output schema declared.

No examples provided.

docs_search ~91

Search the Cactal product documentation: concepts, guides, agent workflows, platform limits, and the API reference. Returns matching Markdown excerpts with page paths; read a full page with the docs read operation. Consult the docs before non-trivial or unfamiliar work such as source-code editing, publishing, or CMS schema changes.

NameTypeReqDescription
querystringyesPlain-language question or keywords, for example "how does publishing work".

No output schema declared.

No examples provided.

feedback_submit ~129

Adds user-requested free-form feedback to the Cactal product-feedback inbox. Describe what happened and what would have made the experience better. Agents must set `authorKind` to `agent` even when acting through a user OAuth connection. Never include credentials, secrets, raw sensitive user content, or unnecessary personal or customer data.

NameTypeReqDescription
authorKindstringyesWho wrote the feedback. An AI agent must pass "agent" even when connected through a user OAuth token.
feedbackstringyesConcise free-form feedback describing the Cactal problem or limitation and what would have made the experience better.

No output schema declared.

No examples provided.

profile_get ~68

Returns who this credential acts for (a stable `id`, plus `name` and `email` for a person) and the organizations it can work in. An organization lists `websites` only when access is limited to those websites. Use an organization `id` to list or create websites.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

skills_read ~457

Read the matching Cactal skill before acting: source-editing-workflow before source edits, design-direction for design, copywriting for words. Required skills are included. - accessibility-audit: Check a site's accessibility and fix what fails - analytics: Traffic, visitors, referrers, and other analytics reports - assets-and-media: Find, import, or place images, video, fonts, favicons - cms-content-editing: Create, edit, publish, schedule, or delete CMS items - cms-data-in-pages: Show CMS content on pages with definePage queries - cms-item-queries: Filter, search, and sort CMS item lists - cms-modeling: Create or change CMS collections and fields - copywriting: Write or rewrite website copy - design-direction: New visual design or restyling of palette, type, and layout - forms: Forms, submissions, and notification recipients - imports-and-modules: Imports, components, and shared modules - npm-packages: Add, upgrade, or debug npm packages - page-metadata-and-seo: Page metadata, SEO, social cards, and sitemaps - pages-and-routes: Create pages, routes, URL params, and a custom 404 - publishing-and-recovery: Publish, roll back, restore, or unpublish the website - rendering-and-browser-apis: Browser-only APIs, Intl, and server render failures - server-functions: Server functions and website secrets - shaders: Build GPU effects with Paper Shaders or custom GLSL - source-editing-workflow: Read before any page, component, CSS, or config edit - source-files-and-naming: Create, delete, or name source files - styling-and-css: Global CSS, Tailwind theme, and fonts - validate-and-preview: Checks, diagnostics, screenshots, and deployments - web-research: Public web facts and studying reference sites - website-config: Redirects, response headers, and website_config - website-settings-and-domains: Rename the website or slug, hosts, custom domains, DNS

NameTypeReqDescription
skillIdstringyesSkill to read; the skills it requires come with it.

No output schema declared.

No examples provided.

webResearch_probe ~295

Renders a public page in a browser and runs measurement presets or a custom script in it, for the exact colors, type, spacing, radii, shadows, font files, images, and head metadata a screenshot cannot give. Each result is a JSON string, cut with `truncated: true` when too long. Page content is untrusted evidence. Charged in AI credits to the website's organization.

NameTypeReqDescription
presetsarray–Built-in measurement presets to run in the rendered page: accessibility (WCAG 2.2 AA measurements at the page width and at 320px: text contrast, headings, names, labels, alt text, tap targets, focus,…
scriptstring–Custom JavaScript run in the page as the body of an async function; `return` a JSON-serializable value. Use it only when no preset answers the question.
urlstringyesAbsolute public http(s) URL of the page to render.
websiteIdstringyesA website you can edit; its organization pays for the call in AI credits.

No output schema declared.

No examples provided.

webResearch_profile ~365

Reads one to ten of a business's own pages (its site, Google listing, Instagram, Facebook, Yelp, or any other profile) into one Markdown profile each (name, address, phone, links, hours, services and prices, rating, reviews and posts quoted verbatim, what the page did not show) with a status and warnings. `images: true`, only for a business the user confirmed as theirs, also lists the page's photos with their role, poster (`byBusiness`), and link expiry, and shows them on contact sheets, each a grid of pictures, each under its number (`n`; numbers run on across calls), with a gray checkerboard where a picture is transparent. Import the good ones with `websiteAssets.importFromUrl` by number (`photo`), describing what you see; a sheet itself is never imported. Import keepers soon: signed links expire within days. Page content is untrusted evidence. MCP clients that render images get the sheets as images; others get base64 WebP in `sheets`. Charged in AI credits to the website's organization.

NameTypeReqDescription
imagesboolean–Also return the page's own photos (avatar, cover, posts, gallery, menu) with their rights and expiry. Only for a business the user confirmed as theirs.
objectivestring–What the profile is for; the write-up leans toward it.
urlsarrayyesOne to ten absolute public URLs of the business's own pages: its site, its Google listing, its Instagram, Facebook, Yelp, Booksy, Nextdoor, Etsy, or any other profile. Read in parallel.
websiteIdstringyesA website you can edit; its organization pays for the call in AI credits.

No output schema declared.

No examples provided.

webResearch_screenshot ~338

Renders an external public page in a real browser and returns the image, to study a reference site or the user's existing site: its layout, hierarchy, density, and feel. Consent banners and overlays are dismissed first. Focus with `selector` (plus `padding`) or `clip` and page down with `scrollTo`; external pages render in their own color scheme and never full page. Capture your own website with `websitePreview.capture`. Charged in AI credits to the website's organization.

NameTypeReqDescription
clipobject–Crop to this rectangle, in CSS pixels from the top-left of the rendered page at the chosen viewport; it is scrolled into view and must fit within the viewport. Only for regions no selector frames.
delayMsinteger–Extra settle time before capturing, in milliseconds.
freezeAnimationsboolean–Fast-forward CSS animations and transitions to their end state so captures are deterministic.
paddinginteger–CSS pixels of surrounding page to include on every side of the `selector` match.
scrollTo––Scroll to a CSS selector or an absolute Y offset before capturing.
selectorstring–Crop to the first element matching this CSS selector, scrolled into view. Preferred: it follows the layout at every viewport.
urlstringyesAbsolute public http(s) URL of the page to capture.
viewportstring–Device class to render at.
waitForSelectorstring–Wait for this CSS selector to match before capturing.
websiteIdstringyesA website you can edit; its organization pays for the call in AI credits.

No output schema declared.

No examples provided.

webResearch_viewImage ~195

Fetches 1 to 48 public image URLs and returns the pictures; nothing is stored. Up to 4 come back full size (an SVG also returns the start of its source); more come back on contact sheets, each a grid of pictures, each under its number (`n`; numbers run on across calls), with a gray checkerboard where a picture is transparent. Import the good ones with `websiteAssets.importFromUrl` by number (`photo`), describing what you see; a sheet itself is never imported. MCP clients that render images get the pictures as images; others get base64 WebP in `pictures`. Not billed to credits.

NameTypeReqDescription
urlsarrayyesAbsolute public image URLs to look at: up to 4 come back full size, more come back on numbered contact sheets.
websiteIdstringyesA website you can edit; its organization pays for the call in AI credits.

No output schema declared.

No examples provided.

websiteAnalytics_query_get ~494

Returns aggregate engagement totals — page views, distinct visitors, visits, bounces, and total time in seconds — for a date range, optionally broken down by one dimension. Use it to answer "how much traffic did the site get" and "what are the top pages/referrers/countries" style questions; use the timeseries endpoint when you need values over time instead. `startAt` and `endAt` are Unix epoch milliseconds; optional filter parameters (path, referrer, country, event, UTM fields, ...) narrow the data. Without `dimension` the response carries the totals alone. With `dimension` (e.g. `path` for top pages, `referrer` for top referrers, `country` for top countries) the response also carries `rows`: up to `limit` (default 25, max 1000) values of that dimension ranked by page views, each with its own engagement totals. Requires a plan that includes analytics (403 otherwise); all-zero totals until the website is published and has traffic.

NameTypeReqDescription
browserstring––
citystring––
cohortstring––
countrystring––
devicestring––
dimensionstring–Break the range down by this dimension, e.g. `path` for top pages, `referrer` for top referrers, `country` for top countries. Omit for totals only.
distinctIdstring––
endAtintegeryes–
eventstring––
hostnamestring––
languagestring––
limitinteger–Maximum number of dimension rows to return (default 25, max 1000). Only used when `dimension` is set.
osstring––
pathstring––
querystring––
referrerstring––
regionstring––
segmentstring––
startAtintegeryes–
tagstring––
titlestring––
utmCampaignstring––
utmContentstring––
utmMediumstring––
utmSourcestring––
utmTermstring––
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteAnalytics_realtime_get ~112

Returns a compact snapshot of traffic over Umami's trailing 30-minute realtime window: total page views, distinct visitors, tracked custom events, and distinct countries, plus the snapshot timestamp. The visitor total is not directly comparable to the removed `active` endpoint's five-minute count. Use it to see recent activity; use the query endpoint for historical ranges. Requires a plan that includes analytics (403 otherwise); all-zero totals until the website is published and has traffic.

NameTypeReqDescription
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteAnalytics_timeseries_get ~521

Returns one traffic time series bucketed by `unit` (`year`, `month`, `day`, `hour`, or `minute`). `series` selects which: `pageviews` returns parallel `pageviews` and `sessions` arrays with one point per time bucket (and accepts `compare` — `prev` or `yoy` — to request comparison data for the previous period or year), while `events` returns tracked custom-event counts as one `events` point per event name per time bucket. Only the requested series' fields are present in the response. `startAt` and `endAt` are Unix epoch milliseconds; `timezone` is an IANA name (e.g. `America/New_York`) that controls bucket boundaries; optional filter parameters narrow the data. The series is capped to the most recent `maxPoints` time buckets (default 30, max 500); a `truncated` field reports when the cap was applied. Requires a plan that includes analytics (403 otherwise); empty until the website is published and has traffic.

NameTypeReqDescription
browserstring––
citystring––
cohortstring––
comparestring–Request comparison data alongside the primary series: `prev` for the previous period, `yoy` for the same range one year earlier. Only valid when `series` is `pageviews`.
countrystring––
devicestring––
distinctIdstring––
endAtintegeryes–
eventstring––
hostnamestring––
languagestring––
maxPointsinteger––
osstring––
pathstring––
querystring––
referrerstring––
regionstring––
segmentstring––
seriesstringyesWhich time series to return: `pageviews` for page views and sessions per bucket, `events` for tracked custom-event counts per event name per bucket.
startAtintegeryes–
tagstring––
timezonestring––
titlestring––
unitstringyes–
utmCampaignstring––
utmContentstring––
utmMediumstring––
utmSourcestring––
utmTermstring––
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteAssets_delete ~57

Archives the asset: it immediately stops appearing in list responses and its id returns 404 from every asset endpoint. Archival cannot be undone through the API; previously issued CDN URLs keep serving the file.

NameTypeReqDescription
assetIdstringyes–

No output schema declared.

No examples provided.

websiteAssets_get ~71

Returns the asset with `description`, `category`, and its CDN delivery shape: for transformable images `url` is the optimized 1920px default and `originalUrl` the original bytes; both never expire. MCP clients that render images also receive the image.

NameTypeReqDescription
assetIdstringyes–

No output schema declared.

No examples provided.

websiteAssets_importFromUrl ~286

Fetches 1-10 public http(s) URLs server-side, one at a time, and stores each as a ready asset with no upload or finalize step. Media only: images, fonts, PDF, audio, video, dotLottie, and Rive; text, data, documents, and archives are refused. Images, fonts, and PDFs must parse as what they claim, hosts on private addresses are rejected, the upload kind and MIME rules apply, and each download is capped at 30 MiB (larger files must be uploaded directly). Each item may carry a `description` and, for images, a `category`. Name each item by `url`, or by `photo`: the number over a picture on contact sheets `webResearch.profile` or `webResearch.viewImage` showed you, which saves copying its long signed link. `assets` carries successes with CDN URLs and `sourceUrl`; `errors` carries failures typed `invalid_url`, `non_public_address`, `unreachable`, `too_large`, `unsupported_type`, `signature_expired`, or `unknown_photo` (a number you were not shown or that expired; look at the pictures again for current numbers). Import only assets you have the right to use.

NameTypeReqDescription
itemsarrayyesEach item succeeds or fails on its own.
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteAssets_list ~213

Returns ready assets newest first as compact rows (`description`, `category`, dimensions, `url`, `srcSet`); fetch one asset for `originalUrl` and `variants`. Filter by `kind`, `category`, `type` (the broad MIME family: image, video, audio, font, or document), or `search`, which prefix-matches each term against the filename, description, and category; every term must match, else any term. Page size defaults to 50 (max 100).

NameTypeReqDescription
categorystring–Only images with this category.
cursorstring––
kindstring––
limitinteger––
searchstring–Matches filename, description, and category; each term matches as a prefix.
typestring–Broad file type derived from the MIME type: image, video, audio, font, or document (everything else). Combines with kind, category, and search.
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteAssets_update ~70

Changes `filename`, `description`, or `category`. Pass only the fields to change; `null` clears a field. `category` is images only.

NameTypeReqDescription
assetIdstringyes–
category–––
description–––
filenamestring–Delivery URLs never change.

No output schema declared.

No examples provided.

websiteDomains_createCustomDomain ~216

Claims `hostname` for this website and registers it with the Cactal edge. Custom domains must first be enabled for the website (`websiteDomains.setEnabled`, owner-only — enabling is the billing moment); the request fails with 403 `custom_domains_disabled` otherwise. Adding or removing domains on an enabled website never changes billing. The domain is created in `pending_dns` status, and the returned `dnsRecords` list exactly what to create at your DNS provider: an ownership TXT record on `_cactal.<hostname>` plus a routing record (a CNAME for subdomains or an A record for apex domains). Hostnames must be lowercase ASCII domains (not IP addresses or Cactal platform hosts), each website can have at most 10 custom domains, and a hostname can be claimed by only one website; claims that never verify expire after 7 days. After creating the records, call the verify endpoint or wait for the automatic re-checks.

NameTypeReqDescription
hostnamestringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteDomains_list ~62

Returns every domain record attached to the website, oldest first: the automatically allocated platform subdomain plus any custom domains. Platform subdomains are always `active`; custom domains carry their current verification status and the DNS records still expected.

NameTypeReqDescription
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteDomains_removeCustomDomain ~92

Deregisters the hostname from the Cactal edge and deletes the domain record. If the removed domain was primary, the oldest remaining active custom domain is promoted automatically. If edge deregistration fails, the domain stays in `removing` status and a background sweep retries until it is gone. Platform subdomains cannot be removed.

NameTypeReqDescription
domainIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteDomains_renamePlatformDomain ~187

Moves the website to `<label>.<platform domain>`, the free address every website is allocated at creation. `label` is just the leading part: 1-40 characters, lowercase letters, digits, and inner hyphens, and it may not be one of the labels Cactal reserves. The change takes effect immediately, on published and draft hosts alike. The previous hostname is released at the same moment, with no redirect and no grace period, so any existing links to it break and another website may claim it. Take care on a published site. Fails with 409 when the label is already taken by another website; renaming to the label the website already has is a no-op. Custom domains are unaffected, and if one of them is primary it stays the canonical address.

NameTypeReqDescription
labelstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteDomains_setPrimaryDomain ~94

Makes this domain the canonical hostname for the published website: requests reaching the platform subdomain or any other custom domain are permanently redirected (HTTP 308) to it, preserving path and query. Only `active` custom domains can be made primary — the request fails with 409 otherwise. Any previous primary is cleared in the same transaction.

NameTypeReqDescription
domainIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteDomains_verifyCustomDomain ~173

Re-checks the ownership TXT record, edge readiness, and whether an HTTPS request to the hostname reaches this Cactal domain, then returns the updated status. A customer CDN or reverse proxy in front is supported when it forwards the verification request to Cactal. `failureMessage` distinguishes a missing ownership record, an unreachable hostname, and a hostname served somewhere else. Cactal asks the domain nameservers directly, so new records usually count on the next check, and this endpoint is safe to poll; Cactal also re-checks pending domains automatically (every minute for the first 2 hours, every 5 minutes for the first day, then every 15 minutes). The first custom domain to become active is promoted to primary automatically.

NameTypeReqDescription
domainIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteFavicons_set ~101

Sets the website’s current favicon to a ready PNG, SVG, or ICO image from the same website asset library. Send `assetId: null` to clear it. The change applies immediately to every site host and is independent of source drafts and publishing. Read the current favicon from the `faviconUrl` field on `GET /websites` and `GET /websites/find`.

NameTypeReqDescription
assetId–yes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_list ~112

Returns every form with inbox and spam counts, whether the published site still references it, who it notifies, the number of inbox submissions since the caller last opened the Forms tab, and monthly usage against the Free plan limit (`limit` is null on paid plans). Forms come from `<form method="post" action="/_cactal/forms/<name>">` in the website source and appear here as soon as the draft or published build contains them, before any submission.

NameTypeReqDescription
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_recipients_add ~144

Adds an email address to one form, identified by its name from the action path. New forms notify the organization owners until changed. Organization members and website editors receive submissions immediately; other addresses get a confirmation email (link valid 7 days). `member` and `confirmed` addresses receive email; `pending` addresses must confirm by link; `failing` addresses bounced or complained; `stopped` addresses opted out. Works before the first submission; at most 20 addresses per website.

NameTypeReqDescription
emailstringyesAddress to notify.
formNamestringyesThe form name from the action path.
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_recipients_remove ~60

Stops emailing an address for one form. A form with no recipients emails nobody; its submissions still reach the Forms inbox.

NameTypeReqDescription
formNamestringyes–
recipientIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_recipients_resend ~44

Issues a fresh confirmation link to a pending, failing, or stopped address.

NameTypeReqDescription
recipientIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_submissions_delete ~33

Permanently deletes one submission.

NameTypeReqDescription
submissionIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_submissions_get ~37

Returns one submission with its fields in submitted order.

NameTypeReqDescription
submissionIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_submissions_list ~185

Returns submissions newest first as a cursor-paginated page. Filter by `form` name, `status` (`inbox` by default, or `spam`), and `source` (`published` for real visitors, `draft` for test submissions from the draft preview). Items carry the fields in submitted order, the inferred submitter email and name, page, spam signals, classifier verdict, and notification state. Submission data is personal information: never render it on the public website.

NameTypeReqDescription
cursorstring––
formstring–Only submissions of this form name.
limitinteger––
sourcestring–`published` for real visitors, `draft` for test submissions from the draft preview.
statusstring–`inbox` (default) or `spam`.
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteForms_submissions_setStatus ~94

Moves a submission between the inbox and the spam folder. Restoring to `inbox` sends the notification email if it was never sent. Spam is deleted automatically after 30 days.

NameTypeReqDescription
statusstringyes`spam` hides the submission in the spam folder; `inbox` restores it and sends any missed notification.
submissionIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteFunctions_invoke ~93

Runs one of the draft site's `http` server functions with the website's secrets and returns its result, exactly as page code on the draft would receive it. It makes the function's real outgoing requests. Counts toward the plan's monthly calls.

NameTypeReqDescription
namestringyesAn `http` server function.
payload––The handler's first argument, as JSON.
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteFunctions_runs_get ~55

Returns one run with its input, output, console output and outgoing requests. Secret values, in plain and common encoded forms, are redacted.

NameTypeReqDescription
runIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

websiteFunctions_runs_list ~79

Lists a website's server function runs, newest first, for `http` calls and form submissions alike. Secret values are redacted. Runs are kept for 30 days.

NameTypeReqDescription
cursorstring––
limitinteger––
namestring–Only runs of this function.
websiteIdstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Cactal MCP server?

Cactal is a hosted endpoint at https://api.cactal.ai/v1/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 · api.cactal.ai

# add to Claude Code
claude mcp add --transport http ai-cactal-cactal 'https://api.cactal.ai/v1/mcp'
Common questions

What is the Cactal MCP server?

Cactal is an MCP server listed in the public MCP registry as ai.cactal/cactal. The website platform for AI agents. One API to build, host, and operate real websites. This page covers its hosted endpoint (https://api.cactal.ai/v1/mcp).

Is the Cactal MCP server safe to use?

Cactal scores 69 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 Cactal MCP server expose?

Cactal exposes 84 tools: feedback_submit, websites_list, websites_get, websites_create, websites_rename, and 79 more. Their descriptions and schemas cost roughly 13,169 tokens of context every time the server is loaded.

Does the Cactal MCP server require authentication?

No. We connected to Cactal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Cactal MCP server still maintained?

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

What did VerifyMCP test on the Cactal MCP server?

VerifyMCP ran 13 checks on Cactal, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.