What Brandon Thinks Chat MCP
# What Brandon Thinks Chat MCP
Privacy-aware, deterministic, read-only MCP tools and an OpenClaw Skill for chat-analysis briefs, aggregate interaction signals, evidence-aware claim audits, and canonical What Brandon Thinks resource discovery.
This project does not upload transcripts, call an AI provider, access accounts, purchase reports, diagnose people, or prove private intent. What Brandon Thinks is independent and is not affiliated with WhatsApp, Meta, Apple, or iMessage.
## Install
```bash
npx -y github:gpt-img-2/whatbrandonthinks-chat-mcp
```
## Tools
- `build_chat_analysis_brief`
- `score_interaction_signals`
- `audit_chat_claim`
- `get_what_brandon_thinks_resources`
## OpenClaw
```bash
openclaw mcp add what-brandon-thinks \
--command npx \
--arg -y \
--arg github:gpt-img-2/whatbrandonthinks-chat-mcp
```
The Skill source is in [`openclaw/what-brandon-thinks-chat-analyst`](openclaw/what-brandon-thinks-chat-analyst/SKILL.md).
## Development
```bash
pnpm install
pnpm validate
```
Canonical product resources: [whatbrandonthinks.org/llms.txt](https://whatbrandonthinks.org/llms.txt)
TDQS
Scored across 4 tools
Each tool targets a distinct action: resource retrieval, brief construction, signal scoring, and claim auditing. However, build_chat_analysis_brief and audit_chat_claim both involve evidence and gap assessment, which could cause slight confusion in deciding between planning and validation.
All tools use snake_case with a verb-first pattern (get_, build_, score_, audit_). The longer noun phrase in get_what_brandon_thinks_resources is the only variation, but it remains consistent with the overall convention.
Four tools is well-scoped for this specialized chat-analysis workflow. Each tool covers a distinct step without redundancy, fitting comfortably within the ideal 3-15 range.
The tool set covers the full analytical lifecycle: retrieving reference resources, structuring a privacy-preserving brief, calculating interaction signals, and auditing a proposed interpretation. No obvious gaps exist for the stated privacy-focused domain.