Dear User

io.github.bleedmode由 GitHub 账号 bleedmode 发布v1.0.20更新于 Oct 24, 2026

Tells you how you and your Claude agent actually work together. Local-only, no API keys.

概览

AI 生成的概览

在本地审查 Claude Code 或 Claude Desktop 配置,评估协作质量并标记泄露的密钥、配置冲突和结构问题。

可以做什么
Dear User 是一个本地 MCP 服务器,会检查你的代理配置文件(CLAUDE.md 或 AGENTS.md)、记忆文件、技能、钩子和会话元数据。它的工具可生成带有人格画像和 0-100 评分的协作报告及改进建议,扫描泄露的密钥和提示注入风险,并检查孤立任务、重叠技能和失效钩子等健康问题。它还能生成可分享的统计卡片、保留历史报告,并应用或忽略建议。
适用场景
适合希望对 Claude 配置做一次快速本地审查的用户,尤其是跨项目积累了大量钩子、技能和记忆文件的情况。也适合想要密钥泄露和规则冲突检查、但不想自建 lint 流程的人。
运行要求
通过 npx 以 stdio 方式在本地运行 npm 包 @poisedhq/dearuser-mcp,需要 Node.js。无需 API 密钥、注册或云账户。可选的 Wrapped 卡片分享需要 DEARUSER_SUPABASE_URL 和 DEARUSER_SUPABASE_SERVICE_KEY。
安装前请注意
报告保存在本地 SQLite 数据库中。share_report 工具会把匿名化的 Wrapped 卡片上传到公开网址,feedback 工具会把你的消息文本发送到第三方收件箱;其他工具均在本地运行。安全扫描会读取可能含有机密的配置和记忆文件,分享前请先检查结果。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Dear User,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Dear User

Your AI agent works for you — but how well do you work together?

Dear User is an open-source tool that audits your Claude Code setup and tells you exactly what to fix. It scores your collaboration, finds leaked secrets and config conflicts, and checks system health — all locally, nothing uploaded unless you explicitly share your Wrapped card.

claude mcp add --scope user dearuser -- npx -y @poisedhq/dearuser-mcp@latest

Then ask Claude: "Analyze my collaboration with Claude"

Landing: dearuser.ai · Feedback: use the feedback tool in Claude, or open an issue


What it does

Dear User is an MCP server (Model Context Protocol — the plugin system Claude Code and Claude Desktop use). Once installed, it shows up as a set of tools your agent can call. No GUI, no sign-up, no cloud account.

Three local reports, one shareable Wrapped card, one feedback channel:

ToolWhat it doesExample prompt
collabFull collaboration report — persona, 0-100 score, friction patterns, specific recommendations"How good is my Claude setup?"
securityLeaked secrets, prompt-injection surfaces, rule conflicts in your agent contract (CLAUDE.md or AGENTS.md)"Check my config for leaked API keys"
healthStructural coherence — orphan scheduled tasks, overlapping skills, dead hooks"Is anything broken in my setup?"
wrappedSpotify-style shareable stats card — scores + counts + persona. Opt-in public URL via share_report."Give me my Dear User Wrapped"
feedbackSend a note to the Dear User inbox"Send feedback: the health report could be shorter"

Plus helpers: onboard (7-step guided setup), history (trend without re-scanning), help (menu), implement_recommendation, dismiss_recommendation, share_report (Wrapped-only upload).

Launch highlights

  • Shareable Wrapped — run wrapped, then share_report to get a dearuser.ai/r/<token> URL for your stats card. Anonymized before upload (paths collapsed to basenames, emails stripped, secrets redacted). Collab/security/health reports stay local — findings can carry business context that isn't safe to auto-share.
  • 12-category secret scanner — OpenAI, Anthropic, GitHub, AWS, Stripe, Slack, Google, Supabase, Vercel, private keys, generic env secrets, bearer tokens. Scans CLAUDE.md / AGENTS.md, memory files, skills, hooks.
  • AGENTS.md native support — first-class input alongside CLAUDE.md. Works out of the box for Cursor, Codex, Aider, Cline, Zed and anyone following the Linux Foundation cross-tool standard. Both files in the same directory? We merge them.
  • Semantic conflict detection (new) — finds rules that contradict each other even when they don't share keywords. "Commit often" vs. "ask before commit" gets flagged.
  • Score calibrated against reality — two studies: 988 public Claude Code setups with substrate committed (median 32/100, max 63) and 2,895 standalone CLAUDE.md files (median 18, max 60). The substrate corpus is the apples-to-apples benchmark for live scores. See research/calibration/ for both studies.

Install

One command per client. Full guide: docs/install.md.

Claude Code (CLI)

bash
claude mcp add --scope user dearuser -- npx -y @poisedhq/dearuser-mcp@latest

Restart Claude Code afterwards so the tools appear.

Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "dearuser": {      "command": "npx",      "args": ["@poisedhq/dearuser-mcp"]    }  }}

Cursor, Windsurf, Cline, Zed — see docs/install.md.

Optional: install the slash commands (see Commands for the full list) so you can type /dearuser-collab instead of asking in prose:

bash
npx -p @poisedhq/dearuser-mcp dearuser-install-skills

Your first 5 minutes

