Skip to main content
Glama
decision-anchor

decision-anchor-mcp

Official
by decision-anchor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to decision-anchor-mcp

No user-submitted related servers found.

    Related Servers

    • Anchord MCP

      nolenation04
      A
      license
      A
      quality
      C
      maintenance
      Anchord MCP is a hosted remote MCP server for AI agents that need canonical identity resolution and safe write evaluation across customer systems. Resolve companies and people to canonical AnchorIDs, inspect linked records and target-system coverage, and evaluate whether a proposed write should be allowed or blocked. Read-only by design.
      11
      28 npm
      MIT
    • @agledger/mcp-server by agledger-ai

      @agledger/mcp-serverofficial

      agledger-ai
      A
      license
      A
      quality
      A
      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
      60 npm
      -

    • CONTINUUM

      Cyrax321
      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.
      23
      Apache 2.0

    • veor

      winterbim
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.
      MIT

    • genpark-enterprise-merkle

      Alpha-Park
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and audit systems to hash execution logs into tamper-proof Merkle trees, compute cryptographic inclusion proofs, and verify audit-trail integrity on demand. It runs as a zero-dependency Python MCP server (stdio JSON-RPC) or as an importable module, exposing anchoring, proof generation, and integrity verification over local agent activity records.
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityActive
    ResponsivenessNo issues

    Resources