Skip to content

DLL Execution

by dllio · remote · no sign-in to list tools · v0.1.0 · published by GitHub user dllio

Free read-only Base Mainnet transaction Preflight and Verification; no signing or custody.

Final · 2
CompareRegistry entry

2 tools: 2 do something that can't be undone.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http dll-execution https://execution.dll.io/mcp

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • Warnpreflight_transaction

    The server marks "preflight_transaction" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.candidate.to): what it sends cannot be taken back.

    What this check looks for
  • Warnverify_transaction

    The server marks "verify_transaction" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.expectation.candidate.to): what it sends cannot be taken back.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Can't be undone 2Claude Code: ask
  • preflight_transactionBefore signing: simulate one unsigned Base Mainnet (8453) candidate (chain_id/from/to/value/data); inspect call success/revert, top-level destination and L2 fee constraints, Judgme…1 finding

    Why it is in this group

    • The input addresses people (input.candidate.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "preflight_transaction" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.candidate.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Before signing: simulate one unsigned Base Mainnet (8453) candidate (chain_id/from/to/value/data); inspect call success/revert, top-level destination and L2 fee constraints, Judgment, reason codes and evidence. Free; no API key, wallet or payment. Complete supported EIP-1559 fee_estimation context optionally estimates L1/L2/applicable Operator/Total Network Fee separately; legacy Judgment is unchanged, not automatic PASS. Inspect http_status, response.judgment and response.simulation. After broadcast use verify_transaction. No signing, broadcasting, custody, asset-delta/risk scan or execution guarantee.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • verify_transactionAfter independent broadcast: verify a Base Mainnet (8453) transaction against explicit inclusion, receipt-status and optional candidate-field expectations.1 finding

    Why it is in this group

    • The input addresses people (input.expectation.candidate.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "verify_transaction" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.expectation.candidate.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    After independent broadcast: verify a Base Mainnet (8453) transaction against explicit inclusion, receipt-status and optional candidate-field expectations. transaction_hash is required; default checks inclusion, NOT receipt success. Free; no API key, wallet or payment. Read http_status, response.verification.state and response.observation_errors; missing evidence is not success. Before signing use preflight_transaction. VERIFIED is not finality, ownership, causality, asset-balance change verification or a swap economic-outcome guarantee. No signing, broadcasting or custody.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dll-execution https://execution.dll.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__dll-execution__preflight_transaction",
      "mcp__dll-execution__verify_transaction"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as dll-execution. Review it before you use it.