One1 Trademark Risk Check
REMOTE · ONE1.CN · SCANNED SEP 27
Trademark conflict, logo look-alike and TRO enforcer checks for cross-border sellers.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1417 tokens (~202/item across 7 items; 7 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the One1 Trademark Risk Check MCP server?
One1 Trademark Risk Check is a hosted endpoint at https://one1.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 · one1.cn
claude mcp add --transport http cn-one1-trademark 'https://one1.cn/mcp'
{
"mcpServers": {
"cn-one1-trademark": {
"url": "https://one1.cn/mcp"
}
}
} {
"servers": {
"cn-one1-trademark": {
"type": "http",
"url": "https://one1.cn/mcp"
}
}
} [mcp_servers.cn-one1-trademark] url = "https://one1.cn/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cn-one1-trademark": {
"type": "remote",
"url": "https://one1.cn/mcp",
"enabled": true
}
}
} openclaw mcp add cn-one1-trademark --url 'https://one1.cn/mcp' --transport streamable-http
mcp_servers:
cn-one1-trademark:
url: "https://one1.cn/mcp" {
"McpServers": {
"cn-one1-trademark": {
"Transport": "http",
"Url": "https://one1.cn/mcp"
}
}
} assistant mcp add cn-one1-trademark -t streamable-http -u 'https://one1.cn/mcp'
{
"mcpServers": {
"cn-one1-trademark": {
"type": "http",
"url": "https://one1.cn/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Sept 26 72
First indexed and scored.
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 27 Sept 2026 · Probed https://one1.cn/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=one1.cn | CN=YE1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5082086fbb1d4e5dc3a333287f1f4807bcf |
| SANs: one1.cn, www.one1.cn | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 one1.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | present | 33094 | 8 | Verified |
| one1.cn. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://one1.cn/.well-known/oauth-protected-resource/mcp", scope="mcp"
Bearer resource_metadata="https://one1.cn/.well-known/oauth-protected-resource/mcp", scope="mcp"Protected resource metadata
| Document | https://one1.cn/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://one1.cn/mcp |
| Authorisation server | https://one1.cn |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://one1.cn/mcp | Verified | 200 | |
| http (plaintext) | http://one1.cn/mcp | HTTPS enforced | 301 | https://one1.cn/mcp |
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 →
coverage_info ~159
查 One1 各辖区的数据覆盖度:文本行数、数据截止日期、覆盖档(full/partial/thin/very-thin)、是否可作核名结论、图形库是否可搜、套餐门槛。 调其它工具前先看目标辖区能不能作结论:scope≠full 或 data_as_of 过旧(如 UK 2018-02、EU 2019-12、US 2025-02)的辖区,「无匹配」不代表可注册。 country: ISO 2 位国码(US/CN/KR/BR/…);留空返回全部辖区摘要。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
No output schema declared.
No examples provided.
graphic_trademark_search ~165
以图搜图:上传 Logo / 图形商标 / 产品主图的公网 URL,找视觉相似的美国图形商标。 用于卖家查自家 Logo/图案是否撞已注册图形商标(CLIP 视觉相似 + 名录加权)。 image_url: 公网可访问的图片 URL(PNG/JPG)。 nice_class: 尼斯类别,可选。limit: 默认 10。 返回: {count, results:[{mark, visual_similarity, risk_level, applicant, legal_status}]}。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| image_url | string | yes | – |
| limit | integer | – | – |
| nice_class | string | – | – |
No output schema declared.
No examples provided.
listing_scan ~148
扫描一段商品 listing 标题/文案,找出其中撞美国注册商标的词/词组并按风险分组。 用于卖家发品前一键自查整条 listing 标题是否含侵权商标词。 text: listing 标题或文案(可整段)。 nice_class: 尼斯商品类别号,可选。 返回: {summary:{高,中,低}, tro_count, hits:[{mark, risk_level, applicant, tro_alert?}]}。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| nice_class | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
trademark_lookup_by_serial ~120
按美国商标号(serial number)精确查该商标的详情与风险。 用于已知商标号(如收到侵权通知里的号)时直接查该标。走 idx_serial 索引,亚毫秒。 serial: USPTO 商标序列号,如 "78414956"。 返回: {serial, found, result:{mark, legal_status, applicant, risk_level, ...}}。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| serial | string | yes | – |
No output schema declared.
No examples provided.
trademark_owner_profile ~189
权利人/品牌的「维权方画像」:聚合其在美国的商标组合 + 是否为 TRO/Schedule A 高频维权方。 用于卖家评估某品牌是否激进维权(批量起诉 Schedule A + 临时禁令 TRO 常冻结账户)、是否应高度规避。 owner: 权利人或品牌名,如 "Nike" 或 "YETI"。 返回: {owner, is_enforcer, enforcement{level,note,src}, total_marks, live_marks, top_classes[{nice,count}], tro_marks[], sample_marks[], risk_hint}。 is_enforcer=true 表示命中维权种子库,强烈建议规避;结果仅供参考,不构成法律意见。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| owner | string | yes | – |
No output schema declared.
No examples provided.
trademark_owner_search ~147
按权利人/申请人(applicant)查其名下的美国商标。 用于做竞品权利人画像、查某公司商标布局、识别高频维权方。 owner: 权利人/公司名,如 "Nike, Inc."。 live_only: 仅 Live,默认 False。limit: 默认 20。 返回: {owner, count, results:[{mark, nice_class, legal_status, risk_level, tro_alert?}]}。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| limit | integer | – | – |
| live_only | boolean | – | – |
| owner | string | yes | – |
No output schema declared.
No examples provided.
trademark_text_search ~320
搜索与某个品牌名/商标词在美国注册商标库中冲突的商标(音/形/义近似检测)。 用于卖家给产品起品牌名前,查是否与已注册商标冲突。 query: 要核查的品牌名或商标词,例如 "Nike"。 nice_class: 尼斯商品类别号(如 "025"=服装鞋帽),可选;提供则按同类目重排风险等级。 live_only: 仅返回有效(Live)注册,默认 False。 limit: 返回条数,默认 10。 ⚠️ 判读规则(重要):`count` 是返回的**最近邻条数**,恒等于 limit,**不是冲突数**—— 即使该词完全无人注册,count 仍为 10。判断有无冲突请看 `has_conflicts` / `conflict_count`(= 风险等级为「高」的条数)。 ⚠️ `coverage.clearance_ok` 为 false 时,「无冲突」**不代表可注册**,必须结合当地检索。 返回: {query, conflict_count, has_conflicts, count, results:[...], coverage:{...}}。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| limit | integer | – | – |
| live_only | boolean | – | – |
| nice_class | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the One1 Trademark Risk Check MCP server?
One1 Trademark Risk Check is an MCP server listed in the public MCP registry as cn.one1/trademark. Trademark conflict, logo look-alike and TRO enforcer checks for cross-border sellers. This page covers its hosted endpoint (https://one1.cn/mcp).
Is the One1 Trademark Risk Check MCP server safe to use?
One1 Trademark Risk Check scores 72 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 One1 Trademark Risk Check MCP server expose?
One1 Trademark Risk Check exposes 7 tools: trademark_text_search, listing_scan, trademark_lookup_by_serial, trademark_owner_search, graphic_trademark_search, and 2 more. Their descriptions and schemas cost roughly 1,248 tokens of context every time the server is loaded.
Does the One1 Trademark Risk Check MCP server require authentication?
Yes. One1 Trademark Risk Check asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the One1 Trademark Risk Check MCP server still maintained?
One1 Trademark Risk Check is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.