xiaohongshu-mcp MCP Server Security Report
MCP for xiaohongshu.com
Run it securely
Host xpzouying/xiaohongshu-mcp in a governed environment — SSO in front, every tool call attributed and audited.
Are you the maintainer?
Verify with GitHub to get alerted whenever xpzouying/xiaohongshu-mcp changes score — and claim the badge for your README.
Claim this serverThe short answer
- Is xiaohongshu-mcp safe to use?
- xiaohongshu-mcp scores 90/100 (grade A) on the Canopii Trust Index — strong posture. It passes 13 of the 20 security controls that apply to it, with no confirmed security failures.
- How reliable is the security score for xiaohongshu-mcp?
- We could evaluate 81% of the controls that apply to xiaohongshu-mcp. Scores are deterministic — the same source always produces the same score — and a partially-scannable server cannot present a high one, because confidence caps the result. The scanner is open source, so this score can be reproduced independently.
- How was xiaohongshu-mcp scored?
- Its published source was scanned against a fixed catalog of weighted security controls covering code safety, committed secrets, dependency vulnerabilities, tool-description integrity, authentication and transport, and maintenance. A confirmed flaw caps the score outright regardless of what else passes. The full rubric is published.
Security controlslatest scored version vmain@98f84ad
Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.
Security controlslatest scored version vmain@98f84ad
Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.
Model–MCP Runtime Guardrails
- Not checkedIndirect Prompt Injection (IPI) Defensesguardno tools extracted
Tool/prompt/resource text is free of hidden instructions that could hijack the agent.
- Not checkedStrict JSON Schema Enforcementno tool schemas found
Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.
- Not checkedUser-in-the-Loop / Approval Scopeguardno tools extracted
No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.
- N/ATool Definition Integrityguardno prior version to diff
Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.
Application Security Checks
- WarnNo SSRF sinksguard3 occurrences
Fetching tool-supplied URLs can pivot into internal networks and metadata services.
skills/post-to-xhs/scripts/cdp_publish.py:128skills/post-to-xhs/scripts/chrome_launcher.py:166skills/post-to-xhs/scripts/image_downloader.py:77Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.
- WarnNo known-vulnerable dependencies10 of 83 runtime deps vulnerable; worst critical
Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.
github.com/modelcontextprotocol/[email protected] — GHSA-89xv-2j6f-qhc8github.com/modelcontextprotocol/[email protected] — GHSA-q382-vc8q-7jhjgithub.com/modelcontextprotocol/[email protected] — GO-2026-4770github.com/modelcontextprotocol/[email protected] — GO-2026-4773Fix: Upgrade the flagged dependencies past their fixed versions.
- WarnHas a security policyno security policy
A SECURITY.md gives a private path to report vulnerabilities.
Fix: Add SECURITY.md with a disclosure contact and process.
- PassNo command-injection sinksguardno sinks found
Untrusted tool input reaching a shell yields remote code execution.
- PassNo dynamic code executionguardno sinks found
eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.
- PassNo path traversalguardno sinks found
Naive path checks let tools read/write outside intended directories (EscapeRoute-class).
- PassNo unsafe deserializationguardno sinks found
pickle/yaml.load/etc. on untrusted data can execute code.
- PassNo committed secretsguardno secrets found
Hardcoded keys/tokens in published source are live credentials an attacker can use.
- PassCredentials sourced from environmentreads credentials from environment
Reading secrets from env/secret stores avoids hardcoding them.
- PassDependencies pinned (lockfile)lockfile present
A lockfile makes installs reproducible and resistant to silent dependency swaps.
- PassActively maintainedrecent commits
Unmaintained servers don't receive security fixes.
- PassRepository not archivedguardactive
Archived repositories will never be patched.
- PassDeclares a licenseApache-2.0
A clear license is required for legal enterprise use.
- PassAdoption & popularityestablished adoption
A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.
- Not checkedSigned releasesnot evaluated
Signed releases let consumers verify artifacts weren't tampered with.
- N/ANo install/post-install scriptsguardno published package
install hooks run arbitrary code on every consumer at install time.
- N/APackage name not typosquattingguardno published package
Names mimicking popular packages are a common malware delivery vector.
- N/APublished with provenanceno published package
Build provenance attests the artifact was built from the claimed source by CI.
- N/AEstablished maintainerno published package
Brand-new / single anonymous maintainers raise takeover and malware risk.
Transport & Trust Model
- PassExecution Sandboxingcontainerized
A container/sandbox image limits blast radius; a server that runs natively has full host access.
- PassNetwork Exposureno bind-all detected
Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.
- N/ATransport Encryption (TLS)guardno remote endpoints
Plaintext HTTP exposes traffic and bearer tokens to interception.
- N/AIAM / Authentication Scopingno remote endpoints
OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.
- N/ALive Endpoint Reachablenot dynamically scanned
A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.
- N/AAuthentication Enforced (live)not dynamically scanned
If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.
Embed this score
Add the live badge to your README — it updates automatically on every rescan.
[](https://index.canopii.dev/server/xpzouying/xiaohongshu-mcp)<a href="https://index.canopii.dev/server/xpzouying/xiaohongshu-mcp"><img src="https://index.canopii.dev/api/badge/xpzouying/xiaohongshu-mcp" alt="Canopii Trust Score" /></a>Versions
| Version | Score | Status | Published |
|---|---|---|---|
| vmain@98f84adlatest | 90A | scored | 8/3/2026 |
Wondering how this compares? The MCP Security Index tracks grade distribution, committed secrets, and missing authentication across the whole ecosystem, refreshed monthly.