mcpbeat

CTRL MCP Server

io.github.CTRLabs/ctrl-mcp
not responding

CTRL is listed as active in the registry but did not answer our last check. It exposes 7 tools. Last commit 11 Jun 2026.

Visual DeFi workflow automation on Base + Ethereum mainnet.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
24.2%
Uptime 24h
22 of 91 checks
7
Tools
read from the server
375 ms
Response time
average over 24h
1
Stars
last commit 11 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add ctrl-mcp --transport http https://www.ctrl.build/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ctrl-mcp": {
      "url": "https://www.ctrl.build/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ctrl-mcp]
url = "https://www.ctrl.build/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ctrl-mcp": {
      "url": "https://www.ctrl.build/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ctrl-mcp": {
      "url": "https://www.ctrl.build/api/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ctrl
ctrl_activate
Return an EIP-5792 transactions[] batch the user signs ONCE to deploy their vault + register spending rules. After signing, the keeper runs the workflow autonomously per the on-chain caps.
ctrl_create_workflow
Create a CTRL workflow draft. ONE trigger + an ordered chain of up to 20 actions/conditions/utilities. Returns { workflowId, activateUrl }. Pass `targetChain` to pick which chain the workflow runs on — "base" (default, launchpads + Aerodrome + UniV4) or "ethereum" (UniV3 only, no launchpads, no clanker/zora). CRITICAL: call ctrl_get_block_catalog FIRST (with the same `chain` value) to discover field names — every key in trigger.config and chain[].config must exactly match catalog fields[].key. Populate EVERY field the user expressed intent for. For pool.created (Token Launch, Base-only) set launchpad (e.g. ["bankr"]), keywordIncludes ("ai,agent,claw"), keywordMatchMode "any", keywordCategories (["ai_agents"]), safetyEnabled true, safetyRejectHoneypot true, safetyMinScore 50. For cypher.swap set tokenIn ("ETH"), tokenOut ("{{trigger.tokenAddress}}"), tokenOutMode "dynamic", amount (ETH units, e.g. 0.005 — ASK USER if not specified), slippage (15 for snipes), and autoSell* if user wants an exit (autoSellEnabled true, autoSellMode "multiple", autoSellMultiplier 2, autoSellPercent 100, autoSellReceiveToken "USDC"). For notify.telegram set message with {{token}}/{{amount}}/{{txHash}} placeholders. Interview the user for missing critical fields (amount, exit strategy, keywords) — do not silently default.
ctrl_fire_manual
Manually fire a workflow once. Keeper picks up within ~5s. Use to test a workflow without waiting for its natural trigger.
ctrl_get_block_catalog
Return the live catalog of every CTRL workflow block with id, label, description, and config-field schemas. Call this before ctrl_create_workflow when unsure of a block's config shape. Pass `chain` to filter to blocks that are compatible with the target chain (Base = launchpads + Aerodrome + UniV4; Ethereum = no launchpads, V3 only). Default is "base".
ctrl_get_execution_logs
Read recent workflow executions: trigger, status, BaseScan tx hash, gas, timing. Without workflowId returns the user's most recent across all workflows.
ctrl_get_vault_status
Read the user's CTRL vault address, ETH + WETH balance, and active rules. Call this BEFORE ctrl_activate so you can tell the user how much they need to fund.
ctrl_withdraw
Return an EIP-5792 batch the user signs to withdraw funds from their CTRL vault back to their wallet. The agent never signs. token defaults to ETH; pass WETH or a 0x token address for other assets; omit amount to withdraw the full balance.

Endpoints

URLTransportStateLatencyChecked
https://www.ctrl.build/api/mcp streamable-http answering 94 ms 11 min ago

CTRL — questions

Answers built from our own checks of this server.

What can CTRL do?
It exposes 7 tools, read directly from the server on our last check. Among them: ctrl_activate, ctrl_create_workflow, ctrl_fire_manual, ctrl_get_block_catalog, ctrl_get_execution_logs, ctrl_get_vault_status and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is CTRL working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 22 of 91 checks got a reply (24.2%), average response time 375 ms. The bar chart above shows every period we have measured.
The registry lists CTRL as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect CTRL?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does CTRL need an API key?
No. CTRL completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is CTRL?
It answers our handshake in 375 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is CTRL open source?
Yes — it is published under the MIT licence and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.