Home / MCP registry index / io.github.mcp-dir/cakto-mcp

Cakto

io.github.mcp-dir/cakto-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_cakto. Source: github.com/mcp-dir/cakto-mcp.

The registry describes it as: Read your Cakto sales: orders, revenue analytics, subscriptions, churn, customers and products.

We read its 27 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http cakto-mcp https://api.mcp.ai/p_cakto

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "cakto-mcp": {
      "url": "https://api.mcp.ai/p_cakto"
    }
  }
}

VS Code

code --add-mcp '{"name":"cakto-mcp","type":"http","url":"https://api.mcp.ai/p_cakto"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

cakto_list_accounts cakto_orders_list cakto_orders_get cakto_orders_analytics cakto_subscriptions_list cakto_subscriptions_get cakto_subscription_churn cakto_customers_list cakto_customers_get cakto_products cakto_products_create cakto_products_update cakto_offers_list cakto_offers_get cakto_offers_create cakto_offers_update cakto_order_bumps_list cakto_order_bumps_get cakto_order_bumps_create cakto_order_bumps_update cakto_order_bumps_reorder show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-cakto-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-cakto-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Analytics and SEO MCP servers