@tencent-rtc/mcp@1.8.9
Tencent Cloud MCP Server for SDK
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package sends undisclosed telemetry to a Tencent endpoint by default when its server starts, including a stable device identifier and SDK app ID. The endpoint matches the package publisher, so this supports a suspicious telemetry verdict rather than exfiltration.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
When the package’s server starts, index.js initializes ServerConfig.
Impact
Tencent receives a stable identifier and SDK app ID on server startup, without an apparent opt-out.
Mechanism
ServerConfig reports mcp_config to webim.tim.qq.com. Without a valid SDKAPPID, it uses a persisted identifier; its fallback incorporates host and username information.
AI rationale
The package sends undisclosed telemetry to a Tencent endpoint by default when its server starts, including a stable device identifier and SDK app ID. The endpoint matches the package publisher, so this supports a suspicious telemetry verdict rather than exfiltration.
Evidence
index.jsserver-config.jsutils/report-es-client.jsutils/get-device-identifier.js~/.mcp/identifier
Network endpoints1
webim.tim.qq.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Server startup initializes ServerConfig, which automatically reports an mcp_config event.
- The report sends the SDKAppID to webim.tim.qq.com over HTTPS.
- When SDKAPPID is absent, startup obtains a persistent device identifier, stored at ~/.mcp/identifier; the fallback identifier is derived from hostname, platform, architecture, and username.
Evidence against
- The package describes itself as Tencent Cloud’s MCP server, and the report endpoint is a Tencent host.
- The manifest has no lifecycle scripts; reporting occurs when the server starts.
- The added knowledge/chunker.js code performs Markdown chunking and offset calculations.
Behavioral surface
CryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts registry_only=start
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgknowledge/chunker.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @tencent-rtc/mcp@1.7.8
matchedIdentity = npm:QHRlbmNlbnQtcnRjL21jcA:1.7.8
similarity = 0.480
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
knowledge/chunker.jsView on unpkgindex.jsView file
9
Findings
1 Critical1 High7 Medium3 Low
CriticalManifest Confusionpackage.json
HighPrevious Version Dangerous Deltaknowledge/chunker.js
MediumNetwork
MediumEnvironment Vars
MediumAi Review Evidenceindex.js
MediumAi Review Evidenceserver-config.js
MediumAi Review Evidenceutils/report-es-client.js
MediumAi Review Evidenceutils/get-device-identifier.js
MediumAi Review Evidenceutils/get-device-identifier.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @tencent-rtc/mcp@1.8.9.
See all versions of @tencent-rtc/mcp for other recorded verdicts.
- Review the evidence and your use of @tencent-rtc/mcp@1.8.9 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.