OpenWorkProof
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OWP_TEAM_TOKEN | No | Shared secret for AgentTeams network authentication | |
| OWP_TEAM_TIMEOUT | No | Timeout in seconds for AgentTeams network operations, e.g. 5.0 | |
| OWP_TEAM_ENDPOINT | No | Endpoint for AgentTeams network connection, e.g. 127.0.0.1:18742 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| owp_generate_keypairA | Generate a new Ed25519 key pair for signing OpenWorkProof objects. Returns the private key as a hex string and the public key as
base64url, along with the derived |
| owp_compute_key_idA | Compute the OpenWorkProof Args: public_key_b64url: The raw public key bytes encoded as unpadded base64url (43 characters). |
| owp_sign_payloadA | Sign a canonical OpenWorkProof payload with an Ed25519 private key. Args:
object_type: One of the allowed signed domains (call
Returns:
The signed payload dict with |
| owp_verify_signatureA | 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 Returns:
|
| owp_compute_digestA | Compute the canonical SHA-256 digest of an OpenWorkProof payload. The digest is computed over the RFC 8785 JCS canonicalisation of
Args: object_type: One of the allowed canonical domains. payload: JSON string of the payload object. |
| owp_verify_work_orderA | Verify a WorkOrder's identity bindings and maintainer signature. Args: work_order_json: JSON string of the WorkOrder object. Returns:
|
| owp_verify_nested_claimA | Verify a nested claim (AgentRequest or HumanDecision) against a WorkOrder. This checks that:
Args: claim_json: JSON string of the AgentRequest or HumanDecision. work_order_json: JSON string of the parent WorkOrder. Returns:
|
| owp_list_domainsA | List all allowed canonical domains for OpenWorkProof objects. Returns:
A dict with |
| owp_validate_profileC | Validate a signed Evidence Lifecycle v0.2, v0.3, or v0.5 profile. |
| owp_integrity_observation_validateA | 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 |
| owp_control_observation_validateA | 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 |
| owp_scope_validateA | 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_compareB | Compare a signed v0.3 scope with one verifier observation. |
| owp_statusA | Replay an OpenWorkProof ledger and return its authoritative state. Args: ledger: Path to the SQLite ledger file. |
| owp_run_testsA | Forward a run-tests execution to the ledger coordinator. Args:
ledger: Path to the SQLite ledger file.
payload: JSON string of the run-tests execution payload (must
include the signed |
| owp_repo_readB | 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_verificationA | Run exactly one explicit v0.2, v0.3, or v0.5 verification operation.
|
| owp_get_decisionB | Prepare, but do not sign or commit, a versioned decision draft. |
| owp_build_delivery_packageC | Export a public, diagnostic, or customer-private delivery package. |
| owp_verify_surface_bundleB | Verify and replay one surface bundle without writing or signing. |
| owp_render_surface_reportC | Return the verified derived report, never payment or acceptance. |
| owp_get_settlement_readinessB | Derive readiness only; this does not prove payment or settlement. |
| owp_get_schemaA | Get the authoritative JSON Schema for an OpenWorkProof object type. Args:
object_type: One of |
| owp_get_schema_digestA | 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 |
| owp_analyze_repoA | Analyse a repository's structure: file count, languages, dependencies. Args:
source: Local path or remote Git URL to the repository.
clone_enabled: If Returns: Repository analysis including file entries, language stats, line counts, and dependency information. |
| owp_validate_judgment_commitmentA | Validate one signed JudgmentCommitment (read-only, no authority). Without a ledger or trusted key context the authority is reported as
|
| owp_validate_action_binding_manifestB | Validate one signed ActionBindingManifest (read-only, no authority). |
| owp_get_binding_statusC | Read the current binding decision head from a ledger (read-only). |
| owp_explain_binding_decisionB | Verify and explain one BindingDecision (read-only). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Many tools are genuinely distinct object-type validators, but there is heavy semantic overlap among 'verify', 'validate', 'assess', and 'explain' operations, especially around binding decisions and observed evidence. Descriptions help, but an agent could easily misselect among the many validate/verify variants without deep domain knowledge.
The owp_ prefix and snake_case are consistent, but verb placement is mixed: most tools use verb_noun, while several use noun_verb or noun-only forms, such as owp_scope_validate, owp_integrity_observation_validate, owp_scope_compare, and owp_status. The pattern is readable but not uniform.
With 29 tools, the server exceeds the heavy threshold, and many near-parallel validators could likely be consolidated into parameterized tools. The breadth of object types explains some volume, but the tangential owp_analyze_repo tool and multiple one-off validators make the count feel bloated.
The server covers key generation, signing, digest computation, schema lookup, signature verification, ledger status, and a wide set of object-specific validators. However, there are notable gaps: several schema-defined object types like capability-grant and acceptance-receipt have no dedicated validation tools, and there is no lifecycle management for keys or ledgers, with authority checks deliberately deferred to non-MCP boundaries.