Openterms-mcp
Related Servers
Alternatives to Openterms-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to evaluate every payment intent against user-signed, on-chain-anchored policies before money moves, returning allow, deny, or human-approval verdicts. Provides policy versioning, revocation, spend reports, and audit trails through MCP tools that agents cannot alter without the owner's key.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables 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.-

agentguardofficial
AlicenseNot gradedqualityAmaintenanceEnforces 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- AlicenseNot gradedqualityNot gradedmaintenanceGovernance primitives for autonomous agents. Verify actions against policy, record signed provenance, and bind intents cryptographically. Free tier available.-
- AlicenseNot gradedqualityDmaintenanceProvides cryptographic governance receipts for AI agents, enabling pre-execution evaluation and signed verdicts (EXECUTE/BLOCK/REVIEW/SHADOW) with offline-verifiable audit trails.MIT
- AlicenseAqualityAmaintenanceGates 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.41,134 PyPI15AGPL 3.0
TDQS
Scored across 10 tools
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.
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.
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.
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.