updated 2026-09-04 23:32 UTC

Xiaohongshu MCP

xpzouying/xiaohongshu-mcp

MCP for xiaohongshu.com

MCP Servers Go Grade C Listed Apache-2.0
57.0/100
Rank #545 of 1320
Compare Xiaohongshu MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-31 · 4d ago
Recent change
Rank +5

Is Xiaohongshu MCP safe? Xiaohongshu MCP scores 57.0/100 (Grade C), ranked #545 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.9/10; 94% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#254 Rust MCP Sdk — 57.2 (C) → #255 Agent360 Browser MCP — 57.2 (C) → #257 Localstack MCP Server — 56.9 (C) → #258 IvanMurzak Unity MCP — 56.8 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 26 spots (#519 → #545)
2026-09-03
Rank Moved
Rank dropped 90 spots (#429 → #519)
2026-09-02
Rank Moved
Rank dropped 17 spots (#412 → #429)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Xiaohongshu MCP View MCP Servers Report missing data
77.7
Activity sub-score · out of 100
#256
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 23:32 UTC · Repo last pushed 4 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
15.6k
Forks
2.3k
Last Push
2026-08-31
4 days ago
Commits (4 wk)
9?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
42
Rank Change
▼26
was #519

Analysis

HVTrust Dimensions vs MCP Servers

57.0 / 100 · 100.0% confidence

Xiaohongshu MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.6 / 25
in line with avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.7 / 20
1.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
10.1 / 20
3.8 above avg 6.3

Activity Inputs

77.7 / 100
StarsRepository reach
25.2 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
15.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.9 / 10
OpenSSF Scorecard · scanned Aug 26, 2026
Signed Commits
94%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 9
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Xiaohongshu MCP safe?

Xiaohongshu MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Xiaohongshu MCP publish package provenance?
No published build provenance is currently detected for Xiaohongshu MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Xiaohongshu MCP have an OpenSSF Scorecard?
Xiaohongshu MCP has an OpenSSF Scorecard score of 3.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Xiaohongshu MCP actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Xiaohongshu MCP use?
Xiaohongshu MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Xiaohongshu MCP's commits signed?
94% of the last 100 commits to Xiaohongshu MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Xiaohongshu MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Xiaohongshu MCP?

For maintainers

HVTrust scores Xiaohongshu MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 9Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 26 spots (#519 → #545)
2026-09-03
Rank Moved
Rank dropped 90 spots (#429 → #519)
2026-09-02
Rank Moved
Rank dropped 17 spots (#412 → #429)
2026-09-01
Rank Moved
Rank dropped 31 spots (#381 → #412)
2026-08-31
Rank Moved
Rank dropped 26 spots (#355 → #381)
2026-08-29
Rank Moved
Rank dropped 11 spots (#351 → #362)
2026-08-27
Rank Moved
Rank dropped 13 spots (#335 → #348)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.9/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 467 spots (#802 → #335)
2026-08-26
HVTrust Changed
HVTrust up 33.4pts (28.1 → 61.5)
2026-08-16
Rank Moved
Rank dropped 15 spots (#784 → #799)
2026-08-10
Newly Listed
First tracked at rank #782
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/xiaohongshu-mcp.svg)](https://hvtracker.net/agents/xiaohongshu-mcp)
HTML:
<a href="https://hvtracker.net/agents/xiaohongshu-mcp"><img src="https://hvtracker.net/badge/xiaohongshu-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON