ChatsumSAFE
Query and Summarize your chat messages.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
This MCP Server is used to summarize your chat messages.
中文说明
Before you start move to chatbot directory, follow the README to setup the chat database. start chatbot to save your chat messages.
Features
Resources
Tools
query_chat_messages- Query chat messages- Query chat messages with given parameters
- Summarize chat messages based on the query prompt
Prompts
Development
- Set up environment variables:
create .env file in the root directory, and set your chat database path.
CHAT_DB_PATH=path-to/chatbot/data/chat.db
- Install dependencies:
pnpm install
Build the server:
pnpm build
For development with auto-rebuild:
pnpm watch
Installation
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-server-chatsum": {
"command": "path-to/bin/node",
"args": ["path-to/mcp-server-chatsum/build/index.js"],
"env": {
"CHAT_DB_PATH": "path-to/mcp-server-chatsum/chatbot/data/chat.db"
}
}
}
}Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
pnpm inspector
The Inspector will provide a URL to access debugging tools in your browser.
Community
About the author
fde53c21f56aOBSERVED · 2026-09-26Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-server-chatsum -- npx -y [email protected]
{
"mcpServers": {
"mcp-server-chatsum": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (1)
1 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
query_chat_messages | read | query chat messages with given parameters |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (4)
dotenv, qrcode-terminal, sqlite3, ts-node, wechaty, wechaty-puppet, wechaty-puppet-padlocal, @types/qrcode-terminal
dotenv, sqlite3, @types/node, typescript
preview.png
Gates applied: no_behavioural_pass, no_license.
fde53c21f56afull audit observations/trust-audit/mcp-server/chatmcp__chatsum.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-09-26 | fde53c21f56a | SAFE | B | 89 | first audit |
Questions
What is the Chatsum MCP server?
Query and Summarize your chat messages.
What tools does Chatsum expose?
1 in total: 1 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Chatsum safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Chatsum need?
No credential environment variables were found in its source, so it appears to need none.
How does Chatsum run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as mcp-server-chatsum at 0.1.0.
How current is this page?
The grade is for one exact copy of the source (fde53c21f56a), read on 2026-09-26. The repository is watched and re-audited when it changes.