xiaohongshu-mcp
MCP for xiaohongshu.com
Runssource: GitHubhomepageGoApache-2.0commit 332d196854a9
Go, Apache-2.0 licensed. The project labels itself: mcp, mcp server and xiaohongshu mcp.
xiaohongshu-mcp runs. An Argusic agent installed it in 5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The HTTP server starts on port 18060, the /health endpoint returns 200, the built-in Chromium browser launches via go-rod, and the /api/v1/feeds/list endpoint returns real feed data from xiaohongshu.com. All 10 Go test packages pass (0 failures). The browser extraction bug is fixed by using system tar instead of the Go xz library.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 90.7 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go ulikunitz/xz library truncates large xz archives — Chromium binary extracted as 35 MB (should be 482 MB), causing segfault18 minutes
- Go (1.24.0) not installed in container2 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... passed (10 packages); curl localhost:18060/health returned HTTP 200 with 'healthy'; curl localhost:18060/api/v1/feeds/list returned HTTP 200 with 33 real feeds from xiaohongshu.com
- Model tokens used
- 672,827
- Exact commit tested
- 332d196854a9
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
[GIN] 2026/09/22 - 19:34:03 | 500 | 25.178402611s | 127.0.0.1 | POST "/api/v1/feeds/searc… time="2026-09-22T19:34:03Z" level=info msg="服务器已优雅关闭" The app works. Let me kill any remaining processes and record results exec /bin/sh -lc 'kill $(pgrep -f "/tmp/app") 2>/dev/null sleep 1 echo "done"' in /work/repo exited 143 in 0ms: Here's my summary of everything I did and observed. tokens used 672,827 Here's my summary of everything I did and observed.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 5 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 mcp projects Argusic has installed and timed, xiaohongshu-mcp was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 3/3 | Runs | 100.00 | 0.10 | |
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.07 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.04 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xiaohongshu-mcp)Questions
- Does xiaohongshu-mcp run?
- Yes. xiaohongshu-mcp runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test xiaohongshu-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 332d196854a9. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test xiaohongshu-mcp?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does xiaohongshu-mcp take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does xiaohongshu-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xiaohongshu-mcp?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does xiaohongshu-mcp compare with the alternatives?
- Of the 4 mcp projects Argusic has installed and timed, xiaohongshu-mcp was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for xiaohongshu-mcp?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.