Skip to main content
Glama
dengyier

OpenWorkProof

by dengyier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to OpenWorkProof

No user-submitted related servers found.

    Related Servers

    • agent-passport-system-mcp

      agent-passport-system
      A
      license
      C
      quality
      A
      maintenance
      Cryptographic identity and trust protocol for AI agents. 38 MCP tools across 8 protocol layers: Ed25519 identity, delegation chains, values compliance, signed communication, policy engine, task coordination, cross-layer integration, and agentic commerce. 264 tests passing.
      154
      342 npm
      4
      Apache 2.0

    • attest

      mrpkk
      A
      license
      A
      quality
      A
      maintenance
      Verification for agent-produced artifacts: schema contract, emptiness, generation provenance and mandate authority. An MCP server (Model Context Protocol over Streamable HTTP) exposing verify_artifact, verify_artifact_batch and bridge_check tools. Deterministic, Ed25519-signed, verifiable offline.
      2
      Apache 2.0

    • RIGForge

      mrodgersjs-web
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server enabling AI coding agents to seal work into cryptographically signed ProofPackets and verify them, catching forged completion claims and enforcing spec-bound acceptance criteria.
      MIT

    • fallimmig-us-mcp

      sjgant80-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.
      MIT

    • GoLogX (logx-mcp)

      AyoubTadlaoui
      A
      license
      Not graded
      quality
      D
      maintenance
      Tamper-evident audit logging for AI agents. Append-only, hash-chained, optionally Ed25519-signed log. The MCP server lets an agent keep and verify a record of what it actually did.
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 29 tools

    Disambiguation2/5

    There are many overlapping validate/verify tools: owp_scope_validate, owp_validate_judgment_commitment, owp_validate_action_binding_manifest, owp_validate_profile, owp_integrity_observation_validate, owp_control_observation_validate, owp_verify_signature, owp_verify_work_order, and owp_verify_nested_claim all perform read-only validation and are easy to confuse. Also owp_get_decision, owp_get_binding_status, and owp_run_verification's prepare_decision operation have fuzzy boundaries around decision drafting versus reading state.

    Naming Consistency4/5

    All tools use snake_case with a consistent owp_ prefix, which is good. However, the verb ordering is mixed: most use verb_noun (owp_get_schema, owp_compute_digest), while several use noun_verb (owp_scope_validate, owp_integrity_observation_validate, owp_control_observation_validate).

    Tool Count2/5

    29 tools is heavy and exceeds the well-scoped range; the surface feels sprawling. The validate/verify family alone accounts for around ten tools, suggesting overlap rather than each tool clearly earning its place.

    Completeness4/5

    For an OpenWorkProof protocol server, the surface covers schemas, keys, signing, digest computation, verification, ledger status, decisions, delivery packages, and settlement readiness, giving broad lifecycle coverage. Minor gaps exist but the core sign/verify/commit/settle workflow appears workable.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources