The un.charter/1945 slice of Arxo Law as a local MCP server over stdio: the same packages and the same engine as the hosted endpoint, evaluated on your machine. Nothing leaves it.

claude mcp add charter -- npx -y @arxo/mcp-charter

Any MCP client that starts a stdio server works the same way:

{"mcpServers": {"arxo-charter": {"command": "npx", "args": ["-y", "@arxo/mcp-charter"]}}}

Platforms: darwin-arm64, linux-x64. Elsewhere the launcher refuses and names the hosted endpoint, https://mcp.arxo.io/mcp/charter, where requests are evaluated on Arxo infrastructure.

pin.json records what the server answers from: the canon profile and its content hash, the digest of the bundled slice and of the binary per platform, and the commit they were built from. Terms of the pinned texts: NOTICE.