找客户 · Find Customers｜销售线索与评论区获客
NPM · PPXC-LEADS-MCP · SCANNED SEP 20
Find sales leads in Douyin, Xiaohongshu, and Kuaishou comments; installs its Skill with approval.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 63 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2312 tokens (~136/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 94% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the 找客户 · Find Customers｜销售线索与评论区获客 MCP server?
找客户 · Find Customers｜销售线索与评论区获客 runs locally as an npm package, launched with npx -y ppxc-leads-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ppxc-leads-mcp
claude mcp add yuanjian068yuan-ppxc-leads-mcp -- npx -y ppxc-leads-mcp
{
"mcpServers": {
"yuanjian068yuan-ppxc-leads-mcp": {
"command": "npx",
"args": [
"-y",
"ppxc-leads-mcp"
]
}
}
} {
"servers": {
"yuanjian068yuan-ppxc-leads-mcp": {
"command": "npx",
"args": [
"-y",
"ppxc-leads-mcp"
]
}
}
} codex mcp add yuanjian068yuan-ppxc-leads-mcp -- npx -y ppxc-leads-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yuanjian068yuan-ppxc-leads-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ppxc-leads-mcp"
],
"enabled": true
}
}
} openclaw mcp add yuanjian068yuan-ppxc-leads-mcp --command npx --arg -y --arg ppxc-leads-mcp
mcp_servers:
yuanjian068yuan-ppxc-leads-mcp:
command: "npx"
args: ["-y", "ppxc-leads-mcp"] {
"McpServers": {
"yuanjian068yuan-ppxc-leads-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ppxc-leads-mcp"
]
}
}
} assistant mcp add yuanjian068yuan-ppxc-leads-mcp -t stdio -c npx -a -y ppxc-leads-mcp
{
"mcpServers": {
"yuanjian068yuan-ppxc-leads-mcp": {
"command": "npx",
"args": [
"-y",
"ppxc-leads-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/ppxc-leads-mcp@0.1.28
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_video_comments ~310
分析单条抖音/小红书/快手内容链接的公开评论，生成客户线索和在线战报。
| Name | Type | Req | Description |
|---|---|---|---|
| commentMaxAgeDays | integer | – | 只分析最近 N 天的评论，支持 3、7。不传默认近 7 天；不会分析 7 天外的评论。 |
| maxComments | integer | – | 最多读多少条评论，默认 30。 |
| platform | string | – | 可选：douyin | xiaohongshu | kuaishou。不传则从链接自动识别。 |
| problemSolved | string | – | 未登录试用时可填：解决的痛点。 |
| productDescription | string | – | 未登录试用时填写：适合谁、解决什么问题、主要卖点。 |
| productId | string | – | 已登录用户的产品 id；试用扫描可不传。 |
| productName | string | – | 未登录试用时填写：用户卖的产品/服务名称。 |
| save | boolean | – | 是否落客户池，默认 false。只有用户明确要保存完整名单到客户池时才传 true。 |
| sellingPoints | array | – | 未登录试用时可填：卖点列表。 |
| targetPersona | string | – | 未登录试用时可填：目标人群。 |
| videoUrl | string | yes | 内容链接（抖音视频/小红书笔记/快手视频）或 ID。 |
No output schema declared.
No examples provided.
cancel_current_search_run ~84
取消当前正在运行的搜索任务，释放任务锁。
| Name | Type | Req | Description |
|---|---|---|---|
| batchId | string | – | 可选：要取消的 start_batch_search_run 返回的 batchId。 |
| reason | string | – | 取消原因，用于诊断和最终状态展示。 |
| runId | string | – | 可选：要取消的 start_search_run 返回的 runId。 |
No output schema declared.
No examples provided.
check_status_and_login ~62
检查 OPC 与平台登录状态；需要时弹出对应平台或 OPC 登录窗口。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | status=只查不弹窗；login_* 为显式登录。试用扫描前不要先调用 login_ppxc。 |
No output schema declared.
No examples provided.
export_diagnostics ~31
导出脱敏诊断信息，方便排查 MCP 安装、登录、搜索和运行问题。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_batch_search_run_status ~49
轮询批量关键词搜索任务状态，获取进度、战报链接和最终汇总。
| Name | Type | Req | Description |
|---|---|---|---|
| batchId | string | yes | start_batch_search_run 返回的 batchId。 |
No output schema declared.
No examples provided.
get_search_run_status ~47
轮询单次关键词搜索任务状态，获取进度、战报链接和客户线索。
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | start_search_run 返回的 runId。 |
No output schema declared.
No examples provided.
get_workflow_manifest ~28
读取后端最新找客户工作流、能力清单和 Skill 更新提示。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_products ~28
列出用户在 OPC 保存的产品，用于客户池、保存和复盘流程。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mark_lead_feedback ~116
记录用户对客户线索质量的反馈，用于后续优化。
| Name | Type | Req | Description |
|---|---|---|---|
| leadId | string | yes | 客户线索 id，来自 query_leads 或找客户结果。 |
| reason | string | – | 用户补充原因，最多会由后端截取保存。 |
| tag | string | yes | 用户判断：accurate=准；inaccurate=不准；too_broad=太泛；feels_like_buyer=像客户；feels_like_passerby=像路人。 |
No output schema declared.
No examples provided.
query_leads ~113
查询已保存的客户池线索，支持按产品、平台、关键词等条件回看。
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 只看最近 N 天入池的客户。 |
| keyword | string | – | 只看这个搜索词挖到的客户。 |
| limit | integer | – | 最多返回几条，默认 30。 |
| productId | string | – | 产品 id；不传则查当前账号全部产品。 |
| status | string | – | 按跟进状态过滤。 |
No output schema declared.
No examples provided.
review_followup_queue ~86
复盘客户池里的待跟进线索，生成跟进建议。
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 只看最近 N 天入池客户，默认 7 天。 |
| limit | integer | – | 每组最多返回几条样例，默认 5。 |
| productId | string | – | 产品 id；不传则查当前账号全部产品。 |
No output schema declared.
No examples provided.
search_keyword_for_leads ~413
LEGACY 同步关键词搜索入口；长任务优先使用 start_search_run 或 start_batch_search_run。
| Name | Type | Req | Description |
|---|---|---|---|
| allowLegacySync | boolean | – | 只有宿主缺少 async/batch 工具且用户明确要求极小同步扫描时才可传 true。 |
| commentMaxAgeDays | integer | – | 只分析最近 N 天的评论，支持 3、7。不传默认近 7 天；不会分析 7 天外的评论。 |
| hostProfile | string | – | 宿主名称；WorkBuddy/压力测试场景传 workbuddy 后本 legacy 工具会被拒绝。 |
| keywords | array | yes | 搜索词列表，最多 10 个。 |
| maxComments | integer | – | 每条内容最多读多少条评论。 |
| maxVideosPerKeyword | integer | – | 每个关键词最多读几条内容，默认 1。 |
| platform | string | yes | 在哪个平台搜：douyin | xiaohongshu | kuaishou。 |
| pressureTest | boolean | – | 是否压力测试；true 时禁止使用本 legacy 同步入口。 |
| problemSolved | string | – | 未登录试用时可填：解决的痛点。 |
| productDescription | string | – | 未登录试用时填写：适合谁、解决什么问题、主要卖点。 |
| productId | string | – | 已登录用户的产品 id；试用扫描可不传。 |
| productName | string | – | 未登录试用时填写：用户卖的产品/服务名称。 |
| save | boolean | – | 是否落客户池，默认 false。试用扫描不要传 true。 |
| sellingPoints | array | – | 未登录试用时可填：卖点列表。 |
| targetPersona | string | – | 未登录试用时可填：目标人群。 |
| useCase | string | – | 调用场景；batch、pressure_test、long_task、async_workflow 会被拒绝。 |
No output schema declared.
No examples provided.
setup_companion_skill ~173
检查或安装与本 MCP 配套的找客户 Agent Skill。首次使用找客户前先调用 action=status（只读）；如果返回 missing/outdated，必须先向用户说明目标目录并取得明确同意，之后才可调用 action=install、指定当前宿主 target 并传 confirm=true。严禁未经用户同意安装或更新 Skill。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | status=只读检查；install=在用户明确同意后安装或更新。默认 status。 |
| confirm | boolean | – | 只有用户已经明确同意写入显示的 Skill 目录时才传 true。status 不需要。 |
| target | string | – | 当前智能体宿主。自动检测不唯一时必须明确指定，不能同时安装到多个宿主。 |
No output schema declared.
No examples provided.
start_batch_search_run ~282
提交批量关键词搜索计划，由 MCP 内部串行执行，适合 WorkBuddy 和压力测试。
| Name | Type | Req | Description |
|---|---|---|---|
| commentMaxAgeDays | integer | – | 只分析最近 N 天的评论，支持 3、7。不传默认近 7 天；不会分析 7 天外的评论。 |
| maxComments | integer | – | 每条内容最多读多少条评论。 |
| plan | array | yes | 批量计划，MCP 会按顺序串行执行。 |
| platform | string | yes | 在哪个平台搜：douyin | xiaohongshu | kuaishou。 |
| problemSolved | string | – | 未登录试用时可填：解决的痛点。 |
| productDescription | string | – | 未登录试用时填写：适合谁、解决什么问题、主要卖点。 |
| productId | string | – | 已登录用户的产品 id；试用扫描可不传。 |
| productName | string | – | 未登录试用时填写：用户卖的产品/服务名称。 |
| save | boolean | – | 是否落客户池，默认 false。试用扫描不要传 true。 |
| sellingPoints | array | – | 未登录试用时可填：卖点列表。 |
| targetPersona | string | – | 未登录试用时可填：目标人群。 |
No output schema declared.
No examples provided.
start_search_run ~372
启动单批关键词搜索任务，返回 runId 后用 get_search_run_status 轮询。
| Name | Type | Req | Description |
|---|---|---|---|
| commentMaxAgeDays | integer | – | 只分析最近 N 天的评论，支持 3、7。不传默认近 7 天；不会分析 7 天外的评论。 |
| committeeKeywordLimit | integer | – | 从后端想词委员会最多取几个词，默认 10。 |
| keywords | array | – | 搜索词列表；最多 10 个。 |
| maxComments | integer | – | 每条内容最多读多少条评论。 |
| maxVideosPerKeyword | integer | – | 每个关键词最多读几条内容；快手建议先 1。 |
| platform | string | yes | 在哪个平台搜：douyin | xiaohongshu | kuaishou。 |
| problemSolved | string | – | 未登录试用时可填：解决的痛点。 |
| productDescription | string | – | 未登录试用时填写：适合谁、解决什么问题、主要卖点。 |
| productId | string | – | 已登录用户的产品 id；试用扫描可不传。 |
| productName | string | – | 未登录试用时填写：用户卖的产品/服务名称。 |
| regenerateCommitteeKeywords | boolean | – | 是否强制触发后端重新想词；只有用户明确要换一批词时传 true。 |
| save | boolean | – | 是否落客户池，默认 false。试用扫描不要传 true。 |
| sellingPoints | array | – | 未登录试用时可填：卖点列表。 |
| targetPersona | string | – | 未登录试用时可填：目标人群。 |
| useCommitteeKeywords | boolean | – | 是否强制使用后端想词委员会。 |
No output schema declared.
No examples provided.
suggest_search_keywords ~66
根据产品信息生成或预览搜索关键词。
| Name | Type | Req | Description |
|---|---|---|---|
| productId | string | yes | 产品 id，用于读取后端想词委员会。 |
| regenerate | boolean | – | 强制重新生成一轮（会消耗电力）。默认 false：直接读现成词单。 |
No output schema declared.
No examples provided.
update_lead_status ~52
更新客户线索跟进状态。
| Name | Type | Req | Description |
|---|---|---|---|
| leadId | string | yes | 客户线索 id，来自 query_leads 或找客户结果。 |
| status | string | yes | 新的跟进状态。 |
No output schema declared.
No examples provided.
What is the 找客户 · Find Customers｜销售线索与评论区获客 MCP server?
找客户 · Find Customers｜销售线索与评论区获客 is an MCP server listed in the public MCP registry as io.github.yuanjian068yuan/ppxc-leads-mcp. Find sales leads in Douyin, Xiaohongshu, and Kuaishou comments; installs its Skill with approval. This page covers its npm package (ppxc-leads-mcp).
Is the 找客户 · Find Customers｜销售线索与评论区获客 MCP server safe to use?
找客户 · Find Customers｜销售线索与评论区获客 scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the 找客户 · Find Customers｜销售线索与评论区获客 MCP server expose?
找客户 · Find Customers｜销售线索与评论区获客 exposes 17 tools: setup_companion_skill, analyze_video_comments, cancel_current_search_run, check_status_and_login, export_diagnostics, and 12 more. Their descriptions and schemas cost roughly 2,312 tokens of context every time the server is loaded.
Is the 找客户 · Find Customers｜销售线索与评论区获客 MCP server still maintained?
找客户 · Find Customers｜销售线索与评论区获客 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the 找客户 · Find Customers｜销售线索与评论区获客 MCP server under?
找客户 · Find Customers｜销售线索与评论区获客 declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.