Mcp Client

MCP Client skill connects and manages MCP servers via stdio or SSE, supporting tool calls, resource reads, prompts, permission control, auditing, and error h...

Do not install or run this skill without cleaning the bundled configuration and reviewing behavior. Specific actions to take before use: - Inspect src/mcp-config.json and remove or replace the hardcoded GITHUB_TOKEN. If that token is real, consider it leaked and rotate it immediately. - Replace absolute/local paths (e.g., C:\Users\99236\.openclaw\workspace) with safe workspace-relative paths or placeholders. - Avoid running the test scripts or the CLI in auto-approve mode until you understand the approvals: the CLI (when run directly) sets autoApprove: true and requireApproval: false and auto-approves '*', which will allow all tool/resource calls without prompts. - Understand that npm / npx will fetch and execute packages (e.g., @modelcontextprotocol/server-*). Run in an isolated environment (container or VM) if you need to test. - If you need GitHub access, configure tokens via environment variables at runtime (not commit them) and verify the code reads process.env rather than a baked-in value. - If you already ran this package with the included token, rotate the token and check GitHub logs for suspicious activity. - If you intend to use this as an OpenClaw skill, consider forking and removing sensitive defaults, disable auto-approve by default, and re-run security review before deployment.

Type: OpenClaw Skill Name: yuyonghao-mcp-client Version: 0.1.1 The bundle contains a hardcoded GitHub Personal Access Token (PAT) in 'src/mcp-config.json' (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), which is a critical security risk. The skill is designed to execute arbitrary commands via 'npx' to launch MCP servers as defined in the configuration, presenting a high risk of Remote Code Execution (RCE) if the configuration is modified. Additionally, multiple files (e.g., 'src/mcp-config.json' and 'test/mcp-servers.test.js') contain hardcoded absolute file paths specific to a developer's local environment, indicating poor security hygiene. While 'src/secure-client.js' implements some defensive features like sensitive path filtering and audit logging, the exposed credential and broad execution capabilities warrant a suspicious classification.