Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/BENZEMA216/wechat-archive-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/benzema216/wechat-archive-harness/wechat-archive)<a href="https://agentmods.dev/mcp/benzema216/wechat-archive-harness/wechat-archive"><img src="https://agentmods.dev/badge/mcp/benzema216/wechat-archive-harness/wechat-archive/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/benzema216/wechat-archive-harness/wechat-archive"><img src="https://agentmods.dev/badge/mcp/benzema216/wechat-archive-harness/wechat-archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wechat-archive scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "wechat-archive": { "command": "uvx", "args": [ "wechat-archive" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 8 lines scan A 3a72c9439c52
wechat-archive is an MCP server published in the GitHub repository BENZEMA216/wechat-archive-harness (0 stars, last pushed 15d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
personal-model
Local-first macOS Runtime for screen-context memory, personal modeling, and MCP. Runs locally from the personal-model Python package.
ai-file-wall
MCP server "ai-file-wall" as configured in starcat-app/Starcat. Runs supports/ai-file-wall/integrations/cursor/mcp-server.mjs with node.
s-gw
MCP server "s-gw" as configured in sgateway/s-gw. Runs ./dist/mcp-server.js with node. Needs 2 environment variables to run.
trove-runtime
MCP server "trove-runtime" as configured in JNHFlow21/trove. Runs locally from the trove-runtime Python package.
call-copilot
Call Copilot — silently record meeting audio in the background, then transcribe locally to clean markdown. Runs locally from the call-copilot Python package.
myday
A private, local memory of what you did on your Mac — 10-minute Markdown records, searchable, and readable by your AI coding agent over MCP. Runs locally from the @abhitsian/myday npm package.