prooftrail

MCP Distribution Contract

This page is the registry-facing contract for the ProofTrail MCP surface. It documents four separate truth lanes: local stdio works now; the ClawHub skill page is live as a public discovery page for the repo-owned skill packet; Goose #26 and agent-skill.co #182 are active upstream review lanes; the OpenHands/extensions lane is closed-not-accepted; and the npm, Official MCP Registry, and GHCR lanes are still unpublished or contract-only upstream.

Use it when you need the shortest truthful summary of:

MCP Package Metadata

Field Value
Name @prooftrail/mcp-server
Registry server name io.github.xiaojiou176-open/prooftrail-mcp
Description Governed MCP access to ProofTrail runs, proof, and workflows
Version 0.1.1
Homepage https://xiaojiou176-open.github.io/prooftrail/
Repository https://github.com/xiaojiou176-open/prooftrail
License MIT
Protocol stdio
Transport stdio
Auth boundary local-with-optional-backend-token

Capability Summary

The MCP surface is a governed browser-evidence bridge for external AI clients.

It is designed for clients that need to:

It is not:

Current / usable today

The current supported path is a local checkout + stdio install.

Use it when you have the repo locally and want your agent shell to call the MCP surface directly from the checkout.

Example configuration:

{
  "mcpServers": {
    "prooftrail": {
      "command": "pnpm",
      "args": ["mcp:start"],
      "cwd": "/absolute/path/to/prooftrail"
    }
  }
}

Optional backend token forwarding example:

{
  "mcpServers": {
    "prooftrail": {
      "command": "pnpm",
      "args": ["mcp:start"],
      "cwd": "/absolute/path/to/prooftrail",
      "env": {
        "UIQ_MCP_API_BASE_URL": "http://127.0.0.1:18080",
        "UIQ_MCP_AUTOMATION_TOKEN": "optional-backend-token"
      }
    }
  }
}

Truth boundary:

Upstream publication split

The following names are the current discovery, review, package, and container surfaces for this repository:

The repo-local registry submission artifact now lives at apps/mcp-server/server.json.

Future package example (not usable today):

{
  "mcpServers": {
    "prooftrail": {
      "command": "npx",
      "args": ["-y", "@prooftrail/mcp-server@0.1.1"]
    }
  }
}

Future container example (not publicly evidenced today):

{
  "mcpServers": {
    "prooftrail": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-v",
        "/absolute/path/to/prooftrail:/workspace",
        "-e",
        "UIQ_MCP_API_BASE_URL=http://host.docker.internal:18080",
        "-e",
        "UIQ_MCP_WORKSPACE_ROOT=/workspace",
        "ghcr.io/xiaojiou176-open/prooftrail-mcp-server:0.1.1"
      ]
    }
  }
}

The package example above still describes an intended publish-facing contract only. It must not be described as a live install path until the npm package is actually published and read back from the upstream registry.

The container example above describes the intended GHCR install shape only. A mounted ProofTrail checkout (or another compatible workspace root) is still assumed, and it is not a standalone hosted MCP endpoint. Today public read-back does not confirm a live GitHub Packages page for this image, so Docker must not be described as a listed/live public lane here. That also means Docker does not upgrade the npm package or Official MCP Registry listing to live.

The live ClawHub page above does not upgrade the npm package, Official MCP Registry, or GHCR lane to live either. It is a separate skill-page lane for the repo-owned packet.

Repo validation command:

pnpm mcp:container:smoke

Supporting docs

This site is open source. Improve this page.