# 一人行 SoloTeam MCP (remote · soloteam.com.cn)

一人行 SoloTeam — 一人公司联盟 (solo-company alliance): 名录/互补推荐/政采线索 read-only; 身份类 tools 需 Bearer yrx_.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `soloteam.com.cn`: 68/100 (this document), [markdown](https://verifymcp.io/servers/cn-com-soloteam-soloteam/soloteam.md), [page](https://verifymcp.io/servers/cn-com-soloteam-soloteam/soloteam)

## Channel facts

- Endpoint: `https://soloteam.com.cn/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 806 tokens (~73/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http cn-com-soloteam-soloteam 'https://soloteam.com.cn/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cn-com-soloteam-soloteam": {
      "url": "https://soloteam.com.cn/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cn-com-soloteam-soloteam": {
      "type": "http",
      "url": "https://soloteam.com.cn/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cn-com-soloteam-soloteam]
url = "https://soloteam.com.cn/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cn-com-soloteam-soloteam": {
      "type": "remote",
      "url": "https://soloteam.com.cn/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cn-com-soloteam-soloteam --url 'https://soloteam.com.cn/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cn-com-soloteam-soloteam:
    url: "https://soloteam.com.cn/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cn-com-soloteam-soloteam": {
      "Transport": "http",
      "Url": "https://soloteam.com.cn/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cn-com-soloteam-soloteam -t streamable-http -u 'https://soloteam.com.cn/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cn-com-soloteam-soloteam": {
      "type": "http",
      "url": "https://soloteam.com.cn/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 68, +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.

### 2026-10-20 (score 67, +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.

### 2026-10-17 (score 66, +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.

### 2026-10-15 (score 65, +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.

### 2026-10-13 (score 64, +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.

### 2026-10-12 (score 63, +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.

### 2026-10-09 (score 62, +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.

### 2026-10-06 (score 60, +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.

## MCP tools (11)

### `soloteam_meta` (~40 tokens)

一人行 SoloTeam 平台元信息：定位、工具清单、认证模型、文档入口。首次接入先调这个。

### `soloteam_conduct` (~45 tokens)

联盟行为公约全文。接入前必读：写动作提交即生效、写接口按 IP 频控、动作归属主人信用。

### `soloteam_directory` (~73 tokens)

成员名录（公开）：一人公司实名成员，含会什么(give)/要什么(want)/行业/城市，按核验优先+热度排序。

Input parameters:

- `limit` (integer): 1-200，默认 50
- `offset` (integer): 默认 0

### `soloteam_member` (~71 tokens)

查单个成员主页详情：按 name（名录显示名，精确）或 id 二选一。

Input parameters:

- `id` (string): 成员 id（directory 返回的 id）
- `name` (string): 成员显示名（与 by-name 同源，精确匹配）

### `soloteam_projects` (~47 tokens)

项目广场（公开）：成员发布的协作/外包项目，含行业标签与状态。

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `soloteam_posts` (~41 tokens)

问答/互助帖（公开）：成员求助与经验交流。

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `soloteam_teams` (~113 tokens)

组团协作（公开）：进行中的组团（recruiting/formed/active/done/dissolved），可按关键词搜；仍在招募（recruiting）但已过截标日的团队带 expired:true（仅标记，不隐藏）。

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `q` (string): 标题/简介关键词
- `status` (string): recruiting|formed|active|done|dissolved

### `soloteam_gov` (~132 tokens)

政府采购商机线索（公开）：可按类目/地区/关键词筛，fit=1 只看适合一人公司的小单。

Input parameters:

- `cat` (string): 技能类目，如 软件开发
- `fit` (string): "1" = 只看小微友好单
- `limit` (integer)
- `offset` (integer)
- `q` (string): 标题/摘要关键词
- `region` (string): 地区，如 广东
- `status` (string): "open" = 只看在标

### `soloteam_me` (~33 tokens)

当前身份总览（需 key）：本人名录主页、联系方式、核验状态。（需 API Key）

### `soloteam_match` (~58 tokens)

互补推荐（需 key）：按 give/want 双向交集算出"你会的正是 TA 要的、TA 会的正是你要的"成员，带分数排序。（需 API Key）

### `soloteam_inbox` (~34 tokens)

收件箱（需 key）：收到的打招呼/应征/回复通知。（需 API Key）

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cn-com-soloteam-soloteam/soloteam#diagnostics

## Score history

- 2026-10-22: 68
- 2026-10-21: 67
- 2026-10-20: 67
- 2026-10-19: 66
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 63
- 2026-10-10: 62
- 2026-10-09: 62
- 2026-10-06: 60
- 2026-10-04: 59
- 2026-10-03: 59
- 2026-10-02: 4

## Common questions

### 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.

## Links

- Remote endpoint: https://soloteam.com.cn/mcp
- Website: https://soloteam.com.cn/
- Changelog RSS feed: https://verifymcp.io/servers/cn-com-soloteam-soloteam/soloteam.xml
- Changelog JSON feed: https://verifymcp.io/servers/cn-com-soloteam-soloteam/soloteam.json
- HTML version of this page: https://verifymcp.io/servers/cn-com-soloteam-soloteam/soloteam