CTRL
REMOTE · WWW.CTRL.BUILD
Visual DeFi workflow automation on Base + Ethereum mainnet.
Available components
Last scanned (8 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://www.ctrl.build/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.ctrl.build | CN=YR1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | 6115a8301ffeddac3a5bd9689df7ff85935 |
| SANs: www.ctrl.build | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.ctrl.build. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| build. | present | 30770, 38839 | 8, 8 | Verified |
| ctrl.build. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 402 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ctrl.build/api/mcp | HTTP error | 402 | |
| http (plaintext) | http://www.ctrl.build/api/mcp | HTTPS enforced | 308 | https://www.ctrl.build/api/mcp |
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 →
ctrl_activate ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depositEth | string | – | – |
| expiryDays | number | – | – |
| maxPerDayEth | string | – | – |
| maxPerSwapEth | string | – | – |
| workflowId | string | yes | – |
No output schema declared.
No examples provided.
ctrl_create_workflow ~413
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | array | yes | – |
| description | string | – | – |
| name | string | yes | – |
| targetChain | string | – | Chain to run the workflow on. Default: "base". "ethereum" disables launchpad-only blocks (pool.created/clanker/zora/bankr/flaunch) and UniV4/Aerodrome routing. |
| trigger | object | yes | – |
No output schema declared.
No examples provided.
ctrl_fire_manual ~44
Manually fire a workflow once. Keeper picks up within ~5s. Use to test a workflow without waiting for its natural trigger.
| Name | Type | Req | Description |
|---|---|---|---|
| workflowId | string | yes | – |
No output schema declared.
No examples provided.
ctrl_get_block_catalog ~129
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".
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional. Filter to a single block bucket. |
| chain | string | – | Optional. Filter the catalog to blocks compatible with this chain. Default: "base". |
No output schema declared.
No examples provided.
ctrl_get_execution_logs ~55
Read recent workflow executions: trigger, status, BaseScan tx hash, gas, timing. Without workflowId returns the user's most recent across all workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| workflowId | string | – | – |
No output schema declared.
No examples provided.
ctrl_get_vault_status ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ctrl_withdraw ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | Decimal amount, e.g. '0.05'. Omit for full balance. |
| token | string | – | 'ETH' (default), 'WETH', or a 0x token address. |
| wallet | string | yes | Vault owner address (0x…). |
No output schema declared.
No examples provided.
How do I install the CTRL MCP server?
CTRL is a hosted endpoint at https://www.ctrl.build/api/mcp, 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 · www.ctrl.build
claude mcp add --transport http ctrlabs-ctrl-mcp 'https://www.ctrl.build/api/mcp'
What is the CTRL MCP server?
CTRL is an MCP server listed in the public MCP registry as io.github.CTRLabs/ctrl-mcp. Visual DeFi workflow automation on Base + Ethereum mainnet. This page covers its hosted endpoint (https://www.ctrl.build/api/mcp).
Is the CTRL MCP server safe to use?
CTRL scores 25 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 CTRL MCP server expose?
CTRL exposes 7 tools: ctrl_get_vault_status, ctrl_get_block_catalog, ctrl_create_workflow, ctrl_activate, ctrl_withdraw, and 2 more. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.
Does the CTRL MCP server require authentication?
Its publisher declares no required credentials for CTRL. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the CTRL MCP server still maintained?
CTRL is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.