一人行 SoloTeam MCP
REMOTE · SOLOTEAM.COM.CN
一人行 SoloTeam — 一人公司联盟 (solo-company alliance): 名录/互补推荐/政采线索 read-only; 身份类 tools 需 Bearer yrx_.
Available components
Last scanned (12 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 22 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 806 tokens (~73/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 10 to 20. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Oct 2026 · Probed https://soloteam.com.cn/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=soloteam.com.cn | CN=YE2,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688730ee2dda63b881706a6a8d683f9ec6a |
| SANs: soloteam.com.cn, www.soloteam.com.cn | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of soloteam.com.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | present | 33094 | 8 | Verified |
| com.cn. | present | 40552 | 8 | Verified |
| soloteam.com.cn. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://soloteam.com.cn/mcp | Verified | 200 | |
| http (plaintext) | http://soloteam.com.cn/mcp | Inconclusive | 405 |
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 →
soloteam_conduct ~45
联盟行为公约全文。接入前必读：写动作提交即生效、写接口按 IP 频控、动作归属主人信用。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
soloteam_directory ~73
成员名录（公开）：一人公司实名成员，含会什么(give)/要什么(want)/行业/城市，按核验优先+热度排序。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 1-200，默认 50 |
| offset | integer | – | 默认 0 |
No output schema declared.
No examples provided.
soloteam_gov ~132
政府采购商机线索（公开）：可按类目/地区/关键词筛，fit=1 只看适合一人公司的小单。
| Name | Type | Req | Description |
|---|---|---|---|
| cat | string | – | 技能类目，如 软件开发 |
| fit | string | – | "1" = 只看小微友好单 |
| limit | integer | – | – |
| offset | integer | – | – |
| q | string | – | 标题/摘要关键词 |
| region | string | – | 地区，如 广东 |
| status | string | – | "open" = 只看在标 |
No output schema declared.
No examples provided.
soloteam_inbox ~34
收件箱（需 key）：收到的打招呼/应征/回复通知。（需 API Key）
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
soloteam_match ~58
互补推荐（需 key）：按 give/want 双向交集算出"你会的正是 TA 要的、TA 会的正是你要的"成员，带分数排序。（需 API Key）
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
soloteam_me ~33
当前身份总览（需 key）：本人名录主页、联系方式、核验状态。（需 API Key）
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
soloteam_member ~71
查单个成员主页详情：按 name（名录显示名，精确）或 id 二选一。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | 成员 id（directory 返回的 id） |
| name | string | – | 成员显示名（与 by-name 同源，精确匹配） |
No output schema declared.
No examples provided.
soloteam_meta ~40
一人行 SoloTeam 平台元信息：定位、工具清单、认证模型、文档入口。首次接入先调这个。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
soloteam_posts ~41
问答/互助帖（公开）：成员求助与经验交流。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
soloteam_projects ~47
项目广场（公开）：成员发布的协作/外包项目，含行业标签与状态。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
soloteam_teams ~113
组团协作（公开）：进行中的组团（recruiting/formed/active/done/dissolved），可按关键词搜；仍在招募（recruiting）但已过截标日的团队带 expired:true（仅标记，不隐藏）。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| q | string | – | 标题/简介关键词 |
| status | string | – | recruiting|formed|active|done|dissolved |
No output schema declared.
No examples provided.
How do I install the 一人行 SoloTeam MCP server?
一人行 SoloTeam MCP is a hosted endpoint at https://soloteam.com.cn/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · soloteam.com.cn
claude mcp add --transport http cn-com-soloteam-soloteam 'https://soloteam.com.cn/mcp'
What is the 一人行 SoloTeam MCP server?
一人行 SoloTeam MCP is listed in the public MCP registry as cn.com.soloteam/soloteam. 一人行 SoloTeam, 一人公司联盟 (solo-company alliance): 名录/互补推荐/政采线索 read-only; 身份类 tools 需 Bearer yrx_. This page covers its hosted endpoint (https://soloteam.com.cn/mcp).
Is the 一人行 SoloTeam MCP server safe to use?
一人行 SoloTeam MCP scores 68 out of 100 on VerifyMCP. 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 一人行 SoloTeam MCP server expose?
一人行 SoloTeam MCP exposes 11 tools: soloteam_meta, soloteam_conduct, soloteam_directory, soloteam_member, soloteam_projects, and 6 more. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.
Does the 一人行 SoloTeam MCP server require authentication?
No. We connected to 一人行 SoloTeam MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 一人行 SoloTeam MCP server still maintained?
一人行 SoloTeam MCP is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.