CouchLoop EQ

Name: CouchLoop EQ
Author: couchloop

CouchLoop EQ provides behavioral governance for LLMs. It monitors AI responses for hallucination, inconsistency, tone drift, and unsafe reasoning patterns, while also managing stateful sessions and guided journeys that remember where you left off.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://ceq--couchloop.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "CouchLoop EQ": {
      "url": "https://ceq--couchloop.run.tools"
    }
  }
}

能力清单

工具	说明
memory	Save and retrieve context, insights, checkpoints, and decisions across conversations. Prevents AI amnesia. Use action "save" to store, "recall" to retrieve, "list" to browse. Recall does keyword search (tokenized substring match across saved content and checkpoint keys), not semantic vector search; pass a UUID in `content` to look up a specific checkpoint by id. Use type "checkpoint" for sprint progress ("save where I am", "bookmark this"), type "decision" for architectural choices and milestones ("lock this in", "we decided on X"), type "constraint" for rules the AI must follow ("never do X again", "always ask before Y"). Constraints tagged "ai-mistake" are auto-saved by the review tool when it catches errors — recall these at the start of new conversations to avoid repeating past mistakes. Triggers: "remember this", "stash this context", "where did we leave off", "what did we decide", "what was the approach we picked", "load my previous context", "don't lose this", "never do that again". With no arguments, returns a summary of everything saved.
conversation	Guided self-reflection, burnout check-ins, and wellness conversations with crisis detection (routed to the therapeutic AI backend). SEPARATELY, it hosts data-driven DEVELOPER journeys that run LOCALLY from your real codebase (git/CI/PRs) and never touch the therapeutic backend: "daily-standup" (3 min: what actually shipped + in-flight + CI/review state → today's focus), "sprint-retro" (8 min: velocity, hot spots, reverts, CI health → wins/pains/decisions/action item), "debug-postmortem" (5 min: failing test + fix diff → root cause + guardrail). For developer journeys the agent gathers the facts and leads with them — it does not ask the user to recall what is already in the repo. Triggers: "I'm burned out", "need a break", "feeling stuck", "let's do a retro on my week", "check in with me", "I keep going in circles", "rubber duck my frustration", "decompress", "vent session", "standup with myself", "postmortem on that bug". Use when the user sounds frustrated, stuck, or wants a non-code conversation about how work is going. NOTE: if the user is angry at AI output specifically (cursing at the AI, "you broke it"), prefer the review tool with verify mode first to address the problem, only use conversation if frustration persists without a code context or the user explicitly wants to talk it out.
review	Unified code review, package audit, pre-delivery verification, and error correction. Modes: "code" for security/quality analysis, "packages" for dependency audit, "verify" for hallucination/fact check (starts correction flow), "confirm" for user confirming detected issue, "apply-fix" for user approving the fix, "dismiss" for user saying "that's not the issue", "full" for all checks. Triggers: "review this", "sanity check this", "is this safe to ship", "check before I push", "audit my deps", "sniff test this", "vet these dependencies". ALSO use verify mode when the user expresses distrust or frustration: "are you sure", "that doesn't look right", "prove it", "did you make that up", "that broke everything", "why did you do that", "I didn't ask for this". Profanity or anger directed at the AI is a strong signal to immediately run verify. CORRECTION FLOW: verify detects issue → present it plainly and ask "is this what you mean?" → user confirms (call with mode "confirm") → explain fix and ask permission → user approves (call with mode "apply-fix") → apply. If user says no (mode "dismiss"), ask them to explain. Memory auto-saves the mistake ONLY after user confirms. Use proactively when the user pastes code, shares a diff, or adds new packages.
status	System dashboard — session progress, history summaries, context usage, protection status, and preferences. Use for high-level overviews and summaries, NOT for retrieving specific stored insights or decisions (use remember with action recall for that). Triggers: "how am I doing", "what's my progress", "show my history", "dashboard", "overview", "my settings", "context window", "backup status", "what do you know about me". Returns personalized status with actionable next steps.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。