Developer Tools

448c.org

Provides a paid isolated code execution sandbox and persistent object storage with buy, renew, replace, and read operations.

1 endpoint28 known toolsFirst detected September 22, 2026Last detected September 22, 2026

ENDPOINT 1

https://agent-exec.448c.org/mcp

No auth detected

MCP server metadata

Name: agent-exec
Version: 0.1.0

Capabilities

tools.listChanged

Known tools 28

execute

PAID: run code in an isolated, network-less sandbox and get stdout, stderr and exit code back.

Potential side effects

storage_buy

PAID: store opaque bytes for the life of the plan you buy, owned by the wallet that pays, readable with no account.

Inferred read-only

storage_renew

PAID: push an object you own further out, by buying it another plan term.

Inferred read-only

storage_replace

PAID: overwrite the contents of an object you own, keeping its id, and buy it a fresh plan term at the same time.

Inferred read-only

storage_read

FREE: read back an object you own, as base64.

Inferred read-only

storage_list

FREE: list the objects your wallet owns -- id, label, size, when each was created and when it expires -- one page at a time.

Inferred read-only

storage_usage

FREE: how many objects your wallet is storing and how many bytes they occupy.

Inferred read-only

storage_delete

FREE: delete an object you own before it expires, and free its bytes.

Potential side effects

claim_acquire

PAID: atomically win a caller-named key for your own fleet -- an accountless compare-and-set.

Inferred read-only

claim_renew

PAID: extend a hold you already have without losing your place in line -- the heartbeat that lets a lease be SHORT (so a crash frees it fast) while a live holder keeps it alive by paying again.

Inferred read-only

claim_acquire_free

FREE: win a caller-named key for 300 seconds, or learn who already holds it.

Inferred read-only

claim_read

FREE: who currently holds this key, if anyone -- scoped to YOUR wallet, so a stranger cannot probe your namespace.

Inferred read-only

claim_release

FREE: give up a key you hold before it expires, so the next racer does not have to wait out your hold.

Inferred read-only

attest_create

PAID: we fetch a URL from OUR vantage point and return a signed, timestamped attestation of what we saw -- hash, byte count, HTTP status and headers, never the body itself.

Inferred read-only

attest_read

FREE and unauthenticated: read a previously-created attestation back by id, with its signature.

Inferred read-only

handoff_deposit

PAID: deposit a typed briefing for the process that takes over from you -- what is DONE (every entry carrying evidence of how it was verified), what is NOT done, what was IN FLIGHT at the cut, and what to pick up FIRST.

Inferred read-only

handoff_read

FREE and unauthenticated: read a briefing back by id.

Inferred read-only

deadman_register

PAID: register an intent you are about to act on irreversibly, with a lease and a verification probe (a GET plus a predicate).

Inferred read-only

deadman_confirm

FREE: the live caller closes the loop before the lease expires, so the probe never runs.

Inferred read-only

deadman_read

FREE and unauthenticated: read an entry back by id, including its verdict and the raw probe response once resolved.

Inferred read-only

listing_promote

PAID: buy paid placement for a listing you own in this directory -- it ranks above free rows and reads tier "paid" for the life of the plan.

Inferred read-only

drift_check

PAID: we re-fetch a venue we have snapshotted before, from OUR vantage point, and return what changed since the baseline -- the schema/rubric fields that moved, were added and were removed, not a byte diff.

Inferred read-only

drift_venues

FREE: every venue id drift_check can be aimed at, with what we hold for each.

Inferred read-only

drift_baseline

FREE: the baseline snapshot we hold for one venue -- what a paid check would diff against, and when it was taken.

Inferred read-only

watch_register

PAID: we poll a URL from OUR vantage point on your interval until your predicate matches or the ttl runs out, and keep the verdict for you to collect -- a wait that survives your own process dying, which is what an agent cannot do for itself.

Inferred read-only

watch_read

FREE: the current state of a watch you registered -- active, matched or expired, with the observation that matched.

Inferred read-only

service_card

What agent-exec sells, what it costs, and exactly where to pay for it.

Potential side effects

search_listings

Free, unauthenticated search over agent-exec's directory of paid agent-facing services (same data as GET https://agent-exec.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agent-exec]
url = "https://agent-exec.448c.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "agent-exec": {
      "type": "http",
      "url": "https://agent-exec.448c.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: agent-exec
Remote MCP URL: https://agent-exec.448c.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agent-exec": {
      "url": "https://agent-exec.448c.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "agent-exec": {
      "type": "http",
      "url": "https://agent-exec.448c.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "agent-exec",
  "transport": "streamable-http",
  "url": "https://agent-exec.448c.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.