Proof Layer

io.github.World-999-LabsPublished by GitHub account World-999-Labsv1.0.1Updated Oct 25, 2026

Signed, hash-chained provenance receipts for AI agent actions.

The publisher's own server: Proof Holdings

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Local MCP server that issues signed, hash-chained governance receipts for AI agent actions, returning a verdict before the agent acts.

What you can do
Request pre-execution verdicts on proposed agent actions, such as EXECUTE, BLOCK, REVIEW or SHADOW, from the Proof Layer service before the action runs. Receive Ed25519-signed, hash-chained receipts that record each evaluated action in an audit trail. Verify receipt bundles offline with the published public key, without calling the API. Legacy vd_ tool names and VERIDOCS environment variables are still accepted alongside the pl_ names.
When to use it
Use it when an agent takes consequential actions, such as sending messages, merging code or moving money, and you want a signed record and a verdict before each action rather than after-the-fact logs. It suits teams that need an auditable, offline-verifiable trail of what an agent was permitted to do.
Requirements
Runs locally as an npm package via npx, so Node.js is needed, and it is intended for desktop MCP hosts. Requires a Proof Layer API key in PROOF_LAYER_API_KEY, obtained from the provider's dashboard, and network access to the Proof Layer API; PROOF_LAYER_API_URL can override the default endpoint.
Before you install
The API key in PROOF_LAYER_API_KEY is a secret sent to the provider's service, and proposed actions are evaluated by that remote closed-source kernel, so action details leave your machine. Anonymous usage telemetry is on by default and must be disabled with PROOF_LAYER_TELEMETRY set to off. Verdicts are advisory governance signals, not enforcement; the agent or host must honor them.

Installation

In SourceWeft

  1. Open Proof Layer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Proof Layer

[@proof-layer/mcp] [@proof-layer/verify] [License: MIT] [MCP compatible] [Live deployment]

Cryptographic governance receipts for AI agents. Issued before the agent acts. Ed25519-signed. Hash-chained. Verifiable offline.

Built by WORLD999_LABS. Published on npm under @proof-layer/*. The legacy @veridocs/* package names continue to resolve and forward to the new ones.


What this repo contains

This is the public half of Proof Layer — the parts you install and run on your own machine:

PackageWhat it doesnpm
@proof-layer/mcpMCP server for Claude Desktop, Cursor, Cline, and any MCP-aware host[npm]
@proof-layer/verifyStandalone offline verifier — zero dependencies, audits any receipt bundle with just our public key[npm]

The kernel (governance engine, Gauntlet adversary/judge pipeline, billing, dashboard) is closed-source and runs at prooflayer.world999labs.com. Open-source clients + closed-source server is the same pattern Stripe, Resend, and Vercel use — you get full transparency on what runs locally and what data leaves your machine, while the proprietary server logic stays protected.


Quick start

bash
npx -y @proof-layer/mcp@latest

Drop into Claude Desktop's claude_desktop_config.json:

json
{  "mcpServers": {    "proof-layer": {      "command": "npx",      "args": ["-y", "@proof-layer/mcp@latest"],      "env": {        "PROOF_LAYER_API_KEY": "pl_live_...",        "PROOF_LAYER_API_URL": "https://prooflayer.world999labs.com"      }    }  }}

Restart Claude. Eight pl_* tools appear in the picker. Get an API key at prooflayer.world999labs.com.

Migrating from @veridocs/mcp? No code changes required. The legacy package name continues to resolve, the legacy vd_* tool names continue to work alongside pl_*, and existing VERIDOCS_API_KEY / VERIDOCS_API_URL environment variables are still accepted. You can switch the package name and env-var names on your own schedule.


Why pre-execution governance?

Most "AI safety" tools run after the model has acted — toxicity filters, output classifiers, post-hoc audit logs. By the time the alarm fires, the agent has already sent the email, merged the PR, or executed the trade.

Proof Layer flips this:

  1. Agent proposes an action (e.g. "send wire transfer for $50,000")
  2. Proof Layer evaluates → returns signed verdict: EXECUTE / BLOCK / REVIEW / SHADOW
  3. Receipt is written to a hash-chained, Ed25519-signed audit trail
  4. Anyone with our public key can verify the entire chain offline — no trust in our infra required

A broken hash chain = tampering, immediately visible. A missing receipt = the agent acted without permission.


Verifying receipts offline

Receipts are designed to outlive us. Here's how to verify a bundle without ever calling our API:

typescript
import { verifyBundle } from "@proof-layer/verify";import fs from "fs";
const bundle = fs.readFileSync("./receipts.ndjson", "utf8");const publicKey = fs.readFileSync("./prooflayer-public-key.pem", "utf8");
const result = verifyBundle(bundle, publicKey);console.log(result);// { pass: 147, fail: 0, total: 147, chainBroken: false }

Public key is published at prooflayer.world999labs.com/v1/public-key and rotates on a published schedule.


Resources


License

MIT — see LICENSE.

The kernel and dashboard are proprietary and not included in this repo. The MCP server, verifier, and all client SDKs published under @proof-layer/* (and the legacy @veridocs/* names) are MIT-licensed.


Contributing

Pull requests, issues, and feedback welcome. See CONTRIBUTING.md.

Source: README.md at commit 68edc25

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Proof integrations