Skip to main content
Glama

Related Servers

Alternatives to credence

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables safe auto-approval for coding agents by gating file-changing actions to only execute when values were explicitly stated by an authorized developer or repository maintainer, refusing actions derived from agent-read text.
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables autonomous agents to detect under-specified, high-stakes user goals, assess their reversibility and risk, and construct minimal multiple-choice clarifications before executing. Runs as a zero-dependency MCP server or importable Python module that gates autonomous execution behind those clarifying questions.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables LLMs to propose UPDATE/DELETE SQL that is run in a transaction, measured, and rolled back, requiring human approval before applying to prevent unauthorized changes.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Tracks what an agent KNOWS vs INFERS vs ASSUMES with calibrated confidence. Provides tools to register, query, and analyze epistemic status of claims across domains.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to maintain local, auditable, undoable architecture-state memory, recall what is currently true, explain why decisions changed, and atomically undo bad memories without cascading stale-child invalidation.
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Each tool has a distinct purpose, though some overlap exists between constraint listing tools (credence_constraints, credence_session_summary, credence_audit). Descriptions clarify their different focuses, reducing ambiguity.

    Naming Consistency4/5

    All tools follow a 'credence_' prefix with descriptive lowercase_underscore names. Most are verb_noun (e.g., credence_register, credence_verify) or noun phrases (e.g., credence_project_status). Slight inconsistency in verb forms but overall pattern is consistent.

    Tool Count4/5

    17 tools is on the higher side but appropriate for the complex domain of epistemic tracking. Each tool addresses a specific need, and the count is justified by the breadth of operations (register, verify, scan, gate, memory, audit, etc.).

    Completeness4/5

    The tool set covers the full lifecycle of constraint management: registration, verification, scanning, gating, memory persistence, and auditing. Minor gaps exist (e.g., no single constraint deletion or update), but core workflows are well-covered.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data