# OpenWorkProof MCP server

> Enables AI agents to provide verifiable work records, review signed evidence, and perform guarded text-editing tasks.

- Repository: https://github.com/dengyier/OpenWorkProof
- Page: https://hostedmcp.org/servers/dengyier/openworkproof
- Transport: stdio
- Stars: 261
- License: Apache-2.0
- Latest version: 1.6.2-credits.1

## Install

### Claude Code

```sh
claude mcp add openworkproof -- uvx openworkproof
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "openworkproof": {
      "command": "uvx",
      "args": [
        "openworkproof"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "openworkproof": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "openworkproof"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"openworkproof","type":"stdio","command":"uvx","args":["openworkproof"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "openworkproof": {
      "command": "uvx",
      "args": [
        "openworkproof"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add openworkproof -- uvx openworkproof
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.openworkproof]
command = "uvx"
args = ["openworkproof"]
```

### Gemini CLI

```sh
gemini mcp add -s user openworkproof uvx -- openworkproof
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "openworkproof": {
      "command": "uvx",
      "args": [
        "openworkproof"
      ]
    }
  }
}
```

## Tools (32)

- `owp_soc_sample_alerts`: Return synthetic Slips JSONL and scope for the reference SOC workflow. No host scanning, external connections or real remediation is performed. This does not activate Guard or protect other MCP tool calls. (read-only)
- `owp_soc_analyze_slips`: Review supplied Slips JSONL locally and return cases plus a signed evidence bundle. Accepts up to 128 KiB, 500 lines and 50 source windows. Uses a synthetic-trained model, a deterministic investigation stub and in-memory simulated actions. Does not control real hosts, push to AiSOC or upload telemetry. Returned keys and checkpoints are self-supplied evidence, not an independent trust anchor. (read-only)
- `owp_soc_verify_bundle`: Verify a reference SOC bundle using separately acquired expected trust pins. Inputs are JSON strings, each at most 8 MiB. Omitted external keys or checkpoint pins yield UNKNOWN, not trusted acceptance. Copying pins from the same bundle only tests consistency; caller-supplied pins do not prove organizational independence. A FAILED/UNKNOWN status is not acceptance. No filesystem writes. (read-only)
- `owp_generate_keypair`: Generate an Ed25519 signing key pair; this tool takes no input parameters. Returns the private key as a hex string and the public key as base64url, along with the derived ``key_id``.
- `owp_compute_key_id`: Compute the OpenWorkProof ``key_id`` for a given Ed25519 public key. Args: public_key_b64url: The raw public key bytes encoded as unpadded base64url (43 characters).
- `owp_sign_payload`: Sign a canonical OpenWorkProof payload with an Ed25519 private key. Args: object_type: One of the allowed signed domains (call ``owp_list_domains`` to see the list). payload: JSON string of the unsigned payload object. private_key_hex: The Ed25519 private key as a hex string. Returns: The signed payload dict with ``signature_alg``, ``signer_key_id``, ``digest``, and ``signature`` fields added.
- `owp_verify_signature`: Verify an Ed25519 signature on a signed OpenWorkProof payload. Args: object_type: The canonical domain of the object. signed_payload: JSON string of the signed payload (must contain ``signature_alg``, ``signer_key_id``, ``digest``, and ``signature``). public_key_b64url: The signer's public key as base64url. Returns: ``{"valid": true}`` if the signature is valid, ``{"valid": false}`` otherwise.
- `owp_compute_digest`: Compute the canonical SHA-256 digest of an OpenWorkProof payload. The digest is computed over the RFC 8785 JCS canonicalisation of ``{"domain": "openworkproof/<object_type>/v0.1", "payload": <payload>}`` (with ``digest`` and ``signature`` fields stripped from the payload at the top level). Args: object_type: One of the allowed canonical domains. payload: JSON string of the payload object.
- `owp_verify_work_order`: Verify a WorkOrder's identity bindings and maintainer signature. Args: work_order_json: JSON string of the WorkOrder object. Returns: ``{"valid": true}`` if all six key bindings are well-formed, distinct, and the maintainer's signature is valid.
- `owp_verify_nested_claim`: Verify a nested claim (AgentRequest or HumanDecision) against a WorkOrder. This checks that: - The WorkOrder identity bindings are valid. - The claim's ``work_order_digest`` matches the WorkOrder. - The claim's actor is bound to a matching key in the WorkOrder. - The claim's Ed25519 signature is valid. Args: claim_json: JSON string of the AgentRequest or HumanDecision. work_order_json: JSON string of the parent WorkOrder. Returns: ``{"valid": true}`` if the nested claim passes all checks.
- `owp_list_domains`: List canonical OpenWorkProof domains; this tool takes no input parameters. Returns: A dict with ``canonical_domains`` (all 9) and ``signed_domains`` (8 — excludes ``sidecar-event`` which cannot be signed).
- `owp_validate_profile`: Validate a signed Evidence Lifecycle v0.2, v0.3, or v0.5 profile.
- `owp_integrity_observation_validate`: Assess one v0.5 population observation set against its contracts. This read-only tool never signs, commits, accepts, or settles anything. Signer authority is reported as ``not_checked``, never as authorized.
- `owp_control_observation_validate`: Assess one v0.5 control observation set against its contracts. This read-only tool never signs, commits, accepts, or settles anything. Signer authority is reported as ``not_checked``, never as authorized.
- `owp_scope_validate`: Intrinsically validate a v0.3 scope without checking authority. This read-only tool does not accept a ledger, private key, or signature instruction. Full Manager authority is checked only by the non-MCP commit boundary.
- `owp_scope_compare`: Compare a signed v0.3 scope with one verifier observation.
- `owp_status`: Replay an OpenWorkProof ledger and return its authoritative state. Args: ledger: Path to the SQLite ledger file.
- `owp_run_tests`: Run tests, write an execution receipt to the ledger, and save test evidence files. The ledger coordinator checks the signed request before execution. The configured executor writes execution artifacts under the runtime and evidence roots supplied in the payload. Args: ledger: SQLite ledger file that receives the execution receipt. payload: JSON string of the run-tests execution payload (must include the signed ``AgentRequest`` and typed arguments).
- `owp_repo_read`: Forward a repo-read execution to the ledger coordinator. Args: ledger: Path to the SQLite ledger file. payload: JSON string of the repo-read execution payload.
- `owp_run_verification`: Write verification results or signed decisions to the ledger, or prepare a draft. ``operation`` must be ``commit_arm``, ``prepare_decision``, or ``commit_decision``. ``commit_arm`` appends a validated verification result to the SQLite ledger. ``commit_decision`` appends the supplied signed verification decision. ``prepare_decision`` returns an unsigned draft without committing that decision. The tool never retries an indeterminate commit.
- `owp_get_decision`: Prepare, but do not sign or commit, a versioned decision draft.
- `owp_build_delivery_package`: Export a public, diagnostic, or customer-private delivery package.
- `owp_verify_surface_bundle`: Verify and replay one surface bundle without writing or signing.
- `owp_render_surface_report`: Return the verified derived report, never payment or acceptance.
- `owp_get_settlement_readiness`: Derive readiness only; this does not prove payment or settlement.
- `owp_get_schema`: Get the authoritative JSON Schema for an OpenWorkProof object type. Args: object_type: One of ``work-order``, ``capability-grant``, ``action-receipt``, ``acceptance-receipt``, ``acceptance-rejection-receipt``. version: Schema version (default ``0.1``).
- `owp_get_schema_digest`: Get the frozen SHA-256 digest of an authoritative JSON Schema. This digest is a protocol-review anchor: changing it requires an explicit version-bump decision. Args: object_type: One of the five schema-bearing object types. version: Schema version (default ``0.1``).
- `owp_analyze_repo`: Analyse a repository's structure: file count, languages, dependencies. Args: source: Local path or remote Git URL to the repository. clone_enabled: If ``True`` and *source* is a URL, clone it to a temporary directory first (default ``True``). Returns: Repository analysis including file entries, language stats, line counts, and dependency information.
- `owp_validate_judgment_commitment`: Validate one signed JudgmentCommitment (read-only, no authority). Without a ledger or trusted key context the authority is reported as ``not_checked``; this tool never signs and never commits.
- `owp_validate_action_binding_manifest`: Validate one signed ActionBindingManifest (read-only, no authority).
- `owp_get_binding_status`: Read the current binding decision head from a ledger (read-only).
- `owp_explain_binding_decision`: Verify and explain one BindingDecision (read-only).

## FAQ

### Does OpenWorkProof require an account or API key?

No, OWP does not require an OWP cloud account or API key to function.

### Does a 'VERIFIED' result mean the work is correct?

No, verification only checks evidence against the stated scope and trust inputs; it does not guarantee the business outcome is correct.
