Skip to main content
Glama
jstibal

Openterms-mcp

by jstibal

Related Servers

Alternatives to Openterms-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to propose wallet payments while a local, human-authored policy decides whether each transaction is approved, requires human confirmation, or is refused, and records every decision in a signed, append-only ledger.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Governance primitives for autonomous agents. Verify actions against policy, record signed provenance, and bind intents cryptographically. Free tier available.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides cryptographic governance receipts for AI agents, enabling pre-execution evaluation and signed verdicts (EXECUTE/BLOCK/REVIEW/SHADOW) with offline-verifiable audit trails.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gates every AI agent tool call against your policy before it runs, then writes a hash-chained, tamper-evident record of what was decided and what happened. Anyone can verify that record offline, without your software, your systems or any key you hold.
      12
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: issuing, verifying, listing, policy simulation, and provider stats are separate concerns. The only ambiguity is between verify_receipt and verify_receipt_by_hash, though their descriptions clarify the different input methods.

    Naming Consistency4/5

    Most tool names follow a consistent lowercase verb_noun pattern such as verify_receipt, issue_receipt, and get_policy. Two noun-phrase names, policy_decisions and provider_activity, deviate slightly but are still readable and predictable.

    Tool Count5/5

    With 10 tools, the server is well-scoped for its terms/receipt policy domain. Each tool serves a distinct operational need: policy access, simulation, decisions, receipt issuance/verification, and workspace/provider management.

    Completeness4/5

    The tool set covers policy retrieval/simulation, receipt issuance/verification/listin, and workspace/provider accounting, so the core workflow is complete. Minor gaps exist such as no explicit receipt revocation or policy update, but these are not clearly required by the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues