Developer Tools

ctrl.build

This MCP server enables managing CTRL smart wallets, including checking balances, viewing workflow blocks, creating and activating workflows, and withdrawing funds.

1 endpoint7 known toolsFirst detected June 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://www.ctrl.build/api/mcp

No auth detected

MCP server metadata

Name: @daxaur/ctrl-mcp
Version: 0.2.0-hosted

Capabilities

tools

Server instructions

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.

Known tools 7

ctrl_get_vault_status

Read the user's CTRL vault address, ETH + WETH balance, and active rules.

Inferred read-only

ctrl_get_block_catalog

Return the live catalog of every CTRL workflow block with id, label, description, and config-field schemas.

Inferred read-only

ctrl_create_workflow

Create a CTRL workflow draft.

Potential side effects

ctrl_activate

Return an EIP-5792 transactions[] batch the user signs ONCE to deploy their vault + register spending rules.

Inferred read-only

ctrl_withdraw

Return an EIP-5792 batch the user signs to withdraw funds from their CTRL vault back to their wallet.

Inferred read-only

ctrl_fire_manual

Manually fire a workflow once.

Inferred read-only

ctrl_get_execution_logs

Read recent workflow executions: trigger, status, BaseScan tx hash, gas, timing.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.daxaur-ctrl-mcp]
url = "https://www.ctrl.build/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "daxaur-ctrl-mcp": {
      "type": "http",
      "url": "https://www.ctrl.build/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: daxaur-ctrl-mcp
Remote MCP URL: https://www.ctrl.build/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "daxaur-ctrl-mcp": {
      "url": "https://www.ctrl.build/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "daxaur-ctrl-mcp": {
      "type": "http",
      "url": "https://www.ctrl.build/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "daxaur-ctrl-mcp",
  "transport": "streamable-http",
  "url": "https://www.ctrl.build/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for ctrl.build was fetched 2026-07-26T02:13:59.426Z and is being refreshed.

Trust status Trusted

ctrl.build is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.