Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldxpzouying-xiaohongshu-mcpMCP100 Selectedio.github.atilaahmettaner/tradingview-mcpMCP100 Selected
Task fit
Best for
  • Searching, reading, and carrying out the publisher-documented Xiaohongshu interactions through an AI assistant
  • Generating chart-based technical indicators and summaries for symbols supported by the project's TradingView integration
Not ideal for
  • Bulk collection, unattended account automation, or analytics that require an official supported platform API
  • Auditable investment decisions, guaranteed real-time quotes, or order execution
Avoid when
  • The intended use conflicts with platform rules, privacy obligations, or your account-risk tolerance
  • The output would be treated as financial advice or used without independently checking data freshness and symbol coverage
Provenance
Provenance details

Community implementation

github:xpzouying · Publisher source ↗

Community implementation

io.github.atilaahmettaner · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 13, 2026

Package: Not documented

Repo: Aug 7, 2026

Package: Not documented

Popularity evidence
GitHub stars

15,255

GitHub stars · checked 2026-08-14T18:46:26.000Z

3,960

GitHub stars · checked 2026-08-14T18:46:26.000Z

External adoption evidence
  • github: repository stars: 15,255Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • github: repository stars: 3,960Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude CodeStreamable HTTP
Claude DesktopStreamable HTTP
CodexStreamable HTTP
VS CodeStreamable HTTP
CursorStreamable HTTP
OpenCodeStreamable HTTP
Claude CodeLocal stdio
Claude DesktopLocal stdio
CodexLocal stdio
VS CodeLocal stdio
CursorLocal stdio
OpenCodeLocal stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationManual browser or QR login and saved session cookies are documented; selected actions require an xsec_token. No formal MCP client authentication is documented.No TradingView account or API key is required. MARKETAUX_API_TOKEN is optional; hosted-service account and authentication details are not fully documented.
CostNo MCP project or service price is documented. Platform, client, model, proxy, or hosting costs can still apply.Self-hosting is MIT-licensed. The README lists hosted plans at $9 or $29 per month with a three-day trial, and a Marketaux free key limited to 100 requests per day.
PermissionsCan log in, publish image or video content, search and read feeds and profiles, read and post comments and replies, like, unlike, favorite, unfavorite, schedule content, and bind products. It stores local session cookies and uses local media paths.Accesses public market data for quotes, technical analysis, screeners, backtests, news, and sentiment. The publisher says it does not execute trades or manage money.
Data handlingUses local browser session cookies, local image and video paths, and Xiaohongshu feed, profile, and comment data; requested content is posted to Xiaohongshu. Docker examples persist cookies and images in mounted directories. Encryption and telemetry are not documented.Market-data requests and results are processed by the self-hosted or hosted server. Optional news and sentiment calls use Marketaux when MARKETAUX_API_TOKEN is configured; provider retention is not documented.
Limitations
Tradeoffs
  • It exposes useful platform actions, but relies on authenticated session state and automation can trigger account, privacy, or platform-policy consequences.
  • Natural-language analysis is convenient, while upstream data availability and indicator interpretation can still be incomplete or wrong.
Risk contextAccount-impacting automation can publish, comment, like, and favorite. Protect the locally stored credential cookies, isolate the account, review every write action, and account for the publisher's warnings about session conflicts, expiry, and account prompts.Outputs are informational, not financial advice, and can be delayed, inaccurate, or incomplete. Do not treat signals or backtests as recommendations; verify data and third-party terms.
Evidence date
Editorial review2026-08-112026-08-11
Candidate evidence2026-08-14T18:46:26.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →