Registry Simulated 3 MCP tools

Registry Engine

Private npm registry simulation and publish flow.

How you use it

Use the private registry path for AGS packages. registry_enforce after publish; never share org tokens outside the host.

Token savings

Prevents “works on my machine / wrong tarball” install loops that burn sessions on auth and version mismatch.

Consistency

Publish auth, packing, and indexing follow one governed path.

In action

Registry

Pack

Tarball produced for @scope/pkg.

Auth

Publish

Enforce

Interactive demo

Publish flow Idle

registry.ags.local — awaiting token

Publishing: @ags/governance-engine@2.4.1-rc

Simulated behavior only — does not execute proprietary AGS engine code.

Diagram

Example usage

# MCP: registry_enforce
{}

# Publish flow (conceptual)
npm pack → auth → publish → registry_enforce