credence
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREDENCE_DB | No | Path to the database file. Default is 'epistemic_registry.db' in the working directory. Set to a global path like '~/.credence/registry.db' to keep it global. | |
| CREDENCE_NO_LOG | No | Set to '1' to disable event logging to ~/.credence/events.jsonl. | |
| CREDENCE_SESSION_ID | No | Session tracking identifier to keep constraints stable across directory changes and terminal restarts. | |
| CREDENCE_MAX_CONSTRAINTS | No | Override the default maximum number of constraints (500) per session. Provide a numeric string. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| credence_registerA | Register an uncertain constraint in the epistemic registry. Use whenever the user states something uncertain: an unconfirmed vendor claim, an assumption, a 'I think' statement, a number from a quick search. All registered values are UNVERIFIED until explicitly confirmed. |
| credence_verifyA | Mark a registered constraint as verified with its confirmed value. After verification the constraint is excluded from Truth Buffer injection and Consistency Enforcer enforcement. An audit trail is recorded — who verified, on what basis, and what the confirmed value is. |
| credence_constraintsA | List all unverified constraints for a session. Use before writing code that may embed user-stated values, or at session end to audit what still needs confirmation. |
| credence_gateA | Pre-execution epistemic gate (CP4): block irreversible tool calls that embed unverified constraint values. Call BEFORE write_file, execute_code, send_request, deploy, or any tool that would embed a user-stated value into code or infrastructure. Uses synonym-expansion to catch paraphrase overlap ("how fast" ↔ "rate limit"). |
| credence_scanA | Generation-Time Constraint Scanner (CP3): scan model output for numeric literals that match registered unverified constraints. Two annotation tiers (no confidence scores — unknown = unverified): ⚠⚠ CREDENCE[stale] — source="temporal_scan" (structurally stale values) ⚠ CREDENCE[unverified] — all other registered constraints Scans both code blocks and prose. |
| credence_self_probeA | Extract domain-relevant values from generated code and register them as unverified by default — zero API calls, zero model judgment. Works with any coding agent (Claude Code, Codex, Cursor, Copilot). The agent's own model is NOT asked to rate its confidence. Instead, every extracted value is treated as unverified until the user explicitly calls credence_verify with evidence. |
| credence_memory_snapshotA | Persist all unverified constraints from a session as project memory. Call at the END of a session. Next session on the same project calls credence_memory_recall to inherit what was still uncertain — the new session starts knowing what it doesn't know. |
| credence_memory_recallA | Load project memories into a new session at session start. Call at the START of a new session. Injects all previously unverified constraints into the new session so enforcement works from turn 1. |
| credence_autoverifyA | Scan text for natural-language verification signals and auto-verify matching unverified constraints — zero API calls. When a user says "actually it's 3600", "confirmed: rate limit is 100", or "I checked, the port is 5432", this tool detects those confirmation phrases and automatically marks matching constraints as verified. Matching: a constraint is a candidate if ≥ 2 non-stopword tokens from the constraint text appear in the confirmation sentence. |
| credence_auditA | Per-session epistemic timeline — all constraints (verified and unverified) in chronological order with full certainty trajectory. Use to answer "what have we tracked this session?" or "what's still open?" before starting an implementation phase. |
| credence_resetA | Clear all constraints for a session. Use after completing a verification pass, or when starting a fresh implementation phase where all prior uncertain values have been resolved. |
| credence_session_summaryA | Brief of unverified constraints for a session. Returns action_required, unverified_count, and a summary list so the model can decide whether to snapshot or prompt the user to verify. |
| credence_diffA | Compare two texts for numeric contradictions. Extracts numeric claims from both texts and detects when the same topic context has different values. Optionally checks against verified registry constraints when session_id is provided. |
| credence_project_statusA | Project-wide epistemic health dashboard. Shows all unverified constraints across sessions that have been snapshotted to this project via credence_memory_snapshot. |
| credence_scan_ghostsA | Scan a session for ghost constraints. Ghost constraints are vendor-supplied facts registered without hedging language — they look certain but are actually unverified. The ghost detector flags unverified vendor_claim constraints with no hedging. |
| credence_marker_healthA | Marker statistics from accumulated session data. Shows which uncertainty markers are most reliable (high precision) vs. noisy (low precision) based on observed FCR outcomes. Requires 10+ sessions before returning data. Returns: status (insufficient_data|available), threshold, markers list. |
| credence_bandit_statusA | Adaptive compression threshold status (Thompson sampling bandit). Returns current learned thresholds per session type, or the static defaults if insufficient data has been collected (< 100 sessions). Returns: status (learning|active), threshold, current_thresholds, message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lakshmi-Chakradhar-Vijayarao/credence-ai'
If you have feedback or need assistance with the MCP directory API, please join our Discord server