credence
Related Servers
Alternatives to credence
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to add decision drafts, evidence, and counterarguments to a shared local decision state, while users confirm or reopen decisions in a web console. Prevents unverified agent answers from being silently turned into code.MIT
- AlicenseNot gradedqualityFmaintenanceEnables 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.78 npmMIT
- AlicenseNot gradedqualityCmaintenanceTracks 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
- AlicenseNot gradedqualityCmaintenanceEnables Alexa+ agents to maintain auditable operational continuity across shifts by turning speech into verifiable state, persisting unresolved work, refusing unverified actions, and requiring human approval before executing and confirming high-risk tasks.MIT
- AlicenseNot gradedqualityAmaintenanceUI interaction verifier for computer-use agents — tracks which UI elements exist and their expected behavior to catch ghost actions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables extraction of structured data from messy text with multi-model verification and human-in-the-loop review, surfacing only high-confidence results or flagging uncertain fields for confirmation.MIT
TDQS
Scored across 17 tools
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.
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.
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.).
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.