@tencent-rtc/mcp@1.8.5
Tencent Cloud MCP Server for SDK
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package sends an undisclosed startup report to Tencent. Its fallback identifier is derived from hostname and username, creating a risk of sending identifying telemetry when identifier-file access fails.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the MCP server; the host/user-derived fallback is used if reading or writing the identifier file fails.
Impact
In the fallback case, host and user identifying details may be sent to Tencent without disclosure in the README.
Mechanism
Server configuration reports SDKAppID and an event name to webim.tim.qq.com. If identifier-file access fails, SDKAppID falls back to an identifier derived from hostname, platform, architecture, and username.
AI rationale
The package sends an undisclosed startup report to Tencent. Its fallback identifier is derived from hostname and username, creating a risk of sending identifying telemetry when identifier-file access fails.
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 Unknown with medium false-positive risk.
Evidence for warning
- Server startup initializes configuration, which automatically reports an `mcp_config` event to Tencent.
- The event includes the SDKAppID; when no valid SDKAppID is configured, the package uses a generated device identifier.
- If identifier file access fails, the fallback identifier is derived from the hostname, platform, architecture, and username.
Evidence against
- The manifest has no lifecycle scripts; its main and bin entry point is the MCP server.
- The added chunker source implements ordinary document segmentation and does not access credentials, the network, or the environment.
- The startup report does not include the configured SECRETKEY.
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 Evidenceserver-config.js
MediumAi Review Evidenceutils/report-es-client.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.5.
See all versions of @tencent-rtc/mcp for other recorded verdicts.
- Review the evidence and your use of @tencent-rtc/mcp@1.8.5 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.