An interoperable WebMCP town — Town Hall publishes a machine-readable provider registry and builds itineraries a general-purpose consumer can follow across independent surfaces.

Say it once, the town does the rest: one request, and the agent chains the whole errand across independent providers, then verifies the journey against the itinerary.

Population 3 · Founded MMXXVI

Follow the build →

In build · MMXXVI

selvage.dev

The transaction boundary for agentic web actions.

Verifies approved terms, revalidates them before execution, and allows or blocks the commit at the provider boundary — each decision leaves an inspectable record of what was approved, attempted, and executed.

WebMCP-first · Cross-model · In-path enforcement · Evidence Receipts

See the teaser →

Open source · npm · Apache-2.0

The WebMCP provider stack

Open-source infrastructure for the provider surface — define and validate structured browser tools, then check any provider against the contract, independent of who built it. Zero-dependency, TypeScript → ESM, built from real multi-provider WebMCP journeys.

@zioladev/provider-tools

Phase 1 · the contract

GitHub ↗ · npm ↗

@zioladev/provider-conformance

Phase 2 · the suite

GitHub ↗ · npm ↗

✓ Provider Tools · ✓ Provider Conformance · Multi-Provider Runtime · Interoperability Conformance · Transaction Governance

Available for selective collaborations

Interesting problems have a way of finding good conversations. hello@ziola.dev