actpkg.dev · part of ACT

The hardened tool registry for AI agents.

Sandboxed, signed, capability-declared WebAssembly. One .wasm runs from your CLI, your agent, your app, or your browser.

Browse components Install the CLI →

$act pull <owner>/<name>
$act run <name> --mcp     # serve to Claude / Cursor / any MCP client
$act call <name> echo --args '{"text":"hi"}'

Capability-sandboxed

Every component declares the host capabilities it needs — filesystem mounts, network reach, clocks — in WIT. The runtime refuses anything undeclared. No ambient authority.

Signed & auditable

Reproducible builds, SBOM in the artifact, cryptographic signatures on every version. Auditors get a structured log of every call an agent made and why.

One artifact, every host

The same .wasm serves agents over MCP, applications over HTTP, humans over CLI, and browsers via JSPI. Build once. Trust once. Run anywhere.

How it works

Three commands from registry to running tool.

Pull

act pull actpkg.dev/acme/sqlite

OCI-native. docker pull works too — the registry speaks the Distribution Spec.

Inspect

act info sqlite --tools

See the tools, schemas, and the exact capability grants the component will ask for.

Run

act run sqlite --mcp \
  --profile sqlite

Boot it as an MCP server, an HTTP service, or call one tool and exit. Same artifact.

Coming soon

Try any component in your browser.

A WebLLM-powered playground will load components straight from the registry — via jco and the new JSPI engine in Chromium — so you can probe tools before you install them.

await act.load(
  "actpkg.dev/acme/sqlite:0.3.0",
);
// runs in the tab, sandboxed.

Ship tools your agents can’t escape.

Browse components Read the spec