io.github.oleg-vdv/kepil
Related Servers
Alternatives to io.github.oleg-vdv/kepil
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to be governed by formal Gentzen sequent calculus proof trees, with human-in-the-loop approval gates and cryptographic audit trails for consequential actions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.MIT
- AlicenseBqualityCmaintenanceEnables AI agents to act on live business objects under enforceable per-call identity, per-tool grants, and mandatory human approval for irreversible actions, with connectors isolated from core logic.8MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to execute prediction-market trades through a risk-control gateway that enforces signed mandates and generates proof trails for accountability.0MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to screen proposed actions, enforce deterministic policies and limits, and produce tamper-proof signed audit receipts before any external side effect is executed.4 npmMIT
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of the workflow: profession discovery, order creation, step execution, status checks, pending human decisions, journal verification, and agent identity. There is no meaningful overlap between tool purposes.
Names are consistently lowercase snake_case and generally readable, but the pattern is mixed: list_professions, create_order, run_step, and verify_journal use verb-first naming, while order_status, pending_confirmations, and agent_passport are noun phrases. This is not chaotic, but the two naming styles make the set less predictable.
Seven tools is a well-scoped size for this domain. Each tool covers a necessary part of the order lifecycle without being redundant or excessive.
The core workflow is well covered: discover professions, create an order, execute steps, monitor status, see pending confirmations, verify the journal, and inspect the agent passport. The only notable gap is a lack of explicit cancellation or direct confirmation tools, but these may be intentionally handled outside the tool surface.