agent-exec

io.sslip.128.221.67.45.agent-execPublished by agent-exec.45.67.221.128.sslip.ioOfficial publisherv0.2.0Updated Oct 25, 2026

Accountless pay-per-use sandbox execution, storage, locks, attestation and handoff; pay via x402.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint offering accountless, pay-per-use sandbox execution, storage, locks, attestation and handoff, paid through x402.

What you can do
Run code in a sandboxed execution environment without creating an account, paying per use through x402 payments. Store and retrieve data in the service's storage. Acquire and manage locks for coordinating work. Obtain attestation and hand off work between sessions or agents. No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
When an assistant needs a disposable sandbox to run code or coordinate work without signing up for an account, and the user is willing to pay per use through x402.
Requirements
A remote streamable HTTP endpoint; no local runtime, packages, environment variables or headers are declared. No authentication is declared, but x402 payments are required for use, so a payment-capable client or wallet is implied.
Before you install
Usage is paid per use through x402, so calls can spend money. The service is accountless and holds stored data and locks, so avoid putting sensitive material in it. Attestation and handoff features are undocumented here; verify what data is sent to the third-party operator before relying on them.

Installation

In SourceWeft

  1. Open agent-exec in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.sslip.128.221.67.45.agent-exec%2Fagent-exec/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-exec": {
      "type": "http",
      "url": "https://agent-exec.45.67.221.128.sslip.io/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.