decision-anchor-mcp
OfficialRelated Servers
Alternatives to decision-anchor-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceConnects MCP-compatible AI agents to the AGLedger API for change control, recording every change with signed, hash-chained records. Provides API pass-through tools and an offline audit verifier.3303 npm-- AlicenseNot gradedqualityAmaintenanceUniversal verifiable recovery for long-running AI agents with semantic checkpoints, idempotent action ledger and hash chained log as a deny by default MCP server. Framework agnostic with adapters for LangGraph, LangChain and OpenAI plus gateway and OTel.28Apache 2.0
- 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
- AlicenseAqualityCmaintenanceEnables MCP-compatible hosts to record, retrieve, and verify LoopGrid decision evidence through tools for decisions, reviews, actions, outcomes, and verification.6Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to gate real-world side effects through a durable decision record, ensuring at-most-once initiation, deduplication, budget enforcement, and auditable outcomes across retries and failures.1522 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceCryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.-
TDQS
Scored across 30 tools
Most tools have distinct purposes, but there are several overlapping observation/distribution tools (observe_environment, observe_pattern, get_environment_anomaly, get_decision_metadata_distribution, get_self_classification_distribution) and similar session lookup tools (get_sdac_session, get_ise_status) that could cause confusion. Descriptions help but boundaries are not always clear.
Tool names generally follow a verb_noun pattern with snake_case (create_decision, list_decisions, confirm_decision). There are minor deviations like 'propose_bilateral' (verb_adjective) and 'get_dac_ur' (abbreviation), but overall the naming is consistent and predictable.
30 tools is heavy for a single MCP server, exceeding the typical range. While the breadth reflects the complex domain, several tools are highly specialized (e.g., multiple session types and distribution queries) and could be consolidated or split into separate servers.
Core decision lifecycle (create, confirm, get, list) is present, along with simulation and analytics. However, there are notable gaps such as no explicit tool for accepting/rejecting bilateral agreements, no way to verify counterparty decisions, and no update/delete for self_classification or agent profile. These omissions may require workarounds.