telleroutlook/agentkit-js/mcp-server

> **WasmAgent adds a verifiable evidence layer to agent tool use: protect tool calls, record what happened, audit the result, and admit trusted traces into downstream systems.**
**Protect → Record → Audit → Admit** · **Sync** — agent↔UI shared state
---
Start in 30 seconds
Pick your entry point:
| Goal | Install |
|---|---|
| **Protect tools** — runtime firewall, policy enforcement, taint tracking with a provenance-preserving information-flow gate wired through the agent runtime | npm add @wasmagent/mcp-firewall |
| **Record evidence** — signed AEP records after every agent run | npm add @wasmagent/aep |
| **Admit from traces** — compliance scoring produces ComplianceEvalRecords for downstream training | npm add @wasmagent/aep @wasmagent/compliance |
| **Sync state** — reducer-backed agent↔UI shared state, agent reads projections + writes intent | npm add @wasmagent/core (/shared-state subpath) |
**Trust Pack — 30-minute end-to-end: docs/quickstarts/trust-pack-30min.md**
---
Quickstart
Three paths — pick the one that fits your use case:
Path 1 — Protect: MCP runtime firewall
Wrap any MCP server: vet tools before execution, enforce policy per call, track taint across results.
→ Security pack · OWASP Agentic Top 10 · Attack demos
Path 2 — Record: AEP evidence export
Emit a signed evidence record after every agent run — consumable by trace-pipeline for audit and training.
→ AEP schema · trace-pipeline 10-min tutorial
Path 3 — Execute: Sandboxed code execution
Run agent-generated code in an isolated WASM kernel — no host-process access.
→ Kernel comparison · Getting started
Path 4 — Sync: Human-agent shared state
Reducer-backed collaborative state where the LLM reads projections, dispatches semantic actions, and respects affordances — all through standard tools.
The semantic action stream doubles as AEP evidence — every dispatch is a provenance-ready record (see #141 for the full confluence design).
---
📚 **Docs** · Getting started · Kernels · OWASP governance · Security pack · Changelog
---
What is shipped vs alpha
WasmAgent uses a five-tier maturity scale to prevent "shipped" from becoming a vague claim:
| Tier | Meaning | Semver guarantee | Production use |
|---|---|---|---|
| **stable** | Public API locked; breaking changes require major-version bump | Yes | Yes |
| **beta** | Functional and used in production, but a specific limitation is documented (e.g. first-line filter only, contract still evolving) | Minor/patch only | Yes, with caveats documented |
| **alpha** | Schema versioned; fields may be added without a breaking-change bump | No | Informed use |
| **demo** | Demonstration or example code; not hardened for production | No | No |
| **research** | Research-grade prototype; interfaces may change without notice | No | No |
Packages not listed here (model adapters, UI cards, etc.) follow the same scale — see each package's README or package.json wasmagent.stability field.
---
Package maturity
| Package | Maturity | Notes |
|---|---|---|
| @wasmagent/core | **stable** | Public API; semver guaranteed |
| @wasmagent/kernel-quickjs | **stable** | |
| @wasmagent/kernel-remote | **stable** | |
| @wasmagent/mcp-gateway | **stable** | Published 0.1.0; gateway composes all firewall layers |
| @wasmagent/mcp-firewall | **beta** | First-line filter, not adversarial-grade — keyword bag + lightweight n-gram classifier; use defence-in-depth |
| @wasmagent/aep | **beta** | v0.2 signature contract (Ed25519) shipped; schema versioned |
| @wasmagent/otel-exporter | **alpha** | GENAI_SEMCONV, AEP↔OTel bridge |
| @wasmagent/aisdk / @wasmagent/mastra-sandbox | **alpha** | API stable, may add fields |