Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
DLL Execution
Overview
Description from the maker (original English)
Free read-only Base Mainnet transaction Preflight and Verification; no signing or custody.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://execution.dll.io/mcpRun this in your terminal
claude mcp add --transport http dll-execution https://execution.dll.io/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"dll-execution": {
"url": "https://execution.dll.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"dll-execution": {
"type": "http",
"url": "https://execution.dll.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://execution.dll.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dllio, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32680 servers in this category
- Published to the registry more recently than 61% of the other 32680 servers in this category
- Basic checks equal to or better than 100% of the other 32680 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is DLL Execution safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 25 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
EmbeddedCI BenchPod
by embeddedci-com
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
DLL Execution — Base transaction simulation and verification for AI agents
Execution infrastructure for AI agents.
DLL is an independent, read-only Base Mainnet API and remote MCP service. Before signing, simulate an unsigned transaction, inspect call success or revert, and check explicit destination and L2 execution fee constraints. After independent broadcast, verify inclusion, requested receipt status and supported transaction-field expectations. Results include structured Judgment or Verification states, reason codes, evidence and explicit uncertainty; DLL never signs, broadcasts or takes custody.
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.
With complete supported EIP-1559 transaction context, optional fee_estimation returns a separate conditional estimate of L1 data, L2 execution, applicable Operator Fee and Total Network Fee. Missing necessary components keep total unavailable, not zero. The estimate is not realized cost, a future spending guarantee or an automatic PASS.
Agent has an unsigned transaction candidate→ calls DLL Execution Preflight → receives simulation / cost / policy / judgment / evidence → Agent decides what to do next
| Judgment | Meaning within the evaluated evidence |
|---|---|
PASS | Simulation and applicable checks passed, with no material unresolved issue identified. Not permission to execute. |
CAUTION | Execution may be technically possible, but important uncertainty or incomplete evidence remains. |
BLOCK | Deterministic evidence, such as a simulation revert or explicit constraint rejection, indicates not to proceed with this candidate. |
INDETERMINATE | Available evidence cannot support a reliable judgment. Do not treat it as success or a proven transaction failure. |
Ordinary successful Preflight currently returns CAUTION because legacy cost_estimate L1/total remain unavailable. A complete optional network_fee_estimate does not recompute legacy Judgment or the L2-only cost constraint. 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 transaction_hash is required. The default checks Base inclusion; request receipt_status: "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
Benchmark compares observed Base Mainnet transaction costs with historical context. The public path uses SIWX wallet identity and x402 v2 upto USDC: the first three valid analyses per verified wallet are free, then $0.005 per delivered valid analysis. Anonymous nonempty payment quotes do not force free-eligible wallets to pay. A paid N-hash batch quotes a maximum of N × 5000 atomic USDC; actual settlement counts only valid paid items. HTTP 200 can contain unavailable items; inspect completed billing. Historical percentiles are not route recommendations, profitability judgments or future fee guarantees. See the Benchmark guide and bounded SDK client reference.
Start here
Start with HTTP or Remote MCP Quickstart: no DLL account, API key, wallet or private repository access. The JavaScript path uses only Node.js built-ins; the remote MCP path uses your existing MCP client. No npm install or AgentKit SDK is required.
- Remote MCP: two free read-only tools and standard client setup; no wallet or payment.
- Capability selection and FAQ: choose Preflight, Verification or Benchmark and understand their boundaries.
- Quickstart: make your first Preflight or Verification call.
- Agent integration instructions: when to call and how to interpret results.
- Preflight contract: inputs, outputs, constraints and errors.
- Verification contract: inclusion, receipt/content checks, realized costs, observation states and errors.
- Benchmark contract: historical cost context, SIWX, allowance, x402 payment and safe reconciliation.
- Benchmark client reference: stage-aware identity/payment negotiation with independent spending authorization, not a generic-client compatibility guarantee.
- Preflight examples: curl, JavaScript, Python.
- Verification examples: curl, JavaScript, Python.
Public discovery and canonical contract
- API origin: compact capability selector and canonical integration links.
- Machine-readable index: index of authoritative public surfaces, not a duplicate API contract.
- Public sitemap and crawl hints: explicitly advertised public GET documents; not authentication or proof of indexing.
- Live OpenAPI: canonical API schemas and available operations.
- Capabilities: currently available capabilities and their scope.
- x402 discovery manifest: Benchmark paid resource discovery; neither Preflight nor Verification requires x402 payment.
This repository explains what DLL does and how to use it. Live OpenAPI, well-known metadata and actual API responses are the canonical public contract. It is not an implementation/source-code mirror.
Documentation checks run offline with node --test test/*.test.mjs: local links, JSON syntax and bounded client safety behavior. They create no real signatures, payments or blockchain requests. Full examples are additionally checked against canonical product schemas during release validation.
Limitations and security boundary
Base Mainnet only. Preflight accepts unsigned candidates; Verification accepts already-broadcast transaction hashes. No signing, broadcasting, custody or autonomous execution. DLL does not prove ownership of the supplied from address or authorize a transaction.
Simulation describes observed chain state; it does not guarantee future inclusion, success or application-level outcomes. The default L2-only fee is not total execution cost; optional network fee completeness describes only the supported conditional model. An unavailable fee is unknown, not zero. DLL does not verify net asset changes, comprehensively scan malicious contracts or guarantee Swap economic results. Keep private keys, credentials and other secrets out of requests. The Agent remains responsible for any later action.
Verification checks only the supplied expectations. Included, successful and canonical observations are not finalized-state guarantees. Its realized L2 fee is not total cost; total execution cost currently remains unavailable even if an L1 fee is observed.