小红书 MCP 服务

小红书（XHS/RED）自动化助手。完整的小红书操作能力，包含 MCP 服务端。 当用户提到小红书、红书、XHS、RED、发笔记、搜笔记、小红书运营等任何与小红书相关的操作时使用此技能。

This skill is functionally consistent with a Xiaohongshu automation tool, but it ships with data/cookies.json that contains multiple session tokens (access-token, id_token, web_session, etc.). Treat that as a high-risk secret: do not install or run this skill without first removing or replacing data/cookies.json with your own credentials obtained via an explicit login. Steps to reduce risk: - Inspect and delete data/cookies.json before running. If you want to use your account, run npm run login and perform the QR login flow — do not rely on the bundled cookies. - Run the service on localhost only: set XHS_HOST=127.0.0.1 before starting to avoid binding to all interfaces (XHS_HOST=127.0.0.1 npm start). - If you must run on a networked host, ensure firewall rules restrict access to port 18060 and verify who controls the bundled cookies (they may be someone else’s account). - Be aware npm install will download puppeteer and Chromium (large binary). Examine package.json dependencies and the code paths (browser.js, xhs-tools.js) for any network destinations you do not expect. If you cannot confirm the origin/owner of the included cookies.json, treat this package as untrusted and prefer obtaining the tool from a known upstream source or reinitializing authentication yourself. If you want, I can list the sensitive cookie names found and show exactly where the code auto-loads them.

Type: OpenClaw Skill Name: skill-xiaohongshu Version: 1.1.0 The skill bundle is classified as suspicious primarily due to the inclusion of a pre-populated 'data/cookies.json' file containing active session tokens and user IDs for a specific XiaoHongShu account, which is highly unusual and poses a security risk. Additionally, 'scripts/browser.js' initializes Puppeteer with high-risk security flags like '--disable-web-security' and '--disable-features=IsolateOrigins', while 'scripts/ensure-service.js' uses 'exec' to run shell commands for process management. While these appear intended for browser automation and service control, the presence of hardcoded credentials and broad permissions warrants caution.