DLL Execution MCP server
online · 100% uptimeio.github.dllio/dll-execution·v0.1.0Free read-only Base Mainnet transaction Preflight and Verification; no signing or custody.
0 stars
Reviews
Write oneNobody has reviewed DLL Execution yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
DLL Execution tools (2)
write = sends, deletes, buys or postspreflight_transactionFreeBefore execution: assess one unsigned Base candidate. Free, no wallet/payment. CAUTION commonly means total cost is incomplete; simulation is not authorization or guaranteed success.
verify_transactionFreeAfter broadcast: verify observed Base transaction against explicit expectations. Default checks inclusion, NOT receipt success. VERIFIED is not finality, ownership or causality. Free; not-found/provider uncertainty is not success.
Public scan report
scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 406ms20/20
- Tool poisoning2 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How DLL Execution compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 288 ms
- faster than 49% of 30,031 servers
What its tools let an agent do: 2 read
Install DLL Execution in Claude Code, Cursor or VS Code
claude mcp add --transport http dll-execution https://execution.dll.io/mcp
What the publisher says
From the DLL Execution repository's README, as published. We do not edit it. Read it on GitHub
DLL Execution
Execution infrastructure for AI agents.
DLL helps AI Agents make better decisions before onchain execution and inspect observed outcomes afterward, with evidence intended to reduce downstream friction, execution cost and avoidable failures.
Any Agent that wants to get something done onchain can call DLL.
This is the north star, not a claim of universal chain support or autonomous execution today.
Who it is for
AI Agents with an unsigned transaction candidate or an already-broadcast transaction hash, and developers integrating those Agents. Before acting, an Agent needs to understand likely failure, known costs, explicit constraints and remaining uncertainty. Afterward, it needs to check observed outcomes against explicit expectations.
Available now: Execution Preflight
POST https://execution.dll.io/v2/execution/preflight
V0.2.1 evaluates one unsigned Base Mainnet transaction candidate and returns read-only simulation, an estimated L2 execution fee, deterministic policy checks, structured judgment and supporting evidence. It is a limited free public trial; no wallet connection, signature or payment is needed for Preflight. Benchmark's separate payment/free-trial rules do not apply to this endpoint.
Agent has an unsigned transaction candidate
→ calls DLL Execution Preflight
→ receives simulation / cost / policy / judgment / evidence
→ Agent decides what to do nextOrdinary successful Preflight currently returns CAUTION: L1 data fee and total transaction cost are unavailable. None of these states evaluates profitability, investment quality, strategic desirability or financial advice.
Available now: Execution Verification
POST https://execution.dll.io/v2/execution/verify
Verification V0.1 observes an already-broadcast Base Mainnet transaction and evaluates narrow expectations about its chain, inclusion, receipt status and optional candidate content. It is free and read-only: no signature, wallet connection or payment is required, and DLL need not have performed the original Preflight.
- Preflight — before execution: evaluate what is likely to happen, within the recorded evidence.
- Verification — after execution: observe what actually happened and evaluate it against explicit expectations.
Only transactionhash is required. The default checks Base inclusion; request receiptstatus: "success" explicitly to check receipt success. Read verification.state, not just HTTP status: VERIFIED means the requested checks are satisfied, CONTRADICTED means at least one check is contradicted, and INDETERMINATE means evidence is insufficient. These states do not establish finality, authorization, ownership, causality or profitability.
Available now: Execution-cost Benchmark
POST https://execution.dll.io/v1/benchmark/transactions
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
DLL Execution: common questions
- Is DLL Execution MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the DLL Execution safety report
- How do I install DLL Execution?
- It runs remotely at execution.dll.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does DLL Execution need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is DLL Execution maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v0.1.0.
- Is DLL Execution up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does DLL Execution compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.