Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OpenWorkProof

PYPI · OPENWORKPROOF

Verifiable execution for AI agents: Ed25519-signed work contracts and audit trails.

Available components

+27 this week 66 Trust /100

Last scanned (7 hours ago)

Scores higher than 64% of PyPI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 5 of 40 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2035 tokens (~70/item across 29 items; 29 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +26
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.00 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 1.4.0 → 1.4.2 functional
    • Package version: 1.4.0 → 1.4.1 functional
  • 14 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 30 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Sept 26 0
    • Provenance: unverified → fail ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 26 Oct 2026 · Analysed pypi/openworkproof@1.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 40 packages
Packages resolved 40
Stale 4
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 29 exposed · ~2,035 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
owp_analyze_repo ~105

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.

NameTypeReqDescription
clone_enabledboolean––
sourcestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_build_delivery_package ~45

Export a public, diagnostic, or customer-private delivery package.

NameTypeReqDescription
ledgerstringyes–
outputstringyes–
privacy_viewstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_compute_digest ~122

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.

NameTypeReqDescription
object_typestringyes–
payloadstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_compute_key_id ~68

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).

NameTypeReqDescription
public_key_b64urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_control_observation_validate ~62

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.

NameTypeReqDescription
payload_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_explain_binding_decision ~31

Verify and explain one BindingDecision (read-only).

NameTypeReqDescription
payload_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_generate_keypair ~53

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``.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

owp_get_binding_status ~32

Read the current binding decision head from a ledger (read-only).

NameTypeReqDescription
ledger_pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_get_decision ~41

Prepare, but do not sign or commit, a versioned decision draft.

NameTypeReqDescription
ledgerstringyes–
request_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_get_schema ~98

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``).

NameTypeReqDescription
object_typestringyes–
versionstring––

Structured output declared, but exposes no named fields.

No examples provided.

owp_get_schema_digest ~86

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``).

NameTypeReqDescription
object_typestringyes–
versionstring––

Structured output declared, but exposes no named fields.

No examples provided.

owp_get_settlement_readiness ~33

Derive readiness only; this does not prove payment or settlement.

NameTypeReqDescription
ledgerstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_integrity_observation_validate ~63

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.

NameTypeReqDescription
payload_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_list_domains ~60

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).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

owp_render_surface_report ~30

Return the verified derived report, never payment or acceptance.

NameTypeReqDescription
package_pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_repo_read ~58

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.

NameTypeReqDescription
ledgerstringyes–
payloadstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_run_tests ~110

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).

NameTypeReqDescription
ledgerstringyes–
payloadstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_run_verification ~126

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.

NameTypeReqDescription
ledgerstringyes–
operationstringyes–
payloadstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_scope_compare ~40

Compare a signed v0.3 scope with one verifier observation.

NameTypeReqDescription
observed_scope_jsonstringyes–
scope_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_scope_validate ~65

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.

NameTypeReqDescription
scope_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_sign_payload ~135

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.

NameTypeReqDescription
object_typestringyes–
payloadstringyes–
private_key_hexstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_status ~40

Replay an OpenWorkProof ledger and return its authoritative state. Args: ledger: Path to the SQLite ledger file.

NameTypeReqDescription
ledgerstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_validate_action_binding_manifest ~33

Validate one signed ActionBindingManifest (read-only, no authority).

NameTypeReqDescription
payload_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_validate_judgment_commitment ~61

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.

NameTypeReqDescription
payload_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_validate_profile ~40

Validate a signed Evidence Lifecycle v0.2, v0.3, or v0.5 profile.

NameTypeReqDescription
profile_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_verify_nested_claim ~145

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.

NameTypeReqDescription
claim_jsonstringyes–
work_order_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_verify_signature ~144

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.

NameTypeReqDescription
object_typestringyes–
public_key_b64urlstringyes–
signed_payloadstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_verify_surface_bundle ~30

Verify and replay one surface bundle without writing or signing.

NameTypeReqDescription
package_pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

owp_verify_work_order ~79

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.

NameTypeReqDescription
work_order_jsonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the OpenWorkProof MCP server?

OpenWorkProof runs locally as a PyPI package, launched with uvx openworkproof. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · openworkproof

# add to Claude Code
claude mcp add dengyier-openworkproof -- uvx openworkproof
Common questions

What is the OpenWorkProof MCP server?

OpenWorkProof is an MCP server listed in the public MCP registry as io.github.dengyier/OpenWorkProof. Verifiable execution for AI agents: Ed25519-signed work contracts and audit trails. This page covers its PyPI package (openworkproof).

Is the OpenWorkProof MCP server safe to use?

OpenWorkProof scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the OpenWorkProof MCP server expose?

OpenWorkProof exposes 29 tools: owp_generate_keypair, owp_compute_key_id, owp_sign_payload, owp_verify_signature, owp_compute_digest, and 24 more. Their descriptions and schemas cost roughly 2,035 tokens of context every time the server is loaded.

Is the OpenWorkProof MCP server still maintained?

OpenWorkProof is still listed as active in the MCP registry. We last reached this channel on 26 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the OpenWorkProof MCP server under?

OpenWorkProof declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.