WeChat MCP Server

The materials explicitly state that no keys or environment variables are required, and there is no indication of API keys, tokens, or external account credentials. Still, the target data itself is WeChat chat history, so even without requesting new secrets, the tool would handle sensitive information if run in a locally logged-in or decrypted environment.

The materials list no remote endpoint host, and the README does not declare any cloud API, telemetry, or upload destination. Based on the available facts, there is no explicit user-data egress path; however, the lack of README detail means undisclosed network behavior cannot be further validated from documentation alone.

The objective checks indicate executes-code capability, meaning it runs code/processes on the local machine. That is a normal property for an MCP tool, but it still warrants running in a controlled environment and verifying that its actual system interactions are limited to the stated WeChat local database access use case.

The description says it can read encrypted WeChat chat history from a local database, search messages, and view sessions and contacts, which implies access to highly sensitive local personal data. For its stated purpose, this kind of local data access is inherent to the tool, and no explicit overbroad permission request is described, but the privacy sensitivity is high.

A positive factor is that the project is open source and theoretically auditable; however, it comes from a third-party registry, has 0 GitHub stars, unknown maintenance status, and essentially no README, which reduces verifiability and maturity. There is not enough concrete evidence to rate it as high risk, but supply-chain trust remains limited and the source code and dependencies should be reviewed before installation.