xhs-bailian-mcp-server_jxh

MCP server package intended to expose tools for an “xhs bailian” (XHS/小红书) workflow to agents via the Model Context Protocol.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Automation mcp ai-agents integration xhs social-media tooling
⚙ Agent Friendliness
33
/ 100
Can an agent use this?
🔒 Security
32
/ 100
Is it safe for agents?
⚡ Reliability
15
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
30
Error Messages
0
Auth Simplicity
40
Rate Limits
20

🔒 Security

TLS Enforcement
50
Auth Strength
25
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
30

No concrete security configuration details (TLS enforcement, auth scheme, scope model, secret handling) were provided in the supplied content. Scores are based on absence of evidence rather than verified implementation.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
0
Error Recovery
20
AF Security Reliability

Use Cases

  • • Connecting an LLM/agent to XHS-related actions (e.g., search, retrieval, or other platform operations) through MCP tools
  • • Building agent workflows that require programmatic access to XHS data/actions
  • • Rapid integration of XHS capabilities into MCP-compatible agent runtimes

Not For

  • • Production-grade deployments requiring verified, documented security/auth guarantees (insufficient repo data provided here)
  • • Use cases requiring a standard REST/GraphQL/SDK interface out of the box (none evidenced here)
  • • Compliance-sensitive environments without clear data handling and dependency/security documentation

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication details were provided in the supplied content. Auth/keys approach is unknown.

Pricing

Free tier: No
Requires CC: No

Pricing not provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Because no README/tool schema/details were provided here, tool names, parameters, and response shapes may be unclear; agents may need manual inspection of the repo to avoid wrong arguments.
  • ⚠ Without documented error codes/retry semantics, agents may not know when to retry vs. fail (e.g., rate limits, upstream errors).
  • ⚠ If the server performs non-idempotent actions, agents may repeat operations on retries unless explicit idempotency keys are supported.

Alternatives

Implement direct integrations to the underlying XHS API (if available) with your own MCP/REST wrapper Use a third-party XHS integration SDK/service (if you can verify security and docs) Create a generic MCP tool layer that calls your own backend for XHS operations

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for xhs-bailian-mcp-server_jxh.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
♥
Community Powered