summary-always
A server that summarizes and records conversation key points, supporting adding summaries and viewing history.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
wsd1
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
add_summary添加对话总结到记录中。 当用户说"总结记录一下"时，使用此工具记录当前对话的有价值信息。 使用场景： * 记录重要的用户要求 * 标记用户认可的有用信息 * 跟踪项目进展和决策 重点要求： 总结内容需要清晰简练，遵循一句话说明白的原则。要聚焦在用户提出的内容上。 关键词的选择要要宁缺毋滥（不要超过5个）。要突出特殊性独立性关联性，比如项目名称、关键技术、人名等，不要太笼统的名词。 参数说明： ♦ content: 需要总结的对话内容。例如：'用户需要创建一个MCP服务器来记录对话总结。' ♦ keywords: 可选的关键词列表，用于标记总结的主题。
show_summaries显示之前记录的总结。 当用户说"看一下之前的总结"时，使用此工具查看所有历史总结记录。 参数说明： ♦ filterKeywords: 可选的关键词过滤，只显示包含指定关键词的总结 ♦ limit: 可选的数量限制，显示最新的N条总结 输出格式： 每行显示一条总结，格式为： YYYYMMDD #关键词1 #关键词2 总结内容... 使用场景： * 回顾之前的对话要点 * 查找特定主题的总结 * 查看最近的记录 * 了解总结统计信息
save_summaries保存当前所有总结到文件。 当用户说"保存总结"时，使用此工具将当前内存中的所有总结记录保存到文件中。 保存方式： 1. 打开 当前时间戳YYYYMMDD.md 文件 2. 将当前的所有记录summaries数组内的内容，依序添加在文件后续 3. 只记录字符串，不用记录json格式
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
SUMMARY_STORAGE_PATHTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
3/3 tools missing one or more hints — add_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); show_summaries (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); save_summaries (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@0.6.1 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/wsd1/mcp-server-summary-always)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check