# Microtoll Engine

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/microtoll/engine  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/microtoll-engine

## Description
Microtoll Engine in your coding tool: docs search and a scaffold for end-to-end-encrypted apps.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "microtoll-engine": {
    "command": "npx",
    "args": ["-y","microtoll-engine"]
  }
}
```

## Documentation & README

# Microtoll Engine

The security layer of an end-to-end-encrypted app, as packages that give any
app the four things AI-generated apps get wrong: sign-in, key handling, access
control and revocation. The server stores only what it cannot read.

**Status:** 0.1.0, the first release (2026-09-27). Pre-1.0: function names
and options may change between minor versions; the bytes it writes never
will. See `docs/pages/formats-and-stability.md` and `DECISIONS.md`.

| Package | Milestone | Licence | What it does |
|---|---|---|---|
| `@microtoll/crypto-core` | M1 | Apache-2.0 | primitives, labelled key derivation, versioned wire formats, hybrid post-quantum seal |
| `@microtoll/identity` | M2 | Apache-2.0 | root key, unlock methods, sessions, restore, deletion |
| `@microtoll/access` | M3 | Apache-2.0 | sealed sharing, capabilities, links, removal and rotation, two-tier disclosure |
| `@microtoll/blind-store` | M4 | AGPL-3.0-only | the reference server library and its Postgres schema |
| `@microtoll/mailbox` | M3b (in M5) | Apache-2.0 | pairwise unlinkable delivery: direct invitations under labels only two people can compute |
| `@microtoll/mcp` | M5 | Apache-2.0 | docs search and project scaffolding for AI coding agents (Model Context Protocol) |

Each package carries its own `LICENSE`. Documentation is CC-BY-4.0.

## Documents

- `microtoll-build-plan.md` — the plan and the non-negotiables.
- `DECISIONS.md` — the founder's decisions.
- `THREATMODEL.md` — per-package threat models and honest limits.
- `docs/` — the source of microtoll.dev, `llms.txt` and the MCP snapshot
  (`npm run docs`); `docs/DESIGN-M5.md`, `docs/DESIGN-M6-pqc-scan.md` and
  `docs/LAUNCH.md`.
- Each package's `FORMATS.md` or `DESIGN.md` — its formats, byte for byte.
- `SECURITY.md`, `CONTRIBUTING.md` — how to report a weakness; the rules and
  the sign-off.

## Examples and deployment

- `examples/notes-app` — end-to-end-encrypted notes with sharing and
  revocation on the reference server: `docker compose up`, then
  <http://localhost:8088>.
- `examples/identity-demo` — the identity package on a page against its
  in-process server stand-in.
- `deploy/` — the hardened Compose file, the Dockerfile and the Nginx sample
  for `blind-store`.

## How it was built, and support

The engine was written with Claude Code (Anthropic's coding agent) from a
security design the founder wrote and decided, milestone by milestone; the
founder read and accepted every change, and every decision with its reasons
is in `DECISIONS.md`. The checks are the ones you can run: the published
test vectors (RFC 5869, RFC 8032, RFC 5903, RFC 7914, NIST CAVP, the X-Wing
draft) through the public API, the frozen fixtures, the adversarial suite,
and the threat model written down in `THREATMODEL.md`. An outside security
audit is the next step, and the NGI/Restack route to fund it is in the plan.

The packages are free and stay free. If they save you work, you can
[sponsor the work on GitHub](https://github.com/sponsors/sealwright).

## Working on it

```
npm install          # TypeScript for the declaration check; ws and pg for blind-store
npm run check        # typecheck + tests (Node >= 24)
npm run db:up        # a throwaway Postgres 17 in Docker for the database-backed suites
```

Tests use Node's built-in `node:test`. The browser packages have no runtime
dependencies; `blind-store` has exactly `ws` and `pg`. The suites that need
a database (blind-store's schema, protocol, live and fixture checks, and the
notes example) run when `npm run db:up` has started one — or a Postgres
answers at `BLIND_STORE_TEST_DB` — and skip with one line otherwise; CI runs
them.