Skip to main content
Glama

Related Servers

Alternatives to OpenWorkProof

No user-submitted related servers found.

    Related Servers

    • 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.
      152
      163 npm
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      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
    • 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
    • A
      license
      Not graded
      quality
      C
      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.
      7
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      AI agent identity, permissions, trust scores, and tamper-evident audit trails. 17 MCP tools: register agents (Ed25519 keypairs), check permissions (sub-5ms), emit audit events, verify trust scores (0-100), delegate credentials, ephemeral agents. IETF Internet-Draft filed. Works with LangChain, OpenAI, CrewAI, Stripe ACP. npx @vorim/mcp-server
      17
      101 npm
      73
      MIT

    TDQS

    B3.1/5.0

    Scored across 29 tools

    Disambiguation3/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive