Skip to content
External endpointresponds

CTRL

Visual DeFi workflow automation on Base + Ethereum mainnet.

Endpoint URL
https://www.ctrl.build/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
334 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.CTRLabs/ctrl-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
@daxaur/ctrl-mcp
Version
0.2.0-hosted
Capability keys
tools
Tool names
ctrl_get_vault_status, ctrl_get_block_catalog, ctrl_create_workflow, ctrl_activate, ctrl_withdraw, ctrl_fire_manual, ctrl_get_execution_logs
Instructions excerpt

CTRL is a workflow automation system on Base mainnet. Workflows run inside a non-custodial V3 vault (verified on Basescan) that enforces the on-chain maxPerSwap and maxPerDay caps the user signs once. The keeper polls every ~5s. Built-in safety primitives include the pool.created safetyEnabled flag (GoPlus honeypot + tax + score gate) and pauseVault/revokeRule kill-switches. Call ctrl_get_block_catalog to read the live list of available blocks before assembling a workflow. Two equivalent surfaces exist: this JSON-RPC MCP server (tool execution needs an sk_ctrl_ key) and the anonymous REST API at /api/mcp/* (no key — the wallet signature at activate-time is the trust boundary). The REST surface is canonical for wallet-native agents; this MCP server is for key-based clients like Cursor and Claude Desktop. Both drive the same workflows.

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 400ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 1,360ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 181ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 334ms
Back to MCP directory