@tencent-rtc/mcp@1.6.0-beta.1
Tencent Cloud MCP Server for SDK
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection shows an MCP server for Tencent RTC documentation and test credential generation, with package-aligned telemetry but no lifecycle hooks, stealth persistence, arbitrary code execution, destructive behavior, or credential exfiltration. The env SECRETKEY is used locally to generate a requested UserSig and is not sent in the inspected reporting payloads.
Decision evidence
public snapshot- server-config.js reads SDKAPPID/SECRETKEY env at runtime; SDKAPPID is reported if set
- utils/report-cls-client.js can POST prompts/answers/feedback to Tencent CLS during MCP tool use
- utils/get-device-identifier.js creates/reads ~/.mcp/identifier for telemetry correlation
- package.json has no lifecycle scripts; bin/main is index.js only
- index.js starts an MCP stdio server; no install-time or import-time project mutation found
- No child_process, eval/vm/Function, dynamic require, native binary, or remote payload loading found in JS sources
- Network calls are hardcoded Tencent-aligned telemetry endpoints, not arbitrary C2
- get_usersig is explicit user-invoked functionality; it uses SECRETKEY locally and reports userID/SDKAppID, not secretKey/userSig
- Knowledge search reads bundled resource files and returns documentation fragments
Source & flagged code
3 flaggedTarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgHardcoded password in resource/knowledge/roomkit/core-sdk/ios/schedule-room.md
resource/knowledge/roomkit/core-sdk/ios/schedule-room.mdView on unpkg · L60Findings
Affected versions and remediation
This report applies to @tencent-rtc/mcp@1.6.0-beta.1.
See all versions of @tencent-rtc/mcp for other recorded verdicts.
- Review the evidence and your use of @tencent-rtc/mcp@1.6.0-beta.1 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.