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/DevinChen2014/wechat-channels-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/devinchen2014/wechat-channels-mcp/socialdatax-wechat)<a href="https://agentmods.dev/mcp/devinchen2014/wechat-channels-mcp/socialdatax-wechat"><img src="https://agentmods.dev/badge/mcp/devinchen2014/wechat-channels-mcp/socialdatax-wechat/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/devinchen2014/wechat-channels-mcp/socialdatax-wechat"><img src="https://agentmods.dev/badge/mcp/devinchen2014/wechat-channels-mcp/socialdatax-wechat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
socialdatax-wechat 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 8d 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
{
"socialdatax-wechat": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.socialdatax.com/wechat/mcp",
"--header",
"Authorization: Bearer <SOCIALDATAX_API_KEY>"
]
}
}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.
- 8d ago First seen · 12 lines scan A c1969e5dcb8f
socialdatax-wechat is an MCP server published in the GitHub repository DevinChen2014/wechat-channels-mcp (0 stars, last pushed 13d 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
socialdatax-weibo
MCP server "socialdatax-weibo", hosted remotely at mcp.socialdatax.com, as configured in DevinChen2014/weibo-mcp.
socialdatax-kuaishou
MCP server "socialdatax-kuaishou", hosted remotely at mcp.socialdatax.com, as configured in DevinChen2014/kuaishou-mcp.
socialdatax-douyin
MCP server "socialdatax-douyin", hosted remotely at mcp.socialdatax.com, as configured in DevinChen2014/douyin-mcp. Needs 1 environment variable to run.
socialdatax-xhs
MCP server "socialdatax-xhs", hosted remotely at mcp.socialdatax.com, as configured in DevinChen2014/xiaohongshu-xhs-rednote-mcp. Needs 1 environment variable to run.
socialdatax-instagram
MCP server "socialdatax-instagram", hosted remotely at mcp.socialdatax.com, as configured in DevinChen2014/instagram-mcp.
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.