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.

Cakto

REMOTE · API.MCP.AI · SCANNED SEP 26

Read your Cakto sales: orders, revenue analytics, subscriptions, churn, customers and products.

Available components

0 this week 74 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4147 tokens (~153/item across 27 items; 27 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 Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 28 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
Install

How do I install the Cakto MCP server?

Cakto is a hosted endpoint at https://api.mcp.ai/p_cakto, 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.mcp.ai

# add to Claude Code
claude mcp add --transport http mcp-dir-cakto-mcp 'https://api.mcp.ai/p_cakto'
// .cursor/mcp.json
{
  "mcpServers": {
    "mcp-dir-cakto-mcp": {
      "url": "https://api.mcp.ai/p_cakto"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mcp-dir-cakto-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_cakto"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.mcp-dir-cakto-mcp]
url = "https://api.mcp.ai/p_cakto"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcp-dir-cakto-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_cakto",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mcp-dir-cakto-mcp --url 'https://api.mcp.ai/p_cakto' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mcp-dir-cakto-mcp:
    url: "https://api.mcp.ai/p_cakto"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mcp-dir-cakto-mcp": {
      "Transport": "http",
      "Url": "https://api.mcp.ai/p_cakto"
    }
  }
}
# add to Vellum
assistant mcp add mcp-dir-cakto-mcp -t streamable-http -u 'https://api.mcp.ai/p_cakto'
// mcp.json
{
  "mcpServers": {
    "mcp-dir-cakto-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_cakto"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Sept 26 +1

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

  • 25 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.346 → 0.9.351 functional
  • 12 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.

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 26 Sept 2026 · Probed https://api.mcp.ai/p_cakto

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ai CN=WE1,O=Google Trust Services,C=US 31 Jul 2026 29 Oct 2026 ECDSA 256 ECDSA-SHA256 796a3b1f576e3f2e133c5d19d8f7be3b
SANs: mcp.ai, *.mcp.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.mcp.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
mcp.ai. absent 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.mcp.ai/p_cakto Verified 200
http (plaintext) http://api.mcp.ai/p_cakto Inconclusive 406
MCP tools · 27 exposed · ~4,022 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
authenticate ~99

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

cakto_customers_get ~114

Leitura de clientes na Cakto (para análise/CRM). Ações: - list: lista clientes (filtros: search, page). - get: perfil de UM cliente + histórico de compras (requer customer_id). [Flattened action: get] Bulk support: accepts customer_ids for batched execution.

NameTypeReqDescription
accountstring––
customer_idstring––
customer_idsarray––
pagenumber––
searchstring––

No output schema declared.

No examples provided.

cakto_customers_list ~114

Leitura de clientes na Cakto (para análise/CRM). Ações: - list: lista clientes (filtros: search, page). - get: perfil de UM cliente + histórico de compras (requer customer_id). [Flattened action: list] Bulk support: accepts customer_ids for batched execution.

NameTypeReqDescription
accountstring––
customer_idstring––
customer_idsarray––
pagenumber––
searchstring––

No output schema declared.

No examples provided.

cakto_list_accounts ~40

Lista contas Cakto (apps do painel) vinculadas a este install — id, label e apelido.

NameTypeReqDescription
accountstring––

No output schema declared.

No examples provided.

cakto_offers_create ~172

Cria uma oferta (preço alternativo) para um produto existente na Cakto. É o passo necessário para ter o que oferecer num order bump com preço diferente do principal. Requer o escopo "write offers".

NameTypeReqDescription
accountstring––
imagestring––
intervalnumber––
interval_typestring––
max_retriesnumber––
namestringyes–
pricenumberyes–
productstringyes–
quantity_recurrencesnumber––
recurrence_periodnumber––
retry_intervalnumber––
statusstring––
trial_daysnumber––
typestring––
unitsnumber––

No output schema declared.

No examples provided.

cakto_offers_get ~196

Leitura de ofertas na Cakto. A oferta é a unidade de PREÇO de um produto (cada produto nasce com uma oferta padrão) e é o alvo de um order bump — um bump aponta para uma OFERTA, nunca para o produto direto. Ações: - list: lista ofertas (filtros: product, status, type, search, ordering, limit, page). - get: detalhe de UMA oferta (requer offer_id). [Flattened action: get] Bulk support: accepts offer_ids for batched execution.

NameTypeReqDescription
accountstring––
limitnumber––
offer_idstring––
offer_idsarray––
orderingstring––
pagenumber––
productstring––
searchstring––
statusstring––
typestring––

No output schema declared.

No examples provided.

cakto_offers_list ~196

Leitura de ofertas na Cakto. A oferta é a unidade de PREÇO de um produto (cada produto nasce com uma oferta padrão) e é o alvo de um order bump — um bump aponta para uma OFERTA, nunca para o produto direto. Ações: - list: lista ofertas (filtros: product, status, type, search, ordering, limit, page). - get: detalhe de UMA oferta (requer offer_id). [Flattened action: list] Bulk support: accepts offer_ids for batched execution.

NameTypeReqDescription
accountstring––
limitnumber––
offer_idstring––
offer_idsarray––
orderingstring––
pagenumber––
productstring––
searchstring––
statusstring––
typestring––

No output schema declared.

No examples provided.

cakto_offers_update ~190

Atualiza uma oferta existente na Cakto (parcial: envie só o que muda). Use status="disabled" para desativar uma oferta sem apagá-la. Requer o escopo "write offers". Bulk support: accepts offer_ids for batched execution.

NameTypeReqDescription
accountstring––
imagestring––
intervalnumber––
interval_typestring––
max_retriesnumber––
namestring––
offer_idstringyes–
offer_idsarray––
pricenumber––
quantity_recurrencesnumber––
recurrence_periodnumber––
retry_intervalnumber––
statusstring––
trial_daysnumber––
typestring––
unitsnumber––

No output schema declared.

No examples provided.

cakto_order_bumps_create ~190

Cria um order bump: pendura uma OFERTA como oferta complementar no checkout de um produto. O produto (product_id) é o checkout onde o bump aparece; a oferta (offer_id) é o que está sendo oferecido — normalmente de OUTRO produto. Use cakto_offers (action=list) para descobrir o offer_id. Requer o escopo "write products". Bulk support: accepts product_ids, offer_ids for batched execution.

NameTypeReqDescription
accountstring––
ctastring––
descriptionstring––
offer_idstringyes–
offer_idsarray––
positionnumber––
product_idstringyes–
product_idsarray––
reference_pricenumber––
show_imageboolean––
titlestring––

No output schema declared.

No examples provided.

cakto_order_bumps_get ~128

Leitura de order bumps (ofertas complementares exibidas no checkout). Ações: - list: lista os order bumps de UM produto (requer product_id). - get: detalhe de UM order bump (requer order_bump_id). [Flattened action: get] Bulk support: accepts product_ids, order_bump_ids for batched execution.

NameTypeReqDescription
accountstring––
order_bump_idstring––
order_bump_idsarray––
product_idstring––
product_idsarray––

No output schema declared.

No examples provided.

cakto_order_bumps_list ~128

Leitura de order bumps (ofertas complementares exibidas no checkout). Ações: - list: lista os order bumps de UM produto (requer product_id). - get: detalhe de UM order bump (requer order_bump_id). [Flattened action: list] Bulk support: accepts product_ids, order_bump_ids for batched execution.

NameTypeReqDescription
accountstring––
order_bump_idstring––
order_bump_idsarray––
product_idstring––
product_idsarray––

No output schema declared.

No examples provided.

cakto_order_bumps_reorder ~116

Reordena os order bumps de um produto numa chamada só: passe a lista completa de {order_bump_id, position}. Posição 1 aparece primeiro. Ids que não pertencem ao produto são ignorados pela Cakto. Requer o escopo "write products". Bulk support: accepts product_ids for batched execution.

NameTypeReqDescription
accountstring––
itemsarrayyes–
product_idstringyes–
product_idsarray––

No output schema declared.

No examples provided.

cakto_order_bumps_update ~162

Atualiza um order bump existente (parcial: envie só o que muda) — troca a oferta, o preço de referência, a copy ou a exibição da imagem. Requer o escopo "write products". Bulk support: accepts order_bump_ids, offer_ids for batched execution.

NameTypeReqDescription
accountstring––
ctastring––
descriptionstring––
offer_idstring––
offer_idsarray––
order_bump_idstringyes–
order_bump_idsarray––
positionnumber––
reference_pricenumber––
show_imageboolean––
titlestring––

No output schema declared.

No examples provided.

cakto_orders_analytics ~147

Analytics de vendas na Cakto: métricas financeiras agregadas por canal/campanha. Agrupe por group_by (utm_source|utm_medium|utm_campaign) e filtre por período (start_date/end_date no formato DD-MM-YYYY neste endpoint). Retorna gross_volume, net_value, total_fees, total_discount e order_count (valores como string, precisão decimal). Vendas sem UTM aparecem como "(unclassified)".

NameTypeReqDescription
accountstring––
end_datestring––
group_bystring––
offerstring––
productstring––
start_datestring––

No output schema declared.

No examples provided.

cakto_orders_get ~225

Leitura de pedidos na Cakto. Ações: - list: lista pedidos (filtros: status csv ex "paid,refunded", type unique|subscription, offer_type main|upsell|downsell|orderbump, payment_method, customer, product, paid_at_gte/paid_at_lt (YYYY-MM-DD), page). - get: detalhe de UM pedido (requer order_id). Retorna os dados crus da Cakto (paginação count/next/previous/results). [Flattened action: get] Bulk support: accepts order_ids for batched execution.

NameTypeReqDescription
accountstring––
customerstring––
offer_typestring––
order_idstring––
order_idsarray––
pagenumber––
paid_at_gtestring––
paid_at_ltstring––
payment_methodstring––
productstring––
statusstring––
typestring––

No output schema declared.

No examples provided.

cakto_orders_list ~225

Leitura de pedidos na Cakto. Ações: - list: lista pedidos (filtros: status csv ex "paid,refunded", type unique|subscription, offer_type main|upsell|downsell|orderbump, payment_method, customer, product, paid_at_gte/paid_at_lt (YYYY-MM-DD), page). - get: detalhe de UM pedido (requer order_id). Retorna os dados crus da Cakto (paginação count/next/previous/results). [Flattened action: list] Bulk support: accepts order_ids for batched execution.

NameTypeReqDescription
accountstring––
customerstring––
offer_typestring––
order_idstring––
order_idsarray––
pagenumber––
paid_at_gtestring––
paid_at_ltstring––
payment_methodstring––
productstring––
statusstring––
typestring––

No output schema declared.

No examples provided.

cakto_products ~145

Lista produtos da conta na Cakto (paginado: count/next/previous/results). Filtros opcionais: search, product_id (um id ou vários separados por vírgula — é assim que se lê UM produto específico), status, type, ordering, limit, page. Bulk support: accepts product_ids for batched execution.

NameTypeReqDescription
accountstring––
limitnumber––
orderingstring––
pagenumber––
product_idstring––
product_idsarray––
searchstring––
statusstring––
typestring––

No output schema declared.

No examples provided.

cakto_products_create ~119

Cria um produto na Cakto. A criação já gera automaticamente a oferta padrão e o checkout do produto (não existe endpoint separado de criar checkout). Requer o escopo "write products" no app do Painel Cakto.

NameTypeReqDescription
accountstring––
categorystring––
descriptionstringyes–
guaranteenumber––
namestringyes–
pricestring––
sales_pagestring––
typestring––

No output schema declared.

No examples provided.

cakto_products_update ~236

Atualiza um produto existente na Cakto. A atualização é PARCIAL: envie só os campos que quer alterar. Use status="blocked" para tirar o produto de circulação sem apagá-lo. Requer o escopo "write products". Bulk support: accepts product_ids for batched execution.

NameTypeReqDescription
accountstring––
affiliateboolean––
affiliate_commissionnumber––
categorystring––
default_payment_methodstring––
descriptionstring––
guaranteenumber––
imagestring––
installmentsnumber––
invoice_descriptionstring––
namestring––
payment_methodsarray––
pricestring––
producer_namestring––
product_idstringyes–
product_idsarray––
sales_pagestring––
statusstring––
support_emailstring––
support_whatsappstring––
typestring––

No output schema declared.

No examples provided.

cakto_subscription_churn ~78

Assinaturas perdidas: lista canceladas/inativas do negócio + métricas agregadas (valor em risco, nº de clientes afetados). Filtros de período opcionais.

NameTypeReqDescription
accountstring––
end_datestring––
pagenumber––
start_datestring––

No output schema declared.

No examples provided.

cakto_subscriptions_get ~162

Leitura de assinaturas na Cakto. Ações: - list: lista assinaturas (filtros: status, payment_method, current_situation new|renewed, search, ordering, limit, page). - get: detalhe de UMA assinatura (requer subscription_id). [Flattened action: get] Bulk support: accepts subscription_ids for batched execution.

NameTypeReqDescription
accountstring––
current_situationstring––
limitnumber––
orderingstring––
pagenumber––
payment_methodstring––
searchstring––
statusstring––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

cakto_subscriptions_list ~162

Leitura de assinaturas na Cakto. Ações: - list: lista assinaturas (filtros: status, payment_method, current_situation new|renewed, search, ordering, limit, page). - get: detalhe de UMA assinatura (requer subscription_id). [Flattened action: list] Bulk support: accepts subscription_ids for batched execution.

NameTypeReqDescription
accountstring––
current_situationstring––
limitnumber––
orderingstring––
pagenumber––
payment_methodstring––
searchstring––
statusstring––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

connect ~42

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

marketplace ~532

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

NameTypeReqDescription
actionstring––
argumentsstring––
cancel_commentstring––
cancel_reasonstring––
conversationstring––
immediateboolean––
limitnumber––
mcp_idstring––
messagestring––
prompt_bodystring––
prompt_categorystring––
prompt_descriptionstring––
prompt_slugstring––
prompt_targetsarray––
prompt_titlestring––
prompt_toolstring––
prompt_varsstring––
querystring––
report_contextstring––
request_detailsstring––
request_namestring––
tier_slugstring––
tool_idstring––

No output schema declared.

No examples provided.

report_bug ~50

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

NameTypeReqDescription
contextstring––
conversationstring––
messagestringyes–

No output schema declared.

No examples provided.

show_version ~17

Show the current MCP platform and adapter versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolkit_info ~37

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Cakto MCP server?

Cakto is an MCP server listed in the public MCP registry as io.github.mcp-dir/cakto-mcp. Read your Cakto sales: orders, revenue analytics, subscriptions, churn, customers and products. This page covers its hosted endpoint (https://api.mcp.ai/p_cakto).

Is the Cakto MCP server safe to use?

Cakto scores 74 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 Cakto MCP server expose?

Cakto exposes 27 tools: cakto_list_accounts, cakto_orders_list, cakto_orders_get, cakto_orders_analytics, cakto_subscriptions_list, and 22 more. Their descriptions and schemas cost roughly 4,022 tokens of context every time the server is loaded.

Does the Cakto MCP server require authentication?

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

Is the Cakto MCP server still maintained?

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