Skip to main content
Glama
decision-anchor

decision-anchor-mcp

Official

Related Servers

Alternatives to decision-anchor-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Connects 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.
      3
      303 npm
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Universal 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.
      28
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible hosts to record, retrieve, and verify LoopGrid decision evidence through tools for decisions, reviews, actions, outcomes, and verification.
      6
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Cryptographically 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

    B3.4/5.0

    Scored across 30 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues