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/jiawei686/wechat-dev-mcpWrote 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/jiawei686/wechat-dev-mcp/wechat-devtools)<a href="https://agentmods.dev/mcp/jiawei686/wechat-dev-mcp/wechat-devtools"><img src="https://agentmods.dev/badge/mcp/jiawei686/wechat-dev-mcp/wechat-devtools/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/jiawei686/wechat-dev-mcp/wechat-devtools"><img src="https://agentmods.dev/badge/mcp/jiawei686/wechat-dev-mcp/wechat-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wechat-devtools 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 1mo 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-devtools": {
"command": "npx",
"args": [
"-y",
"wechat-dev-mcp"
]
}
}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.
- 1mo ago First seen · 9 lines scan A a268283d1210
wechat-devtools is an MCP server published in the GitHub repository jiawei686/wechat-dev-mcp (18 stars, last pushed 1mo 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-30.
Other mcp servers, from other repositories
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
prodlint
Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance. Runs locally from the prodlint npm package.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Launched with sqry-mcp --no-daemon. Needs 1 environment variable to run.
errorlens
Structured error recovery for MCP agents. Runs locally from the mcp-errorlens npm package.
mcp-registry-finder
MCP server "mcp-registry-finder" as configured in bharat3645/mcp-registry-finder. Runs locally from the mcp-registry-finder npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.