After installing, restart your client and try these in order:

  1. Baseline scan:

    Run Dear User collab on this project

    You'll get a persona (Vibe Coder / Senior Developer / Indie Hacker / Venture Studio / Team Lead), a 0-100 score across 7 categories, and 3-10 concrete recommendations.

  2. Security sweep:

    Run Dear User security

    Checks your agent contract (CLAUDE.md or AGENTS.md), memory, skills and hooks for leaked tokens, injection surfaces and rule conflicts.

  3. Share the result (optional):

    Share my collab report

    Returns a dearuser.ai/r/<token> link. Anonymized before upload. You choose whether to paste it anywhere.

Example output from collab:

Persona: Indie Hacker (87% confidence)Score:   73 / 100
Top friction:  • Quality Standards — no test-before-commit rule in CLAUDE.md  • Memory Health    — 2 memory files haven't been touched in 90+ days  • Communication    — no language preference stated (English vs Danish mixing)
Recommendations (3 shown, 5 total):  1. Add a "Session start protocol" block to CLAUDE.md  (apply with: implement_recommendation)  2. Rotate the OpenAI key leaked in ~/.claude/memory/api-notes.md  3. Merge overlapping skills: deploy-check and ship-check share 80% of their rules

Commands

Eight slash commands ship with Dear User. Ask your agent by name, or type the slash command if you installed them with dearuser-install-skills.

CommandWhat it does
/dearuser-collabCollaboration analysis — persona, 0-100 score across 7 categories, prioritized recommendations.
/dearuser-healthSystem health — orphan jobs, overlap, stale schedules, missing MCP registrations, reconciliation gaps.
/dearuser-securitySecret scan, prompt-injection surfaces, and rule conflicts in your agent contract.
/dearuser-wrappedShareable collaboration stats in a Spotify-Wrapped style card.
/dearuser-onboardConversational 7-step setup for first-time users.
/dearuser-historyShow your last reports, score trend over time, or what changed since the last run — no re-scan.
/dearuser-feedbackSend a short note (bug, request, reaction) to the Dear User founders.
/dearuser-helpShow what Dear User can do and list every tool.

Three in-chat actions the agent can call for you: share_report (upload a Wrapped card to dearuser.ai/r/<token>), implement_recommendation (apply a pending recommendation), dismiss_recommendation (mark one irrelevant).

Privacy

Dear User is local-first. Your scans stay on your machine:

  • Your agent contract (CLAUDE.md or AGENTS.md), memory, skills, hooks and session metadata are read but never uploaded
  • Results are stored in ~/.dearuser/dearuser.db (SQLite, WAL mode)
  • The optional localhost dashboard reads from that DB — nothing is transmitted
  • Dear User reads session metadata only (counts, lengths) — never your actual conversation content
  • No API keys required, no sign-up, no telemetry

The only exceptions are things you explicitly trigger:

  • share_report (Wrapped only) — your Wrapped card is anonymized (paths collapsed, emails stripped, anything matching our secret patterns redacted) and uploaded to dearuser.ai so you can share a URL. Your local DB is not modified. You can set an expires_at to auto-expire the link. Collab/security/health reports are NOT shareable — findings can carry business context (project names, client names, architecture notes) we don't think should live on a public URL.
  • feedback — when you call the feedback tool, your message goes to our Supabase inbox. That's the whole point of the tool. We don't attach your scans or files — only the text you write.

No other tool transmits anything. If share_report isn't configured with DEARUSER_SUPABASE_URL + DEARUSER_SUPABASE_SERVICE_KEY, it errors out cleanly and the rest of Dear User keeps working.

Full privacy details: docs/privacy.md.

How it works

Your files (CLAUDE.md or AGENTS.md, memory, hooks, skills, sessions)        │    Scanner ──► Parser ──► Engines (scoring, secrets, conflicts, health)        │ Persona detection → Scoring → Gap analysis → Recommendations        │    Feedback loop (tracks which recommendations you implemented)        │    ~/.dearuser/dearuser.db  ←  dashboard reads from here
  • 5 personas detected from your setup — each gets tailored recommendations
  • 7 scoring categories: Role Clarity, Communication, Autonomy Balance, Quality Standards, Memory Health, System Maturity, Coverage
  • Feedback loop: Dear User remembers what it recommended. Next run, it checks which ones you implemented and shows the score delta.

Who it's for

  • "Vibe coders" — you prompt Claude and ship product, but you're never quite sure if your setup is actually working. Dear User tells you.
  • Senior developers — you want a fast audit for leaked secrets, config drift and rule conflicts without wiring up a custom lint pipeline.
  • Indie hackers / solo founders — you've accumulated hooks, skills and memory across projects. Dear User surfaces what's orphaned or contradicting itself.
  • Team leads — you want a local audit of your team's shared agent setup. Collab, security and health reports stay on your machine; only your personal Wrapped card can be shared publicly.

Repository layout

  • mcp/ — @poisedhq/dearuser-mcp npm package (the MCP server). See mcp/README.md for development notes.
  • web/ — dearuser.ai landing + share-report pages (Astro).
  • docs/ — install guide, privacy doc, per-platform setup (Supabase/GitHub/Vercel for the optional security platform advisors).
  • research/ — calibration data + architecture notes we're willing to share.

Contributing

See CONTRIBUTING.md. Bug reports and small fixes welcome via GitHub issues and PRs.

Community & support

Links

License

Dear User is MIT-licensed. See LICENSE.

Open-core commitment: everything in this repo is MIT and stays MIT. If we ever build team or hosted features (agency dashboards, cross-project trend lines, vertical-specific benchmarks), they'll live in separate repos with their own license — never by pulling pieces out of this one.

来源:README.md,提交 a75dd4b

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.0.20最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分